You’ve met four knobs this level. On their own, each is a small convenience. Together, they turn a generic tool into your tool — one that knows your project, remembers how you work, runs your favorite prompts on command, and stops pestering you about safe things.
Personalization compounds. The second hour with a configured Claude is worth more than the first, because every piece is pulling for you at once.
Let’s wire it up. This is a twenty-minute setup, and you already know how to do every step.
The four knobs, one more time
| Knob | Solves | Lives in |
|---|---|---|
| CLAUDE.md | Re-explaining the project every time | The repo (or ~/.claude for personal) |
| Memory | Re-explaining yourself every time | Privately, on your machine |
| Slash commands | Re-typing the same prompts | .claude/commands/ |
| Settings allowlist | Approving the same boring commands | .claude/settings.json |
Notice the pattern: every knob kills one kind of repetition. That’s the whole theme of this level — stop saying the same thing twice.
Your twenty-minute setup
- Write a
CLAUDE.mdfor a project you actually use — ask Claude in the chat or type it in the file pane. What it is, how to run it, two or three conventions Claude keeps missing. Five lines is plenty to start. - Add one personal preference — either to your
~/.claude/CLAUDE.mdor by just telling Claude (and letting it remember). Something like “explain your plan before big changes.” - Save one slash command you’d genuinely reuse. A
/reviewof your staged changes is a great first one. - Allowlist two commands you’ve approved a hundred times. Next time the permission ask pops up for
git statusorls, click “Allow always” instead of “Allow once” — the truly boring ones.
That’s it. Four small acts, and the tool fits you instead of the other way around.
Don’t try to perfect it today
Here’s the trap: people sit down to “configure everything” and burn an afternoon polishing a setup before they’ve felt what’s missing. Don’t.
Build your setup the way you’d break in a pair of boots — a little at a time, as you go.
The best CLAUDE.md lines are the ones you add the third time you explain the same thing. The best commands are the prompts you’re already tired of typing. Let your setup grow from friction — every time something annoys you twice, that’s the signal to write it down. A config that grows this way actually fits, because every line earned its place.
What’s next
You’ve nailed four knobs. There’s one more dial on the same panel — one that most people never touch — and it might be the highest-leverage of all: the model itself.