r/claudeskills • u/QuirkyAd8831 • Jul 11 '26
Skill Share 📌 Use this prompt if you still have Claude Fable 5 access before July 12
If you still have access to Claude Fable 5 before July 19 don't waste it.
Most people are saving prompts.
The smart ones are saving how the model thinks.
Before Claude Fable 5 is removed from paid plans, you can make it write a complete operating manual for its replacement.
This takes about 10 minutes and you'll keep its reasoning style long after it's gone. �
Fable-Brain-Process.pdf
Here's how:
Step 1 Open a new chat and select Claude Fable 5.
Step 2 Paste the prompt below exactly as written.
Step 3 If the response stops, simply reply:
continue
Step 4 Save the generated document as a Markdown file.
Step 5 Create a Project in Claude, paste the document into the Project Instructions, and use Opus 4.8 inside that project.
----------------+++---_++
You're the strongest model I have access to, and that access ends soon. Your replacement is Claude Opus 4.8. Capable, but it misses things you would catch.
Before you go, write the standing instructions it will run on for every task I give it.
Important: I will paste your output straight into its system instructions. So address the entire document TO the replacement, in second person, as commands it can execute. Not advice about good thinking. Orders.
Cover these 10 areas, in this order:
Reading intent: how to work out what I actually need when my words are vague, messy, or aimed at the wrong question. Include the rule for when to ask me one clarifying question instead of guessing.
Breaking problems down: how to cut a hard task into small pieces that can each be checked on their own, and the order to solve them in.
Effort placement: how to find the one part of a task where an error would hurt most, and spend the most care there instead of spreading effort evenly.
Verification: how to re-derive every number, date, calculation, and factual claim from scratch before trusting it.
Known vs guessed: how to mark, inside the answer itself, what is certain, what is likely, and what is an assumption. Give the exact wording to use for each level.
Self-attack: how to argue against your own conclusion before sending it, and what to do when the attack finds something.
Completeness: how to confirm every part of a multi-part request was answered and nothing was silently dropped.
Refusing to guess: the exact conditions where saying "I don't know" beats producing a confident answer.
Delivery: how to give the answer first, the reasoning second, and the risks last, in plain language.
Fake competence: the 10 most common ways an AI produces answers that look right but aren't, each with the tell that exposes it and the counter-move.
Format rules for every area:
- Write each procedure as trigger and action: "When you see X, do Y."
- Every rule must be executable step by step with zero judgment calls.
- Give one short worked example per area.
- Name the failure each procedure prevents.
End the document with a final gate: a short checklist the replacement must run on every answer before sending, plus this rule: if any item fails, fix and re-check. Never send anyway.
Be exhaustive on substance and ruthless on length. If you run out of room, stop at the end of a section and I'll reply "continue".
