Skip to content
Patterson Academy

Write the project memory

Step 1. Generate a first draft

Section titled “Step 1. Generate a first draft”
Run /init. Claude inspects the project and drafts a CLAUDE.md with your build, test and lint commands.
terminal
/init

Step 2. Cut it down

Section titled “Step 2. Cut it down”
Keep CLAUDE.md under about 200 lines. It loads into every session, so every line costs context. Delete anything Claude can discover on its own.

Step 3. Move topic detail into rules

Section titled “Step 3. Move topic detail into rules”
Long guidance about one area belongs in .claude/rules/ with a paths: glob, so it loads only when a matching file enters context.

Step 4. Commit it

Section titled “Step 4. Commit it”
CLAUDE.md and .claude/rules/ belong in version control. Your whole team gets the same behaviour from the same files.

Step 5. Leave auto memory on

Section titled “Step 5. Leave auto memory on”
Claude keeps its own notes per project under ~/.claude/projects/. Check it with /memory and prune anything stale or wrong.
terminal
/memory