CCA-F start here · Trap gym · Where does this instruction live?

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

At a glance: Team rules go in the project CLAUDE.md, personal ones in ~/.claude/CLAUDE.md, rules for one kind of file spread across folders in .claude/rules with paths, a task you start yourself in a command, and a long procedure needed only sometimes in a skill.

Start here: notes in an office

Think of an office where people leave notes for each other.

Your own notebook. You read it every day, in every office you visit. Nobody else ever sees it. That's the place for your habits, not the team's rules.
The noticeboard by the door. Everyone who walks in reads it, every day, including the new hire and the auditor. Keep it short: only what applies to everyone, always.
A note taped to one cupboard. You read it only when you open that cupboard. Good for rules about what's inside. Clumsy if the same things are kept in three cupboards.
The binder on the shelf. Nobody reads it until they need it, such as the once-a-month procedure. Then it's there for anyone who asks.

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.

Your laptop only · not in git you, in every project; never teammates or CI ~/.claude/CLAUDE.md always ~/.claude/commands/ when you type it The repository · in git every teammate on clone, and every CI run CLAUDE.md (root) always @docs/….md loads with it server/CLAUDE.md, mobile/… in that folder .claude/rules/ + paths: matching file touched .claude/skills/*/SKILL.md when invoked .claude/commands/ when typed

Butter: always loaded. Pink: loaded when matching files are touched. White: loaded only on request.

The one question to ask: who must get this instruction, and when?

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.

1. The instruction
2. Where you put it

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

TrapWhat the wrong option looks likeWhy it's wrong
Right content, wrong reachTeam rules in ~/.claude/CLAUDE.md; a personal habit or /standup in the committed repoUser-level files are not in git, so teammates and CI never get them. Committed files reach everyone, wanted or not.
Right reach, wrong timingA monthly runbook in CLAUDE.md; always-on standards in a skill or commandCLAUDE.md loads every session and pays every time. Skills and commands wait to be asked, and people forget.
Folder where a pattern was neededA 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

Who needs it decides repo or home folder. When they need it decides always, by file pattern, or on request.

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).”

← All traps