A new engineer reports that the agent never adds the team's required license header or uses the internal logging wrapper when it generates boilerplate, although it does both reliably for everyone else. You find that the tech lead wrote these conventions in ~/.claude/CLAUDE.md on their own machine. What is the right fix?

Answer: C — Move the conventions into the project-level CLAUDE.md committed to the repository, then confirm with /memory that the new engineer's sessions load it.

User-level ~/.claude/CLAUDE.md applies only to that user and isn't shared through version control. Team conventions belong in project-level configuration, and /memory shows which memory files are actually loaded. (a) copies the file by hand, and the copies will drift and have to be redone for every new hire. (b) relies on someone remembering to do it every session. (d) covers skill invocations only, puts standards meant to apply everywhere into on-demand skills, and duplicates them across files.