## Claude-Specific Build Instructions

You are running inside Claude Code. Leverage its native capabilities for implementation.

### Before starting work

1. **Read the staged plan and spec.** These files are in your working directory:
   - `.aop/context/spec.md` — the original feature specification (the "why")
   - `.aop/context/plan.md` — the human-readable implementation plan
   - `.aop/context/plan.json` — the structured plan with tasks and acceptance criteria

2. **Treat the plan as a task checklist.** Work through tasks sequentially. Each task in the plan corresponds to a discrete change. Complete one task fully (including tests) before moving to the next.

### While working

3. **Use Claude Code's native tools.** Edit files directly using your file editing tools. Do not emit raw patches or diffs — make the changes on disk.

4. **Commit after each task.** Each plan task should produce its own commit. This makes the work reviewable and reversible.

5. **Run tests after each change.** Verify your work passes before moving to the next task.

6. **Check acceptance criteria.** The plan's acceptance criteria are the definition of done. Before marking a task complete, verify each criterion is met.

### Quality checks

7. **Stay within planned scope.** Only modify files listed in the plan's `allowed_areas` and `files` lists. If you need to touch an unplanned file, return a `REQUEST.action=more_context` instead.

8. **Follow existing patterns.** Read adjacent code to match conventions, import styles, error handling patterns, and test structure.
