Exercise 3 — Solution

Task: A user works on this website project in the morning and on a
completely unrelated Node.js API project in the afternoon. Which of
this chapter's own four global-file examples (explanation style,
prompting feedback, utility scripts folder, "conversation" command)
would still be in effect during the afternoon session, and why?

All four would still be in effect during the afternoon session on the
unrelated Node.js API project.

Why: all four examples live in ~/.claude/CLAUDE.md, the global file,
which the chapter states explicitly applies "across every project,
regardless of which directory Claude Code is started in." None of the
four examples depend on anything specific to the morning's website
project - explaining mistakes with what-went-wrong-plus-how-to-avoid,
welcoming direct prompting-style feedback, saving general-purpose
scripts to one particular folder, and the "conversation" transcript
command are all preferences about how this specific USER wants to work
with Claude, not facts about the website codebase itself. Since the
global file is read the same way no matter which project Claude Code
is currently working in, the afternoon session on the Node.js project
would see the identical four instructions as the morning session did.

What would NOT carry over is anything from this repository's own
local CLAUDE.md - the @rules/ include list, the Key Paths table, and
every rules file they pull in (permanent_rules.md, language_rules.md,
etc.) - since none of that is loaded at all once Claude Code is
working in a different repository entirely.

Notes:
- This is the practical, lived version of the chapter's own
  compare-table row: "Applies where: Every project, everywhere" for the
  global file versus "Only inside this repository" for the project
  file.
- The "conversation" command is actually a good concrete illustration
  of this in action - its own instructions explicitly describe two
  different save locations depending on whether the current directory
  is inside a project with its own CLAUDE.md or not, which only works
  correctly because the command's own definition lives in the global
  file and is available everywhere to make that distinction.