Cindy Zhu.
Free guides
Power-user Claude

Claude Fable 5's system prompt: the real story + the patterns worth stealing

Hey, it's Cindy ๐ŸŒฑ A plain-English walkthrough of the Claude Fable 5 system prompt and the patterns worth stealing for your own AI instructions.
btw the waitlist for AI System Club is now open! If you're keen on using AI to automate your content, video editing, job search, business or build AI agents, feel free to sign up (only if you want to hehe). Ps. the waitlist gets first dibs:)

The links


the timeline

What actually happened

  • ๐Ÿ—“ June 9, 2026: Anthropic releases Claude Fable 5 and publishes its core system prompt on the docs page above.
  • ๐Ÿ” June 9, 2026, hours after launch: a community extraction of the full claude.ai prompt (including the tool layer) lands on GitHub.
  • โธ June 12, 2026: US export controls temporarily suspend Fable 5 access (source: the redeployment post above).
  • โ–ถ๏ธ July 1, 2026: Fable 5 comes back with updated safety classifiers, which is the "just came back" you keep hearing.

So "leaked" is the viral word, and I kept it because that is what everyone calls it. The accurate version: Anthropic publishes the core prompt itself, and the GitHub file is a community extraction that additionally captures tool instructions the published page only references. Anthropic has not confirmed the extraction is complete or unmodified, and it reflects claude.ai specifically (the API gives you no default system prompt, and Claude Code ships its own instructions).


copy these

The 3 patterns worth stealing

These come straight from the file, and they work in any CLAUDE.md, project instructions, custom instructions box, or agent prompt.


pattern one

1. Named sections with one job

The prompt is not one wall of rules. Every rule lives inside a scoped section like tone_and_formatting, search_instructions, refusal_handling, or user_wellbeing.

โœ‚๏ธ Steal it: split your instructions into sections like ## voice, ## tools, ## formatting, ## never do. One topic per section, no rule floating homeless at the bottom.


pattern two

2. Decision rules, not vibes

Claude is not told "search when useful". It gets explicit if-then logic: answer directly for stable knowledge, always search for anything that changes (roles, prices, news, new releases), and scale effort to the task (one search for a single fact, several for deep research, suggest the Research feature past that).

โš™๏ธ Steal it: for every tool or recurring choice in your setup, write the trigger and the action. "If the request mentions a brand deal, read the deals folder first. If a stat is older than 6 months, re-verify before using it."


pattern three

3. Worked examples, including what not to do

Rules come with demonstrations. There are dedicated example sections, and even a literal "What not to do" list followed by "What this should feel like", with a good phrasing shown next to a weak one.

๐Ÿงช Steal it: under each instruction, paste one real example of output you loved and one you rejected, labelled. Models copy examples far more reliably than they follow adjectives like "professional" or "engaging".

๐ŸŽ Bonus pattern I could not fit in the reel: severity tiers. The copyright section is written as a hard limit ("NON-NEGOTIABLE") while style preferences stay soft, so the model knows which rules can flex. Mark your own dealbreakers the same way.

run this

The exact rewrite prompt

Download the extraction as claude-fable-5.md, put it in a folder with your current instructions file, then run this in Claude (Claude Code or a Claude project both work):

๐Ÿ› ๏ธ the rewrite prompt
Read my current instructions in [your-file.md] and the extracted Claude Fable 5 system prompt in claude-fable-5.md.

Rewrite my instructions using Anthropic's structural patterns:
1. Named sections with one job each.
2. Explicit decision rules (trigger plus action) for every tool and recurring choice.
3. At least one worked example per section, including one "what not to do".
4. Severity levels, so hard limits are clearly separated from soft preferences.
5. A short "critical reminders" block at the end repeating only the 3 rules that matter most.

Keep all of my original intent. Where my current instructions are ambiguous, list the ambiguity and ask me instead of guessing.

what to watch

About running it on open models

You will see people loading this prompt into open-weight models to make them behave more like Claude. The models named in the viral posts are real and genuinely good: GLM-5.2 by Z.ai (open weights, June 2026, huggingface.co/zai-org/GLM-5.2) and Kimi K2.7-Code by Moonshot AI (open weights, June 2026, huggingface.co/moonshotai/Kimi-K2.7-Code).

One honest note: a system prompt transfers instructions, not capability. Expect Claude-style structure and manners from this trick, not Claude-level intelligence. The patterns above are the part that upgrades every model you touch, including the ones you already pay for.
the waitlist is now open

AI System Club is launching soon

Build AI systems with me through recorded lessons you can follow at your own pace. Join the waitlist for first access and the founding price.

btw this list gets first dibs
the moment doors open :)