Domain 3 of the exam asks: where do you put an instruction so that Claude Code actually follows it, and who else gets it? There are about seven different places you can put one, they behave differently, and the exam questions are almost entirely about choosing between them.
You scored 11 out of 12 on those questions — but you told me you don't have a grip on them, and I believe you, because your machine has never had a single one of these files on it. You recognised the right answers. That's fragile. This lab makes you create each one and watch what it does, which takes about an hour and makes the whole domain concrete.
Everything in Domain 3 sorts along three questions. If you can fill in this table from memory, you can answer almost any D3 exam item — because the questions are always a scenario that fixes two columns and asks you to pick the row.
| Mechanism | Where it lives | Does a teammate get it on git clone? |
When is it loaded? | Can it restrict tools? |
|---|---|---|---|---|
User memory~/.claude/CLAUDE.md |
Your home folder — outside any repo | No — never in version control | Always, in every project | No |
Project memoryCLAUDE.md in the repo root |
The repository | Yes | Always, in this project | No |
Directory memorysubdir/CLAUDE.md |
A subfolder of the repository | Yes | Always, when working in that subtree | No |
Path rules.claude/rules/*.md |
The repository | Yes | Only when the file you're editing matches a path pattern | No |
Slash command.claude/commands/name.md |
Repo (shared) or ~/.claude/commands/ (personal) |
Yes, if in the repo | Only when you type /name | No |
Skill.claude/skills/name/SKILL.md |
Repo (shared) or personal | Yes, if in the repo | Only when invoked | Yes — allowed-tools |
Permissionssettings.json |
Repo or your home folder | Yes, if in the repo | Always — and enforced, not merely followed | Yes — this is the control |
Memory files load on every single turn, so anything you put there is a permanent tax on context. Commands and skills load only when invoked. Path rules load only when a matching file is touched. A question that complains "our CLAUDE.md is 900 lines and Claude cites React rules while editing Go" is complaining about exactly this.
Anything inside the repository is shared through git. Anything in ~/.claude/ is yours alone and
version control will never distribute it. A question saying "every developer must have this on clone" has one
answer; "one engineer is trialling this" has the other.
key: value notation where indentation
creates nesting and a leading dash makes a list item. You'll write about four lines of it in this lab.
---
paths:
- "**/*_test.go"
---
Everything below the dashes is the actual content.* matches anything within one folder level;
** matches across any number of folder levels.
So **/*.test.tsx means "any file ending in .test.tsx, anywhere in
the project, however deeply nested." That "anywhere" is the whole point — it's why a glob can express a rule
that no single folder could./something. Two kinds, and the exam cares about the difference:
built-in ones that ship with Claude Code (/memory, /compact,
/config), and custom ones you create yourself by dropping a Markdown file into a
commands/ folder. A custom command is just a saved prompt.settings.json saying which tools Claude may use and on which paths. Enforced by the
program itself, not by Claude's cooperation. This is the only mechanism on the table that can actually
guarantee something.-p and it prints an answer and exits, with no interactive prompting. This is how it runs
inside CI.
CI = the automated system that runs checks on every pull request. There's no human
at a keyboard, so anything that waits for input hangs forever. That's a whole exam question.You've used Claude Code only through the VS Code panel, so here is exactly what to do — no assumed steps.
~/cca-f-lab when we set this up. It's a
throwaway with a few fake Go and TypeScript files — nothing real, nothing connected to any of your projects,
and it is not pushed anywhere.cca-f-lab. Open it in a new window, not added to your current workspace.
cca-f-lab is a sub-folder of a
bigger workspace, you'll be observing the wrong thing all the way through./memory and press enter. You should see very
little: no project memory, because you haven't created it yet. That empty result is your baseline — Exercise 1
is about watching it change.CLAUDE.md in your home folder (~/CLAUDE.md — the one describing
CostIntelligence1 and your other projects). Because cca-f-lab sits inside your home
folder, /memory may well list that file too.
Each exercise has a green What to look for box, and the honest difficulty is that most of these mechanisms are invisible — nothing announces "I have loaded a rule." So the lab uses three tricks, and it's worth knowing them up front:
Ask the program, not yourself. /memory lists what is actually loaded right now. When you
are unsure whether a file took effect, this settles it in two seconds. In the exam, "run /memory"
being the correct answer to a confusion about conflicting conventions is exactly this reflex.
Set up a contradiction, then see which side wins. If two files give opposite instructions and Claude follows one of them, you have directly observed precedence. This is why Exercise 1 has you write conflicting rules on purpose — a single rule that gets followed teaches you nothing, because it might have done that anyway.
Test the negative case. Every rule test needs two trials: a file that should trigger it, and one that shouldn't. If the convention shows up in both, the scoping isn't doing anything and you've learnt something more useful than if it had worked.
| Part | Exercises | Time | What it settles |
|---|---|---|---|
| A — Memory | 1, 2, 3 | ~30 min | Where instructions live, who receives them, and when they load. The largest slice of D3. |
| B — Invocable things | 4, 5 | ~25 min | Commands vs skills, and the two frontmatter fields that separate them. |
| C — How work proceeds | 6, 7, 8 | ~35 min | Plan mode, headless CI, and guidance vs enforcement. |
If you only have time for three: do 2, 5 and 8. Path globs, skill frontmatter, and permissions-versus-instruction are the three ideas that carry the most exam weight and are hardest to absorb by reading.
When you're done, re-sit the twelve D3 items in Mock Exam #4 — Q11–Q16, Q38–Q39, Q41–Q44. The test isn't whether you get them right again; you already did. It's whether you can now say why each wrong option is wrong. That's the difference between recognising an answer and knowing one.
The lab has you add a few things to your real home folder — that's deliberate, since seeing the user-level layer behave differently from the project level is half the point. Remove them when you finish:
rm -rf ~/cca-f-lab
rm -f ~/.claude/commands/rfc-mine.md
# then edit ~/.claude/CLAUDE.md and delete the block marked "CCA-F LAB"
Your existing ~/CLAUDE.md and
~/.claude/settings.json are untouched by all of this.