Scenario 2 of 6

Code Generation with Claude Code

Using Claude Code to accelerate development — generation, refactoring, debugging and documentation — integrated into a team's workflow through custom slash commands, CLAUDE.md configuration, and judgement about when plan mode beats direct execution.

Primary domains: Claude Code Configuration & Workflows · Context Management & Reliability

What this scenario tests

The most concretely testable of the six, because most of it reduces to knowing which file a setting belongs in. Questions describe a team whose conventions are not being followed, or a repository where one directory needs rules the rest does not, and ask where the fix goes: user memory, project memory, a path-specific rule, a skill, or a command. The plan-mode questions are judgement calls about the size and reversibility of the change.

Traps it is built to catch

Putting a team convention in user-level CLAUDE.md. It is not version-controlled and nobody else gets it — the symptom described in the question is precisely that teammates are not following the rule.
Reaching for plan mode on a single-file change with an obvious shape. Plan mode earns its overhead on architectural decisions, not on every edit.
Confusing a slash command with a skill. One is invoked explicitly by the user; the other loads when its description matches the request.

The most useful hour of preparation

Configure a real repository properly: a project CLAUDE.md with imports, a directory-scoped rule under .claude/rules/ with a glob, and one custom command with allowed-tools and argument-hint frontmatter.

Lessons that cover this scenario

6 of the 30 task statements, across 2 domains.