Charlie HillsFree guide · Claude & Claude Code
Clean up your Claude setup with Fable 5.2: The 3 prompts
Three prompts that make Fable 5.2 measure everything Claude loads before you type, find the rules that contradict each other, then fix it one change at a time. Plus where every new rule should go.
Charlie Hills Added 13 November 2026 · Free
What’s inside
- 1The run order
- 2Measure what loads
- 3Find the rules that fight
- 4Fix it, then prove it
- 5Give every new rule a home
- 6When something doesn't work
- 7What to do today
The run order
|
Step |
What it does |
Changes anything? |
Time |
|
1. Measure what loads |
Shows everything Claude reads before you type, biggest cost first |
No |
About 10 minutes |
|
2. Find the rules that fight |
Turns every clash into a yes or no question |
No |
About 10 minutes |
|
3. Fix it, then prove it |
Backs up, makes one change at a time, re-tests |
Yes, after your answers |
About 20 minutes |
|
4. Give every new rule a home |
Keeps it clean from now on |
Only what you add |
Ongoing |
Step 1: Measure what loads
Open Claude Code in your home folder (the one your .claude folder sits in) and pick Fable 5.2. Then paste this:
Audit my Claude setup before you change anything. This first pass is read-only: report in the chat and edit nothing.
1. Run claude -p "/context" in this folder. Show me everything that loads before I type a word: my CLAUDE.md files, my memory, the skills list, my connectors and Claude Code's own text, with the tokens for each. If it won't run, estimate from file sizes (4 characters is about 1 token) and label it an estimate.
2. Skills: how many are listed, and how many show only a name with no description because the list ran out of room.
3. Hooks: list every hook in my settings, what sets it off and what it does. Flag any that add text to every message, any that point at a file that no longer exists, and any that have never been tested.
4. Real use: read my last 30 days of sessions in ~/.claude/projects/. Tell me the typical tokens carried per reply, the share of replies over 150,000 tokens, my 10 most-read files with their sizes, and every skill, connector and hook I never used.
Finish with one table, biggest cost first.What you should get back, and the check
One table, biggest cost first: your rules file, memory, skills list, connectors and Claude Code's own text, each with a number. Then a list of skills that show only a name, any automations (hooks) that fail or never run, and the tools you never use.
The check: look at the skills line. If a lot of your skills show "name only", Claude can't see what they do, so it can't pick the right one. That's the first thing to fix. Watch for the same connector added more than once too.
That’s the first part. The rest of this guide is free too.
