CCAR-F practice › Claude Code Configuration & Workflows · Question 47 of 105
Claude Code Configuration & Workflows · Select TWO
A 1,200-line root CLAUDE.md mixes testing, API, deployment, and frontend standards. Package maintainers say most of it is irrelevant to their code, and edits from different teams keep colliding. Which two changes best address this? Select two.
Show answer and explanation
Answer: A and D — Split the file into focused topic files in .claude/rules/, such as testing.md and deployment.md / Keep each standard in its own file and @import only the relevant ones in each package's CLAUDE.md
Both are modular alternatives to a monolithic CLAUDE.md. Topic files in .claude/rules/ give each area its own home, and @import lets each package's CLAUDE.md pull in only the standards its maintainers know apply. (B) moves team standards into user-level files that teammates never receive. (C) makes always-applicable standards depend on someone remembering to invoke a skill.
Keep going
More Claude Code Configuration & Workflows questions
- 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…
- A team's /scaffold-tests skill should only create test files and must never run shell…