CCAR-F practice › Claude Code Configuration & Workflows · Question 48 of 105
Claude Code Configuration & Workflows
A new engineer reports that Claude Code ignores the team's API naming conventions in their sessions. The tech lead who set up Claude Code for the team sees the conventions applied every time. Both are on the latest main branch. What is the most likely root cause?
Show answer and explanation
Answer: B — The conventions live in the lead's ~/.claude/CLAUDE.md, which git never shares
User-level instructions in ~/.claude/CLAUDE.md apply only to that user and are not part of the repository, so a teammate who clones the repo never receives them. Moving the conventions into the project-level CLAUDE.md (or .claude/rules/) and committing it fixes the problem for everyone. (A) doesn't explain a consistent difference between two users. (C) misreads the hierarchy. (D) describes a mechanism that doesn't exist.
Keep going
More Claude Code Configuration & Workflows questions
- For the same developer on the same branch, Claude follows the repository's logging…
- Your project CLAUDE.md holds the team's naming conventions plus a 15-step release…
- A team's /analyze-deps skill reads dozens of files and prints a detailed report on each…
- A team's /scaffold-tests skill should only create test files and must never run shell…
- A senior engineer wants the team's shared /review skill to apply her own extra security…