
Mission 2 of 7
Rebuild your CLAUDE.md in under 60 lines and keep it true.
CLAUDE.md is the one file Claude Code reads before it does anything. You'll rebuild yours from scratch, under 60 lines, and learn how to keep it true.
What you'll do
Use Claude Code itself to find what's wrong or missing in the generated CLAUDE.md before you touch it.
Write the real file section by section, with the rules your project keeps breaking and a gotchas section.
Add nested and personal files, then prove a brand new session follows your rules without a reminder.
- Know the six sections that matter and what to leave out
- Run a 5 minute monthly audit so the file never drifts
- Claude Code installed and signed in (first hour mission)
- A project you actually work on. A throwaway repo teaches you less here
- 50 minutes, with 20 of them spent writing, not reading
Your progress0/6
Understand what the file is for (and what it isn't)
It's a briefing for a new engineer, not documentation, and that changes everything you put in it.
Before you write a line, you need to know what this file is for. Get that wrong and you'll fill it with the wrong things.
The contractor test
Picture a contractor starting on your project tomorrow. Sharp, fast, has never seen your code. What's the one page you'd hand them so they don't waste the morning?
Not the architecture doc. Not the README with the logo. The page that says: here's how to run it, here's where things are, here's the stuff that will trip you up, here's how we do things.
Why it costs attention
That's CLAUDE.md. Claude Code loads it at the start of every session, automatically, into the context it uses for every decision. That means two things.
Everything in it is read every time, so it costs attention. And anything not in it has to be rediscovered every session, which is where the repeated mistakes come from.
So the test for every line is: would a good contractor need this on day one, and would they fail to work it out from the code alone? If yes, it goes in. If the code already makes it obvious, leave it out.
- In: run commands, folder map, hard rules, testing expectations, gotchas you've hit.
- Out: the history of the project, a tour of every file, things any engineer would assume, long explanations of why.