You'll finish with: A finished CLAUDE.md, under 200 lines, specific to you.
This is the hour that makes everything else work. In Claude Code it's a file called CLAUDE.md that loads automatically every session. In a chat project it's the custom instructions box. In Cowork it's the instructions field.
Counterintuitive, but Anthropic's own docs are clear: longer files eat context and Claude follows them less consistently. Aim under 200 lines. Write only what you'd otherwise re-explain.
If two people could disagree about whether Claude followed the instruction, it's too vague.
/clients/[name]/notes.md with the date"The clients section is where most files go soft:
The second produces completely different writing.
Same question, with and without the file
Depends which one you opened in the last chapter. It's the same box in each — just a different name.
In Claude Code the folder ends up looking like this:
A file ending in .md is a plain text file. Nothing special opens it — Notepad on Windows, TextEdit on a Mac, or the editor built into Claude. The .md just tells programs the text uses a few simple marks for headings and lists.
Two traps when you make one. Windows Notepad quietly adds .txt unless you set Save as type to All Files first. Mac TextEdit needs Format → Make Plain Text. If your file ends up called CLAUDE.md.txt, that's what happened — rename it and it will work.
Facing a blank page? Don't. The setup builder asks you these same questions one at a time and writes the file for you — then you edit a draft instead of starting from nothing. That is a much easier job, and it takes about twenty minutes. Come back here when you have it.
/init and it drafts one from your folder — otherwise create the file yourself.Open a brand new chat in that project and ask: "What do you know about my business?" It should tell you back, specifically, without you pasting anything.
If it answers vaguely or asks who you are, the file didn't load. In Claude Code, run /context and check CLAUDE.md is listed under Memory files.
# [Company] — Operating Context
## Who we are
[What the business does, who it serves, how it makes money.]
## Who I am
[Name, role, what you do daily, what you don't do.]
## Our clients
[Type 1] — the pain: [concrete, not abstract]
[Type 2] — the pain: [concrete, not abstract]
## What we sell
[Offer] — [what it's for, roughly what it costs]
We do NOT sell: [list it]
## How we talk
- [Voice rule]
- Banned words: [yours]
- Sounds like us: "[a real sentence]"
## Systems we run on
Invoicing: [tool] · CRM: [tool] · Email: [tool]
## Standing rules
- Never send anything to a client without showing me first
- Never quote a price I haven't confirmed
- Flag uncertainty instead of guessing