Lite is free. Pro adds the quality layer on top.
Write a CLAUDE.mdthat works.
A short file of standing instructions is read at the start of every session. Make each line earn its place.
// the steps
Six steps
01 Say what the project isTwo lines: what it does and the stack. This saves the AI from guessing.
02 List the commandsHow to install, run, test and build. Commands the AI can copy exactly are the most useful lines.
03 State the rules that matterThe few things that must always hold: a style rule, a folder not to touch, a language for copy. Be specific.
04 Leave out the obviousDo not explain what the AI already knows. Long files dilute the lines that count.
05 Treat it as guidanceThe file is context, not enforcement. For a rule that must never be broken, use a check that blocks the action.
06 Prune it every monthDelete lines that no longer apply and add the correction you keep repeating. A short current file beats a long stale one.
// with adams
Where Adams fits
Rules that come from your correctionsProCoach in Pro turns the corrections you repeat into short rules every session receives, and lets you keep, forget or add one. It complements a CLAUDE.md file rather than replacing it.
// faq
Questions
How long should it be?
Short enough to read in two minutes. Aim for under a page.
Can I have more than one?
Yes. Claude Code reads files in your project and your user folder. Use the project file for the project and the user file for habits.
Does the AI always follow it?
Not always. It is context. Use a hook or a check for rules that must never fail.
// related