CoursesClaude Code in Practice
Memory Files
The CLAUDE.md files: what they are, which one loads when, what earns a line, how to keep them short and free of conflicts, and how to find out why a rule was not followed.
- Lessons
- 7
- Exercises
- 39
- Minutes
- 42
- 1
What a Memory File Is
After this lesson you can say what a CLAUDE.md is, where each of its four locations applies, and why a rule in it is advice Claude reads rather than a lock.
Fill blankMultiple choiceTap - 2
Which File Loads When
After this lesson you can predict which memory files are in the window at launch, which join later when a file is read, and how imports and path-scoped rules change that.
DebugMultiple choiceTrace - 3
What Belongs in the File
After this lesson you can sort a bloated CLAUDE.md into what stays, what becomes a skill, what becomes a path rule, and what the code already says.
Fill blankMultiple choiceTap - 4
Short, Specific, Not Contradicted
After this lesson you can keep a memory file under 200 lines, write rules Claude can check, and clear a conflict between two files instead of hoping one wins.
DebugFill blankMultiple choice - 5
When Claude Ignores a Rule
After this lesson you can find out why a rule is not followed: not loaded, wrong place, too vague, contradicted, or a must-never that needs a hook. And you can tell auto memory from CLAUDE.md.
DebugMultiple choice - 6
Checkpoint: Memory FilesCheckpoint
Load order, imports, what belongs, conflicts and enforcement, in a repo you have not seen.
DebugMultiple choiceTrace - 7
Boss: Memory for Two TeamsBoss
One monorepo, two teams, one bloated file: split it, clear the conflict, check what each session loads, enforce the must-never, and hand it over.
DebugCode orderMultiple choiceTrace