CCARF Practice Question

Paper 3 · Question 15

D3 Claude Code Configuration & Workflows · Paper 3

[Scenario 2: Code Generation with Claude Code] Your team uses Claude Code for code generation, refactoring, debugging, and documentation, integrated into daily development with custom slash commands and CLAUDE.md configuration — and you must judge when plan mode beats direct execution. The project's CLAUDE.md has grown to 2,000 lines covering testing, API conventions, deployment, and styling; sessions load it all regardless of task. What is the recommended reorganization?

• A.Delete the file and rely on the model's general knowledge of good practice
• B.Move everything to each developer's user-level CLAUDE.md
• C.Split it into focused, topic-specific files in .claude/rules/ (e.g., testing.md, api-conventions.md, deployment.md), adding path-scoped frontmatter where conventions apply only to matching files
• D.Convert the entire file into a single slash command developers run manually

Show answer & explanations

Correct answer: C

A: abandons hard-won project conventions

B: unshares team configuration and guarantees divergence

C: The .claude/rules/ directory is the modular alternative to a monolithic CLAUDE.md: focused topic files, with YAML path scoping where rules should load only for matching files — less irrelevant context, easier maintenance.

D: makes always-relevant standards opt-in and forgettable

Related Claude Code Configuration & Workflows questions

More: Paper 3 · All practice questions