CCARF Practice Question

Paper 3 · Question 11

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. You have a personal /scratch-notes slash command you use constantly, but it reflects your own workflow and should not appear for teammates when they pull the repository. Where does the command file belong?

• A.In .claude/commands/ in the repository, like all slash commands
• B.In the root CLAUDE.md under a # Commands heading
• C.In ~/.claude/commands/ in your home directory, where user-scoped commands live outside version control
• D.In .claude/rules/ with a paths glob matching your username

Show answer & explanations

Correct answer: C

A: publishes a personal tool to the whole team

B: is project context, not a command definition mechanism

C: Command scoping mirrors intent: ~/.claude/commands/ holds personal commands visible only to you, while .claude/commands/ in the repo is shared with everyone via version control. A personal workflow tool belongs in the former.

D: misuses path-scoped rules, which condition on edited file paths, not identity

Related Claude Code Configuration & Workflows questions

More: Paper 3 · All practice questions