CCAR-F practice › Claude Code Configuration & Workflows · Question 46 of 105
Claude Code Configuration & Workflows
A monorepo has one root CLAUDE.md that three package teams keep editing to add build steps that apply only inside their own package. Merge conflicts on the file now happen weekly. What is the most appropriate fix?
Show answer and explanation
Answer: C — Move each team's steps into a CLAUDE.md inside that team's package directory
Directory-level CLAUDE.md files hold instructions that are true only for one subtree, on top of the project-level file. Each team then edits its own file, which removes the conflicts and keeps other packages' steps out of unrelated sessions. (A) keeps everyone editing one file. (B) uses user-level files, which are never shared through version control. (D) duplicates the project-wide content, and the copies will drift.
Keep going
More Claude Code Configuration & Workflows questions
- A 1,200-line root CLAUDE.md mixes testing, API, deployment, and frontend standards…
- A new engineer reports that Claude Code ignores the team's API naming conventions in…
- 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…