# The Claude Fable 5 Prompt Pack 12 copy-paste prompts for getting real work out of Claude Fable 5 on your Max plan. From the Waboom AI Operator's Guide: https://www.waboom.ai/resources/claude-fable-5 **The rule that beats every prompt: context is king.** Before you send any of these, attach the files that matter: plans, drafts, price lists, contracts, meeting notes. A rough brief with the real files beats a perfect brief with none. ## Contents 1. The Kickoff Brief 2. Stop Overplanning 3. Scope It First 4. The Self-Checking Build 5. No Fake Progress Reports 6. Stay In Your Lane 7. Keep It Simple 8. The Overnight Run 9. Delegate Like a Manager 10. Give It a Memory 11. Readable Reports 12. One Thing to Never Ask --- # 1. The Kickoff Brief Fable 5 makes hundreds of small decisions during a long job. If it does not know who the work is for, it guesses. **When to use:** Start every meaningful task with this, and attach the files that matter before you hit send: plans, drafts, price lists, contracts, meeting notes. Context is king, and Fable 5 can only work with what it can see. ## The prompt ``` I'm working on [the larger task] for [who it's for]. They need [what the output enables]. With that in mind: [request]. ``` ## What that looks like filled in ``` I'm working on a price review for my joinery business. It's for me and my ops manager. We need to see exactly where our margin has slipped so we can reset our rates before we quote the spring season. With that in mind: go through the three supplier price lists and last year's quotes in this project, compare them against our current rate card, and give me the 15 products where margin has slipped the most, with a recommended new rate and one line of reasoning for each. ``` **Why it works:** Fable 5 checks every small decision against the goal you give it, so one line of context beats three paragraphs of instructions. --- # 2. Stop Overplanning On smaller tasks Fable 5 can research and deliberate for minutes before it lifts a finger. That time comes out of your limits. **When to use:** Paste at the top of any task where you already know what you want and just need it done. ## The prompt ``` When you have enough information to act, act. Do not re-derive facts already established in the conversation, re-litigate a decision I have already made, or narrate options you will not pursue. If you are weighing a choice, give a recommendation, not an exhaustive survey. ``` **Why it works:** This is Anthropic's own instruction for keeping the model moving when a task is clear enough to start. --- # 3. Scope It First Most people under-use Fable 5 by giving it small tasks. Its real strength is jobs you would normally break up yourself. **When to use:** Use when the job is bigger than one sitting and you have not fully thought it through. Let the model do the thinking. ## The prompt ``` Here is the job: [describe the outcome you want, even roughly]. Before you start, scope it. Tell me how you would break it down, what you need from me, and what could go wrong. Ask me your clarifying questions now, in one batch. Once I answer, execute end to end without checking in unless you are genuinely blocked. ``` ## What that looks like filled in ``` Here is the job: I want a complete onboarding pack for new hires at my electrical contracting company. Rough shape in my head: a first-day checklist, a first-week training plan, the safety basics, and a who-to-call list. I have uploaded our current staff handbook, two old checklists and our org chart; keep whatever is worth keeping. It is not fully thought through, which is why I am handing it to you. Before you start, scope it. Tell me how you would break it down, what you need from me, and what could go wrong. Ask me your clarifying questions now, in one batch. Once I answer, execute end to end without checking in unless you are genuinely blocked. ``` **Why it works:** Anthropic's advice is to start at the top of your difficulty range: pick a harder task than you would give other models, and have Fable 5 scope it before executing. --- # 4. The Self-Checking Build A long run that drifts off spec in hour one wastes everything after it. Fable 5 can catch this itself, but only if you ask. **When to use:** Add to any long-running job: a build, a big document, a research project, a batch of pages. ## The prompt ``` Establish a method for checking your own work at an interval of [every major step / every 30 minutes / every section] as you build. Run this check every interval, verifying your work with subagents against the specification. If a check fails, fix it before moving on. ``` **Why it works:** Anthropic found that fresh-context checkers outperform the model critiquing itself, like a builder who stops every hour to check the level. --- # 5. No Fake Progress Reports On long runs, any AI can drift into reporting what it intended to do rather than what it did. **When to use:** Add to every long or unattended run. Pairs perfectly with The Overnight Run below. ## The prompt ``` Before reporting progress, audit each claim against a real result from this session. Only report work you can point to evidence for; if something is not yet verified, say so explicitly. Report outcomes faithfully: if something failed, say so with the output; if a step was skipped, say that; when something is done and verified, state it plainly without hedging. ``` **Why it works:** In Anthropic's testing this instruction nearly eliminated fabricated status reports, even on tasks designed to provoke them. --- # 6. Stay In Your Lane Fable 5 is proactive. Sometimes that means it drafts the email, changes the file, or fixes the thing when you only wanted an opinion. **When to use:** Use when you want analysis and advice, not action. Especially anywhere it can touch real systems, files or messages. ## The prompt ``` When I am describing a problem, asking a question, or thinking out loud rather than requesting a change, the deliverable is your assessment. Report your findings and stop. Do not apply a fix until I ask for one. Before taking any action that changes real state, check that the evidence actually supports that specific action. ``` **Why it works:** It draws a clean line between advising and acting, which is exactly the line you want with a model this capable. --- # 7. Keep It Simple At full power Fable 5 can over-deliver: extra features, extra structure, extra polish nobody asked for. All of it costs credits. **When to use:** Add to focused fixes and small builds where you want exactly what you asked for and nothing else. ## The prompt ``` Don't add features, refactor, or introduce abstractions beyond what the task requires. A small fix doesn't need surrounding cleanup, and a one-off job doesn't need a reusable system behind it. Don't design for hypothetical future requirements: do the simplest thing that works well. Don't add handling for scenarios that cannot happen. ``` **Why it works:** The simplest version ships faster, costs less of your weekly limit, and is easier to check. --- # 8. The Overnight Run Left alone, a long run can stall on a polite question like "Want me to continue?" and sit there for eight hours waiting for you. **When to use:** Use for any job you plan to walk away from: overnight work, weekend runs, anything unattended. ## The prompt ``` You are operating autonomously. I am not watching in real time and cannot answer questions mid-task, so asking "Want me to...?" or "Shall I...?" will block the work. For reversible actions that follow from the original request, proceed without asking. Before ending your turn, check your last paragraph. If it is a plan, an analysis, a question, or a promise about work you have not done, do that work now. End your turn only when the task is complete or you are blocked on input only I can provide. ``` **Why it works:** It converts every would-be checkpoint into forward progress, so you wake up to finished work instead of a question. --- # 9. Delegate Like a Manager Fable 5 can spin up subagents, which are helper copies that work on separate pieces at the same time. Most people never ask. **When to use:** Use in Claude Code when the job splits into independent pieces: research five competitors, audit ten pages, process a folder of files. ## The prompt ``` Delegate independent subtasks to subagents and keep working while they run. Intervene if a subagent goes off track or is missing relevant context. ``` **Why it works:** Independent pieces get done in parallel instead of one after another, so the whole job lands sooner. --- # 10. Give It a Memory Every new session starts from zero. You end up re-teaching the same preferences and re-fixing the same mistakes. **When to use:** Set up once in Claude Code for any project you return to. Then run the second prompt whenever you finish a big piece of work. ## The prompt ``` Keep a notes folder for lessons learned. 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 project files already record; update an existing note rather than creating a duplicate; delete notes that turn out to be wrong. To set it up from history, run this once: Reflect on the previous sessions we've had together. Use subagents to identify core themes and lessons, and store them in the notes folder. Make sure you know to reference it in future sessions. ``` **Why it works:** Anthropic reports Fable 5 performs notably better when it can record lessons from previous runs and read them back later. --- # 11. Readable Reports After hours of work the final summary can read like an engineer's shorthand: dense, jargon-heavy, full of labels you never saw. **When to use:** Add to any long job where the final write-up matters, especially work you will forward to someone else. ## The prompt ``` Lead with the outcome. Your first sentence should answer "what happened" or "what did you find", the thing I would ask for if I said "just give me the TLDR". Supporting detail comes after. When you write the final summary, write it for a reader who did not watch you work: complete sentences, terms spelled out, no shorthand or labels you invented along the way. If you have to choose between short and clear, choose clear. ``` **Why it works:** The summary is the product. This makes it readable by the person who was not in the room, which is usually the person who matters. --- # 12. One Thing to Never Ask Old prompt packs are full of "explain your reasoning step by step" and "show your thinking". On Fable 5 these backfire. **When to use:** This is a warning, not a prompt. Check your saved prompts and delete these instructions before reusing them with Fable 5. ## The rule Avoid instructions like: "show your thinking", "explain your reasoning step by step", "transcribe your internal reasoning", "think out loud before answering". Fable 5 declines these and the request can fall back to a lesser model, so you pay Fable prices for Opus answers. If you want to follow along, ask for progress updates or a summary of the approach instead. The reasoning already happens on its own; you don't need to ask for it. **Why it works:** Fable 5 protects its internal reasoning by design. Asking for it triggers a refusal instead of a better answer. --- Adapted from Anthropic's official Claude Fable 5 prompting guide. Full guide with all 12 prompts: https://www.waboom.ai/resources/claude-fable-5