In the code generation scenario, a development team uses Claude Code day to day to write, refactor and review code. Questions set here lean on the Claude Code configuration domain and the prompt engineering domain: how a team shares conventions, how risky work is planned, and how guarantees are enforced rather than requested.
The setup you should picture
A repository with a root CLAUDE.md that records build and test commands and code conventions, subdirectory CLAUDE.md files for parts of the codebase with their own rules, shared settings with permission rules committed to the repo, a few project commands or skills for routines the team repeats, and hooks that run formatters or block edits to protected paths. Each developer also has personal preferences in their own user-level files.
Decisions the exam probes
Shared versus personal. Team conventions and permission rules go in committed project files; personal preferences go in user-level files; personal overrides that should not be committed go in local settings. Many questions are simply "where should this live?"
Guidance versus enforcement. CLAUDE.md content is loaded into context and usually followed. Hooks and permission rules are enforced by the harness every time. If a rule must never be broken — no edits to migrations, formatting after every change — the answer is a hook or a deny rule.
Planning risky work. For a wide refactor in unfamiliar code, explore and plan first: plan mode lets Claude read and propose without changing files, and a human approves the approach before implementation begins.
Packaging repetition. A review routine typed many times a day should become a project command or skill that anyone can invoke by name, rather than text pasted into the chat or loaded into every session through CLAUDE.md.
Keeping context clean. Clear the session between unrelated tasks; compact a long session when the same task continues. Keep CLAUDE.md short so important rules are not drowned out.
Common traps
- Putting personal preferences in the team's committed CLAUDE.md.
- Relying on a memory-file sentence for a rule that must always hold.
- Letting a long CLAUDE.md accumulate meeting notes and history.
- Starting a broad refactor without an agreed plan.
- Using a post-edit alert where a pre-edit block was needed.
How to practise
Set up a small repository the way you would for a team of five: write the root and one subdirectory CLAUDE.md, commit a settings file with allow and deny rules, add a formatter hook and a hook that blocks one folder, and package one routine as a command. Then ask Claude Code to break each rule and see which mechanisms actually stop it.
The six scenarios are listed in Anthropic's official exam guide (version 1.1), with four drawn per sitting. The emphasis described here is our own study guidance, not official exam content.