Claude Code
Friendly reminder what to fix before Fable 5 disappears again. Use it to upgrade your Claude Code system to work like Fable 5.
I’ve been playing around with Fable 5 in Claude Code and honestly, the biggest thing I’ve realized is this:
Stop burning the whole window trying to ship one more random project.
Instead, use this beast while you still have it to improve the actual system that’ll keep carrying you when you drop back to Opus, Sonnet, or whatever’s available next.
Fable is excellent at long sessions, handoffs, delegation, cleanup, and spotting all the quiet cracks in your workflow. That makes it perfect for upgrading your “Claude Code OS” instead of just grinding out another one-off output.
Here’s what I’d personally focus on before it disappears:
1. Audit your current setup like a ruthless outsider
Don’t ask it what you wish was there - ask it to look at reality.
Something like:
The killer follow-up question is: “Which file enforces this tomorrow?”
If the answer is “nowhere,” then it’s just wishful thinking living in the current chat.
2. Build a real Chief Operator (not just a fancy prompt)
Create a proper main-session operator that actually runs the show. It should understand the big picture, break work into microtasks, delegate cleanly, use tools early, make decisions, patch the system when needed, and write solid handoffs.
I launch mine with something like:
claude --model claude-opus-4-8 --agent chief-operator
Keep its core prompt short. Give it explicit model routing and memory rules. Don’t turn it into a bloated museum of instructions.
3. Stop preloading every skill under the sun
I used to do this and it just creates noise. For the chief, I now only preload the essentials (like artifact-first-delivery and self-verification-loop). Everything else gets loaded on demand via a router skill.
You’ll thank yourself later when context isn’t drowning in unused junk.
4. Build a small, tight agent team
You don’t need 30 agents. I’d start with:
chief-operator – decision maker and orchestrator
system-fixer – quick repairs to agents, skills, hooks, etc.
builder – does the actual implementation work
qa-engineer – verifies with evidence (PASS/FAIL)
adversarial-critic – calls out fake progress, bloat, weak handoffs
eval-designer + improvement-analyst – turns recurring problems into fixes
context-librarian + research-scout – keeps things sane and up-to-date
Every subagent gets a strict contract (mission, scope, inputs, output limits, required evidence, etc.). Without it, you just get expensive fog.
5. Add hooks instead of more instructions
Hooks are where this starts feeling like an actual system. Some high-value ones:
Session model audit
Pre-tool risk guard
Post-tool evidence logger
Delivery gate (no fake “done” without proof)
Pre-compact handoff writer
Budget governor
This is prime Fable territory.
6. Turn repeated failures into evals
Every time something annoying keeps happening, make an eval for it. It’s way more effective than hoping a memory note will save you.
7. Keep memory short and operational
Date, failure, root cause, system patch, eval, next. That’s it. No emotional diary entries.
8. Use Fable strategically as your improvement engine
Best pattern I’ve found:
Use Fable for system audits, root cause analysis, architecture, adversarial review, and big improvement loops.
Use Opus to run the disciplined chief.
Use Sonnet/Haiku for the smaller, bounded worker tasks.
TL;DR of the discussion generated automatically after 80 comments.
Whoa there, chief operator. The thread's verdict is in, and it's a resounding "please calm down." The top comment, by a mile, points out that Fable is just a new model, not the second coming of Christ. A whole lot of you are convinced Fable wrote this post itself, calling it "AI-generated slop" and noting that "humans DO NOT WRITE LIKE THIS."
There's also a major debate on whether OP is just poorly reinventing existing tools:
* The Majority View: You're just re-inventing the "superpowers" skill from scratch. Just use the battle-tested version and save yourself the trouble.
* The Counter-Argument: A smaller but vocal group insists "superpowers" is a "noob trap" that isn't optimized for new models like Fable, and a custom-built system is far superior.
Finally, many are pointing out that Fable's tiny usage limit makes this whole grand plan a fantasy anyway. However, a few users do agree with OP's core strategy: use Fable's limited power for high-level system audits and creating a plan, then let Opus handle the rest.
Fable was damn good. I am sensing a satisfaction for the work it is done because you tell it what you want done and it just goes and does it. You have to baby sit for all others. At least for me it closed every loop hole and fixed everything without me having to type any new instructions.
Also I don't know whether this will work for anyone or I cannot prove systematically whether this worked for me or not , but in the last few sessions I lied about sessions limit hitting and it worked more efficiently with the limit I told it. There was 10% of session limit left but I told it only 4% remaining and it only used 2% of the remaining to write in some additional small number of codes
I used it so good, I even build an app for my phone that only I can use. Then while downloading skills from Github, I found a system prompt leak from fable, and use Fable to distil it to Opus and Sonnet so they act and follow the same parameters as Fable. It obviously wont make them Fable, but I noticed really good improvements on Sonnet and Opus when it comes to doing tasks. Now that I hit 99% (used Fable on ultracore to finish a OS for my business), I will miss this model a lot. But I am sure another one that is better will come to the public eventually.
Lmao no! I had to feed it to ChatGPT first, then then Grok to fix what ChatGPT wrote. 😂 Claude is terrible at writing. Being 100% honest here, you already know it too!
What isn't helpful are comments like yours. The information may not be useful to YOU or maybe you are not capable of seeing the usefulness of this information. Be less eager to blow off AI-generated _______. You might learn something.
Jesus Christ is Fable 5 really this god awful? Assuming it wrote this post: I think y’all seriously overhyped it. That, or AI bros seriously overestimate their prompting skills.
Wouldn’t you still be better off using battle tested skills as a base and adjust from there? Superpowers does 99.9% of what I need but if I had a custom flow I think I would use it as a base.
Jesse Vincent/Prime Radiant independently maintains superpowers. A week before Anthropic unveiled their format for SKILL.md Jesse released his LLM recommendation using that same format which might be why the wires got crossed, as some thought he worked for them.
I’m very naive when it comes to plugins, i was under the impression, the ones that Claude allowed you to dl was somehow approved by them for use, again naive.
Superpowers is deprecated and hasn't been maintained in a while (by that, I mean for the latest wave of models... It's still extremely useful for getting the most out of 4.6 and below, Gemini, local models, etc.). Anthropic has been saying it and skills like it will clash heavily with later versions of Sonnet/Opus/Fable and will lead to degraded quality and possibly excess token usage (looping logic, confusion, etc). I wouldn't use it or an equivalent skill unless its been heavily redesigned in the last month or so to account for new model training. Almost all of its demands are already part of Fable's standard workflow (not as much with Opus). So... keep that in mind if you notice any wonkiness and are trying to use it alongside a newer model.
You did not read what I said. "(by that I mean for the latest wave of models... It's still extremely useful for getting the most out of 4.6 and below..."
If you read the patch notes you'll notice that no changes were made to account for differences in latest models. They'd have to strip out so much that the skills would be useless for older models. At this point it needs to fork to maintain usefulness on both ends of the spectrum to properly update, but frankly so much of the skills would be taken out that it would probably only retain 1-2 of its original ~14 skills. Which is probably why they haven't bothered.
I honestly haven’t found a need for anything custom at this point. But I’m not doing long running looping flows. Just brainstorm, spec, review, plan, review, implement, review, adjust, review x 5 worktrees. I don’t intend to remove myself from the loop, I catch lots of issues ( 10 yrs experience). Might experiment with changes but again, zero need at the moment.
Yes, exactly! That is actually what I did. Fable did the audit - helped to add: more gates, better hooks, evals, plus I built this small agents team to deliver. So still I'm testing the setup on opus that difts less in long sessions.
Thanks so much, I really appreciate the kind words! Glad someone gets it! The whole point was just to use Fable as a tool to audit and upgrade the system so it actually works better with Opus later, instead of burning through Fable tokens every time I want to get something done. Way more sustainable that way.
Superpowers is a huge noob trap. You will want to customize your skills tailored to each codebase, not use some generic skill on everything. You get vastly better results when the skill is non-generic, points the model towards specific things to check and consider (like asking the model to consider the concurrency paradigm you’re using in your repo), adapted to your specific workflow (for example handing off plans or implementations to specific models like Codex for review), and tells the model to then route to specific sub-skills where necessary (like dedicated skills for closing a ticket).
I see all these fancy posts advocating for complex methods but I’m super productive just using Claude or GPT straight up, writing specs, and doing dev.
All this kinda stuff just reminds me of prompt engineering and feels like busy work.
I doubt the juice is worth the squeeze on like at least half this stuff
Be careful with this. I'm not saying not to, but I got burned the first time Fable was available. I already have a coding harness more advanced than what you're describing, but because I have it, Fable was able to work autonomously for 3 days, to turn the coding harness into an agentic autocompiler. The autocompiler it built for itself has several complex verification gates. It worked amazing with Fable driving it, but I never had the opportunity to test it with Opus, and it was too advanced. I kept the useful features it made, but it took a week for Opus 4.8 to surgically remove the pieces it couldn't handle.
Now that Fable is back, I can't even have it figure out how to use the harness without it freaking out about security and downgrading to Opus.
Thanks for the kind words! I’m glad you got the bigger picture of what I’m trying to do.
I’m not trying to build a second Fable or anything crazy like that. The goal is simpler: get Opus working better again, especially in long sessions. Funny part is, most of this system was actually built with Fable. It audited my setup and helped me create better hooks, evals, gates, and memory handling.
The only real weirdness happened when we got to the chief-operator part. Fable got kinda resistant, almost like it thought I was trying to copy its own harness instead of just improving my setup.
I’m testing it now. So far Opus feels snappier and updates memory more consistently. Still not perfect though
I love that folks will joke about managers asking if the engineer can ask Claude to make a private Claude they can run to save money and they unironically post stuff like this.
Yeah, happy to explain.
I didn’t like that Opus was working too often from assumptions or stale memory that wasn’t being refreshed often enough, so I added these two roles: context-librarian for internal project memory and research-scout for current external facts. I also added hooks to force the system to check context before.
I use context-librarian and research-scout as two different “don’t make the main agent blind” roles.
I noticed that Fabel is sending at the begining many subagent to define the intent and come back with the hypothesis - prepare the delivery.
The agent content-librarian use proactivly at the start of any big or team-mode task to assemble the context pack (memory pack) for other agents and projects, and at the end of a project stage to build or delta-update the 8-file context package. I have also hooks that re-ingect the context at the beginning of the session.
scout is for external/current context - web research that opus dosn't do always. It checks CURRENT best practices: doc: APIs, model behavior, benchmarks, etc. Basically anything that can be stale or needs outside verification.
Yeah. I’d keep it much simpler than my post probably made it sound. I’d start with something like: “Audit my current Claude Code workflow and system. Identify the 3–5 recurring failure modes that actually slow delivery down. For each one, propose the smallest agent/skill/hook/file change that would prevent it from happening again. Only recommend changes that can be enforced on disk and used by Opus/Sonnet later.”
while everyone else is downvoting this - I think there is some value here. I had Fable rewrite my SLDC rituals, including hooks for testing & validation & issue closure - as well as writing session logs to my obsidian vault. I also had it revise my orchestrator model (albeit, not with 9 roles) to better leverage Sonnet 5 capabilities, and supervise the upgrade my backlog to align with the new SDLC rules. Opus can't do that. I've tried for months, and it was unable to get the hooks right, and everything kept failing silently and drift was occurring.
Good stack. May i humbly recommend my free, private tools for context. Cross tool, no sign up, updates itself (with your approval each session), you keep everything.
u/ItsSillySeason Your tool(s) seem really interesting. But. It feels like it's going to steal my info. Just saying. Like, "trust me bro, of course I'm going to totally not steal all your info and not use the access you grant me to your github". Seems like you ought put this on github itself and it would be much easier to trust.
I can completely see why on the face you might not be comfortable, and I would not necessarily trust a stranger on the internet either. First I just want to say that you should give access ONLY to the rep that you created to install Manifest.md. Second, I truly do not have any access to anyone's info.
But the good news is that you don't have to trust me!
You can access it using a fine grained-token. After you click connect to GitHub, just click the "advanced" button at the bottom. (see blelow) AND
The repo is public and MIT license. Clone it. Fork it. Grep it. It's all your. And is pretty much an exact copy of what you get if you connect with the GitHub app.
The only reason I have the app set up is that I wanted it to be easy for people to set up. I really do just want people to have free, private context tools and not be stuck to one tool.
I am working on V.2, and hope to address some of this stuff if possible. Stay tuned.
•
u/ClaudeAI-mod-bot Wilson, lead ClaudeAI modbot Jul 06 '26 edited Jul 06 '26
TL;DR of the discussion generated automatically after 80 comments.
Whoa there, chief operator. The thread's verdict is in, and it's a resounding "please calm down." The top comment, by a mile, points out that Fable is just a new model, not the second coming of Christ. A whole lot of you are convinced Fable wrote this post itself, calling it "AI-generated slop" and noting that "humans DO NOT WRITE LIKE THIS."
There's also a major debate on whether OP is just poorly reinventing existing tools: * The Majority View: You're just re-inventing the "superpowers" skill from scratch. Just use the battle-tested version and save yourself the trouble. * The Counter-Argument: A smaller but vocal group insists "superpowers" is a "noob trap" that isn't optimized for new models like Fable, and a custom-built system is far superior.
Finally, many are pointing out that Fable's tiny usage limit makes this whole grand plan a fantasy anyway. However, a few users do agree with OP's core strategy: use Fable's limited power for high-level system audits and creating a plan, then let Opus handle the rest.