Capstone: get a repository ready for a new teammate
No walkthrough this time. A teammate starts Monday and gets only what is in git — the brief says what the team needs; you choose how to build every part of it.
01The setup
Use the repository you have been shaping through this level — skills, memory, settings, hooks, agents all welcome — with a clean working tree and a test command that passes. Nothing here needs a new repo; the capstone is the repo you already have, finished. If you want the upstream practice template and its automated checks for this capstone, Wesam’s repo ships exactly this task with a checker — link below.
02The brief
A teammate starts Monday. They will clone the repository, open Claude Code, and their sessions should work the way the team’s do — with nothing but what git gives them. Everything you built in this level had a personal half (settings.local.json, local-scope servers, plugins installed for you) and a committed half. The capstone is the committed half, complete.
- 01A skill the teammate can run by name on their first day — the checker, the deploy notes, whatever this repo repeats — that also loads on its own when a request matches it (lesson 1).
- 02Memory that pays its way: CLAUDE.md importing a real document, and the testing conventions in a scoped rule under .claude/rules/ that loads only when test files are touched (lesson 2).
- 03Team settings in the committed .claude/settings.json: deny reading .env and .env.*, allow exactly the one test command — and the sandbox turned on for everyone, "sandbox": {"enabled": true} in the shared file, since /sandbox writes only to your personal one (lesson 4).
- 04A PreToolUse hook for Edit and Write that blocks the folder your tests depend on fixture-exact — samples/, or yours — and nothing else (lesson 5).
- 05A reviewer subagent with read-only tools, committed under .claude/agents/ (lesson 6).
- 06The MCP server your team actually uses — or Chrome DevTools MCP if none yet — in a committed .mcp.json, pinned, data flows off (lesson 7).
- 07One plugin from an Anthropic marketplace, enabled for the project in committed settings — and the install command a teammate runs once, written down where they will find it, in the README or CLAUDE.md (lesson 8).
03The proving session
Then prove it the way Monday will experience it. Start a session and try each part: run the skill by name; ask for an edit inside the protected folder with the Edit tool by name and watch it bounce; delegate a review to the subagent; approve the MCP server and use one of its tools; run the test command without a prompt. Pick the model and effort for each job as the diagnosis table says, not out of habit. Commit everything, run the tests one last time, and leave git status clean — the repo a teammate clones is the repo you just finished.
Every box ticked is the Intermediate exit. Installment 3 — Advanced — picks up exactly here: several sessions at once, work nobody watches, a setup a whole team runs, and bounds on every run that works alone.
Why does the capstone put the sandbox in the shared settings file?
- A/sandbox writes only to your personal file, which teammates never get
- BThe sandbox cannot be enabled per-person
- CLocal settings are ignored in git repos
→Check your answer
The command saves to .claude/settings.local.json — yours, uncommitted. For everyone, the key goes in the committed file by hand.
A teammate pulls your finished repo. What do they still run once, by hand?
- AEvery skill, to register it
- BThe hook scripts, to make them executable
- Cclaude plugin install <plugin>@<marketplace> --scope project, for the enabled plugin
→Check your answer
The committed entry turns the plugin on; the bits are fetched per machine. Skills, hooks and agents need nothing — git already carried them, permissions included.
The one-line difference between this level and Beginner…
- ABigger prompts
- BThe project now enforces what CLAUDE.md could only suggest
- CFaster models, always
→Check your answer
Beginner made one change safe. Intermediate moves the guardrails into the repository — hooks, scopes, sandbox — so the safety survives your absence. That is what Monday inherits.