TL;DR: Everything you need to do to get maximum value from Fable.
I guarantee that after you're done reading, you'll have all the necessary tools to quite literally 10x your AI productivity with Claude Fable.
These are the exact principles that Anthropic is telling you to use - sourced straight from the Claude Docs themselves.
Table of Contents
Differences with Fable 5
Loop Engineering 101
Fable 5 + Skills
Vision Capabilities
Building A Context System w/ Fable (memory)
Let's get right into things:
Differences with Fable 5 (based on what we know)
I want to preface by saying I'm writing this before the official Fable 5 re-release, and this is only the best information I have available - things may be subject to change.
Based on the official Anthropic docs, there are 6 core differences between Fable and all other Claude models:
1. Run Time
Every Claude model before Fable 5 worked in relatively short bursts.
Claude Fable 5 is meant to sustain output over extended periods to complete multi-day, goal-directed tasks.
This is one of the biggest shifts. Fable 5 is meant for fully autonomous work (paired with /goal or /loop).
2. It Gets Things Right First Time
One of the most reported early observations from people using Fable 5 is how rarely they need to iterate. Early testers reported single-pass implementations of systems that previously took days of iteration.
3. Clarifying Questions
To execute autonomous work loops accurately, Fable 5 may ask a series of clarifying questions before it kicks off its autonomous run.
4. Agent Management
Fable 5 is built to manage multiple parallel subagents at once (spinning up 50+ agents for complex tasks).
5. It "Sees" Better
Claude Fable 5 interprets dense technical images, web applications, and detailed screenshots with substantially higher accuracy (more on this later).
- Coding + Security Audits
It's no secret that Fable is a coding genius. This new model is especially powerful for codebase review and debugging (though it seems the re-release will nerf Fable's abilities in these areas).
Loop Engineering 101
The first thing you need to understand about Fable is that it was built for fully autonomous work.
This means that if you're going to use this model, you need to understand loop engineering.
Loop engineering sounds complex, but you actually don't need to be technical at all to launch fully autonomous loops.
wtf is a /loop?
In simple terms, think of loops as a way for AI agents to prompt themselves.
Instead of you being the barrier between every prompt and every iteration, you design a loop once, and your AI agents handle all the back-and-forth - only coming to you when the success criteria have been met.
I really like this Loop Anatomy graphic from @0xCodez.
There are two primary ways to launch loops inside of Claude Code:
- /goal: How you launch tasks that run until they're done.
Example:
"/goal keep researching until you can answer these 5 questions."
- /loop: How to run intervals that don't stop until you cancel them.
"/loop every 30 minutes, flag any email that actually needs me."
Both of these strategies have their place, and if you're going to run Fable 5, you need to use these two basic loop engineering commands inside Claude Code.
Barbell Strategy (model selection)
To save on token costs, I'm running a "barbell" strategy approach, and I think most people should replicate it.
Planning the loop (initial 10%): Fable 5
Gruntwork & execution (middle 80%): Subagents like Sonnet, Haiku & Opus
Final verification (last 10%): Switch back to Fable 5 to verify the spec
Barbell Strategy Approach for Fable 5
Fable 5 + Skills
Loop engineering within Fable is extremely powerful, but without the necessary skills, Claude lacks the context, data, and information needed to produce viable outputs.
This is where Claude Skills come in, and if you plan to use Fable for any repetitive workflows, you'll want to pay attention here.
Claude Skills \summary\
What Is a Skill?
The way to think about a skill is simple: it's a recipe you teach once, and Claude reuses forever.
There are three primary ways I like to build skills for Fable:
1. From a past chat
This is the fastest way to start.
If you've done any kind of work in Claude (financial analysis, writing, research, video scripting, etc.), you can simply ask Claude to analyze that entire chat, extract your preferences and patterns, and turn it into a reusable skill.
Open a chat, type /skill creator, and let Claude do the work.
2. From scratch
Go into Claude Code, select skill creator, hit enter, and Claude walks you through building a skill from the ground up.
A good way to start: open a Google Sheet, list everything you do on a regular basis, and use that as your starting point for creating Fable Skills.
3. From data
This is the high-leverage move, and my favorite way to create Claude Skills in general.
If you're building an X account, for example, you could pull thousands of tweets from creators in your niche, feed them into a skill, and tell Claude to mimic the tone, the thought patterns, the structure.
Every tweet it writes for you becomes training data. You give it feedback on what landed, what flopped, what's working on the current meta, and the skill updates.
Why Skills Matter More on Fable
Fable 5 is specifically built to be thorough and proactive about testing its own work.
That makes it the best Claude model ever for iterating on skills, because it doesn't just execute the skill, it actively looks for ways to improve it.
One thing worth knowing: you own your skills. They live in your local folder, not inside Claude's memory. That means you can port them to GPT, to Gemini, or whatever model comes next.
Fable 5 Visual Capabilities
This is something I haven't seen any other creator talk about.
Vision is one of the most underrated things Fable 5 does well, and most people aren't using it anywhere near its ceiling.
For example, when Fable 5 was originally released, Claude posted a video where Fable beat the entire Pokémon Red game - only using visual capabilities!
Some creative ways that I plan to use Fable 5's visual capabilities:
Document & Data
- Extract exact data points from charts, graphs, and scientific figures in PDFs
Design & UI
- Drop a screenshot of any UI and get detailed critique and improvement suggestions
Development
- Screenshot a dashboard and get the underlying logic reverse-engineered
Content & Creative
- Drop screenshots to replicate creatives
Agentic / Computer Use
- Read live interfaces and act on them without helper tools
If you want to get the most out of Fable, take advantage of its amazing visual abilities!
Building A Context System w/ Fable (memory)
All of this, loops, skills, vision, none of it reaches its ceiling without one thing: context.
I strongly encourage everyone reading to set up a context memory system for their Fable workflows.
Here's what I personally recommend:
Step 1: Create a Local Folder
Start simple. Create a folder on your machine called (something like /claude-context). This is your AI brain. Everything you put in here becomes context that Fable can reference in every session.
What goes in it:
- A company map (who's in the business, what each person does, current priorities)
- Production SOPs for anything you do repeatedly
- One-pagers for important clients, projects, or meetings
- Any strategic documents you've created (launch plans, content systems, distribution strategies)
- A running log of decisions made and outcomes
Pro Tip: Use Wispr Flow to mass dump context here.
Step 2: Create a Memory File
Inside your folder, create a file called claude-memory.md. This is where Fable stores and updates what it learns about you over time.
Add one instruction to your setup (very important):
*"Every time I give you major context about my business or situation,
update claude-memory.md with the key details."*
Now it becomes a self-updating system. Every material change you share is automatically written to the memory file.
Step 3: Create an Instructions File
Create a claude-instructions.md file that tells Fable how to behave.
This is where you set the rules for how it stores memory, how it formats responses, what it should always or never do. Think of it as the standing brief it reads before every engagement.
A simple starting template:
1Every time I share major context, update claude-memory.md.2Always reference past decisions before making new recommendations.3When I ask for strategy, assume you know everything in this folder.4Format all outputs in markdown unless I say otherwise.
Step 4: Connect It
Point Claude Code at your context folder using /add or reference it in your CLAUDE.md. Once it's connected, every loop, every skill, every session starts with Fable already knowing your world.
This is the base memory system that I think everyone should set up and run with Fable 5. The good thing is you can also transfer it across tools immediately.
Final Thoughts
I hope you've found this article helpful.
I'm extremely excited about the Fable 5 re-release, and I think that if you master these principles, you'll get the most out of Fable.
I plan to make a ton more Fable 5 content, so be sure to follow me here @milesdeutscher and @aiedge_ for deeper AI insights.
If you enjoy written AI content, feel free to subscribe to my AI newsletter.
It's 100% free, and I genuinely believe we've built the best AI newsletter in the game (we also never spam).
Get started here:
Thanks for reading!
