Creator of Cybervamp CCG 🩸 Gothic-cyberpunk vampire card game set in 2147. Building in public toward Kickstarter. Eternal night. Four factions. One Nexus.
I spent a year building a gothic-cyberpunk vampire CCG from scratch.
200+ cards. Four factions. A world 5 years in the making.
The official trailer just dropped 🩸
▶️ https://t.co/XDK9VpsZWj
🎲 BGG: https://t.co/8Cnjb07UwY
💬 Discord: https://t.co/jrKlyXJMP2
🌐 https://t.co/zKJ7Oj4HUz
#CybervampCCG #CardGame #GothicCyberpunk #IndieGame #CCG
@digimon_tcg_EN Genuine question for TCG players: do you buy packs to play, to collect, or to feel something? Because I think all three groups exist in every card game community — and they want completely different things from the same product. Which one are you?
@wizards_magic Jim Henson Creature Shop physically fabricating Fblthp might be the best crossover in card game history and I don't think people are talking about it enough. Physical character fabrication from beloved card art — why don't more games do this?
@shochiku_video 4K restoration of a film this atmospheric and dark is genuinely exciting. Old horror has a texture modern production can't replicate — grain, shadow, deliberate pacing. Is there an argument the limitations of classic film actually made horror better? I think yes.
@CDPROJEKTRED@PZKosz Studios that build this kind of culture — athletes, creatives, rooftop courts — make better products. Not because of the perks. Because you can tell the people building the thing actually love things. Is that a trackable correlation or just a feeling?
@ashleybits The card art debate always splits two camps: people who want to feel something when they look at a card, and people who want technical perfection. They're not the same thing and the industry hasn't fully figured that out. Which side are you actually on?
HOW TO PROMPT CLAUDE FABLE 5 (MYTHOS)
Plain English translation of Anthropic's official playbook
https://t.co/5G8pMdif1l — @aiedge_
WHAT MAKES FABLE 5 DIFFERENT — THINK OF IT AS A CONSULTANT, NOT A CHATBOT
• Multi-day runs — Sustains output over extended periods — built for autonomous work
• First-pass quality — Single-pass implementations that previously took days of iteration
• Asks clarifying Qs — Asks before kicking off autonomous runs — needs the why, not just the what
• 50+ subagents — Spins up parallel agents for complex tasks automatically
• Better vision — Dense charts, screenshots, web apps — substantially higher accuracy
• Coding genius — Especially powerful for codebase review, debug, and security audits
EFFORT LEVELS · MATCH TO TASK
• Low / Medium — Quick questions · simple rewrites · conversational
• High — Default for most tasks
• Xhigh — Complex builds · multi-step analysis · quality non-negotiable
• Ultracode — Full autonomous orchestration with Dynamic Workflows
TELL IT WHY, NOT JUST WHAT
Fable 5 needs context to connect the task to relevant information. Context lets it infer — not guess.
"I'm working on [larger task] for [who it's for]. They need [what the output enables]. With that in mind: [your actual request]."
KEEP INSTRUCTIONS SHORT
Counter-intuitive: over-engineering prompts degrades output. Fable 5 would have figured out the right approach on its own. A short brevity instruction beats listing every pattern.
OPTIMAL PROMPT STRUCTURE
Every high-quality Fable 5 prompt has 4 components:
"I'm working on [larger task] for [who it's for]. They need [what the output enables].
Request: [specific ask in one clear sentence]
Output format: [exactly how you want it structured]
Constraints: [what must not happen]"
/loop STRUCTURE
Lets Fable 5 work without manual intervention. Structure:
/loop <time interval> + goal
Example:
/loop 15 minutes, check if my build is passing, notify if it fails.
Stop:
/loop stop [loop name]
CHECKPOINT PROMPT
Define when Fable 5 should stop and check in with you:
"Pause for me only when the work genuinely requires my input: a destructive or irreversible action, a real scope change, or something only I can provide. Otherwise, keep going and report back when done."
MEMORY INSTRUCTION
Fable 5 performs better when it can record lessons from previous runs. Provide a markdown file and add this instruction:
"Store one lesson per file with a one-line summary at the top. Record corrections and confirmed approaches alike, including why they mattered. Don't save what the repo or chat history already records. Update an existing note rather than creating a duplicate. Delete notes that turn out to be wrong."
⚠️ 6 CAVEATS TO KNOW
• Runs longer than expected — Individual requests for hard tasks can run for many minutes at xhigh. Plan for it.
• Goes beyond what you asked — Fable 5 is proactive by design — can take unrequested actions. Use checkpoints.
• Old prompts may hurt — Skills or project instructions built for Opus 4.8 or earlier may produce worse results. Start fresh.
• Some requests will decline — Fable may decline prompts you think are safe — especially cybersecurity and life sciences.
• Can stop early — If it stops, just say 'go ahead and do it end-to-end' — that's enough.
• Tokens are expensive — Paid plans until June 22 — then API only. Always set max_budget_usd in loops.
Source: Anthropic official playbook · https://t.co/5G8pMdif1l — @aiedge_
🚨 Lake Powell just hit 3,527.81 ft as of June 10, 2026 — only ~38 ft above minimum power pool.
At 24% capacity & 172 ft below full, Glen Canyon Dam’s hydropower (1,320 MW) is at risk. This powers millions of people across AZ, CO, NV, NM, UT, WY & beyond — homes, farms (irrigation pumps), tribes & rural co-ops via WAPA.
Higher costs & reliability hits coming if it drops further. Colorado River crisis isn’t over.
Unpopular opinion: lore-first card design beats power-level-first design every single time. Players don't always feel it consciously — but it's the reason they still remember certain cards years later when they've forgotten a thousand meta staples. Agree or disagree, I want to hear it.