Where does this instruction live?
Here the trap is the right content in the wrong home. Every option holds the same words; what changes is who loads them and when. A team rule in your own home folder never reaches a new hire. A monthly runbook in CLAUDE.md fills every session. Learn the homes, and these questions turn into a lookup.
D3 Claude Code ConfigurationExam guide 3.1, 3.2 and 3.3About 15 minutes
Start here: notes in an office
Think of an office where people leave notes for each other.
Claude Code has the same homes. Your notebook is ~/.claude/CLAUDE.md and ~/.claude/commands/. The noticeboard is the root CLAUDE.md (an @import just pins a second page to it). The cupboard notes are a folder CLAUDE.md, or a .claude/rules/ file whose paths: pattern says which files it is for, wherever they are. The binders are skills and slash commands: they load when someone asks.
Butter: always loaded. Pink: loaded when matching files are touched. White: loaded only on request.
- Only me, in every project:
~/.claude/CLAUDE.md(a habit) or~/.claude/commands/(something I run). - The whole team and CI, always: the root
CLAUDE.md. If the text already lives in a repo file,@importit rather than paste a copy. - One kind of file, wherever it sits:
.claude/rules/with apaths:glob such as**/*.test.tsx. - Everything in one folder: that folder's
CLAUDE.md. - Now and then, on request: a skill in
.claude/skills/or a command in.claude/commands/.
Words in the question that tell you which home
Who
- “every engineer”, “new hires”, “on clone”, “CI”: in the repo
- “only me”, “every repository I open”, “teammates don't want it”: home folder
When
- “every file”, “all code”: always loaded
- “files named …”, “spread across folders”: a
paths:rule - “once a month”, “when asked”, “not tied to a file”: a skill or command
- “fills the context”, “loads during unrelated work”: it's loaded too widely
Try it: six sessions
Pick an instruction, then pick a home for it. The simulator replays six sessions from one day in a repository with server/, mobile/, packages/shared/ui/ and scripts/db/, and shows what happened to the instruction in each. The diagram above marks the home you chose.
Token counts are illustrative, chosen to show the shape. They are not measurements. Which files load in which session follows the loading rules in exam guide 3.1–3.3.
Things to try: screen conventions + folder CLAUDE.md (the note sits on mobile/, the screen is in packages/shared/ui/), then + rules with paths. Then review criteria + ~/.claude/CLAUDE.md and watch the teammate and CI rows. Last, runbook + root CLAUDE.md against + project skill.
The three traps
| Trap | What the wrong option looks like | Why it's wrong |
|---|---|---|
| Right content, wrong reach | Team rules in ~/.claude/CLAUDE.md; a personal habit or /standup in the committed repo | User-level files are not in git, so teammates and CI never get them. Committed files reach everyone, wanted or not. |
| Right reach, wrong timing | A monthly runbook in CLAUDE.md; always-on standards in a skill or command | CLAUDE.md loads every session and pays every time. Skills and commands wait to be asked, and people forget. |
| Folder where a pattern was needed | A CLAUDE.md in mobile/ for screen files that also live in packages/shared/ui/ | A folder note loads only in that folder. A paths: glob follows the file type into every folder. |
Practice: three exam-style questions
Answer first, then open “Think it through”.
Rule to remember
Exam guide 3.1: “User-level is not shared via version control.” Exam guide 3.2: “Project commands in .claude/commands/ (shared) vs user ~/.claude/commands/ (personal).” and “Skills = on-demand task workflows; CLAUDE.md = always-loaded universal standards.” Exam guide 3.3: “Glob-pattern rules beat directory CLAUDE.md for conventions spanning directories (e.g., **/*.test.tsx).”