Twenty practical tricks to get better results from Claude Fable 5.2 while spending less
8 bite-sized sections
2 min read
Free, no signup
Short answer
A free list of 20 Claude Fable 5.2 hacks as of November 2026: prompting tricks for long and complex work, planning and verification habits, using subagents, saving money with model routing, prompt caching, and fast mode only when needed, context management, Projects and CLAUDE.md, and safety habits, based on what Anthropic has published about the model.
These hacks are simple habits, not secret settings. They work because Fable 5.2 is built for long, ambiguous technical work, and it does best when it has a clear goal and a way to check itself.
The biggest hack is a clear definition of done.
02
Prompting hacks
1 · State the outcome and the why
Fable makes better choices when it knows the purpose
2 · Define done
Say exactly what a finished result looks like
3 · Ask for questions first
Let it ask up to five questions before starting
4 · Paste the real material
Give files and data, not summaries of them
5 · Say what you already tried
It will not repeat your dead ends
03
Planning hacks
6 · Plan first
Ask for a plan and edit it before any work starts
7 · Work in stages
Break big jobs into checkpoints
8 · Ask for assumptions
Have it list what it is assuming
9 · Use subagents
Let it split large projects across helper agents
04
Verification hacks
10 · Give it a test
Tests, expected numbers, or a checklist to pass
11 · Ask it to check its own work
Review against the definition of done before finishing
12 · Ask what it is unsure about
Get a list of weak spots to review yourself
05
Cost hacks
13 · Route by difficulty
Use Haiku, Sonnet, or Opus 5.5 for routine steps and Fable for the hard parts
14 · Cache long context
Cache reads cost $0.20 per million tokens in the API
15 · Use fast mode sparingly
It is up to 2.5x faster but costs $16 input and $80 output per million tokens
16 · Start fresh chats
Do not drag a huge old conversation into a new task
06
Setup hacks
17 · Use a Project
Keep instructions and key files in one place
18 · Write a CLAUDE.md
In Claude Code, give standing rules for your codebase
19 · Save winning prompts
Turn prompts that work into templates or skills
07
A safety hack
20 · Keep approvals on
Review plans and risky actions, and never paste secrets into prompts
Anthropic notes that flagged cybersecurity and biology requests are routed to less capable models, so legitimate researchers should use its verification programs.
08
Put three hacks to work today
Add a definition of done to your next prompt
Ask for a plan before execution
Give it a test to pass
The golden rule
Do not look for magic words. Give Fable 5.2 a clear goal, a plan to follow, and a way to check its work, and spend its power only where it matters.
Prompting
Planning
Verification
Cost
Caching
Setup
Safety
Pick three hacks from this list and use them on your next hard task.
For research and ideas only. Results vary and nothing here is a promise of income. See our Disclaimer.
See you Monday!
Weekly newsletter
Everything new, every Monday.
One short email every Monday with everything shipped that week: new free tools and websites, new guides, new free browser tools and what's new in my free Gumroad libraries, plus how the site is growing. Free, and you can unsubscribe anytime.
You sign up on Gumroad, which stores your email to send the newsletter. See our Privacy Policy.
Cookies and your choices
Visits are counted by Cloudflare Web Analytics, which sets no cookies and stores nothing on your device. An affiliate tracking script from Impact.com also loads on our pages and can set its own cookies so partner companies can credit us for sign-ups. Essential storage is always on so pages load and work correctly. You decide whether your browsing preferences are saved on your device. Read the Privacy Policy.