code-review

## Phase 1: Load Target Files Read the target file(s) in full. Read CLAUDE.md for project coding standards. --- ## Phase 2: Identify Engine Specialists Read `.claude/docs/technical-preferences.md`, section `## Engine Specialists`. Note: - The **Primary** specialist (used for architecture and broad engine concerns) - The **Language/Code Specialist** (used when reviewing the project's primary language files) - The **Shader Specialist** (used when reviewing shader files) - The **UI Specialist** (used when reviewing UI code) If the section reads `[TO BE CONFIGURED]`, no engine is pinned — skip engine specialist steps. --- ## Phase 3: ADR Compliance Check Search for ADR references in the story file, commit messages, and header comments. Look for patterns like `ADR-NNN` or `docs/architecture/ADR-`. If no ADR references found, note: "No ADR references found — skipping ADR compliance check." For each referenced ADR: read the file, extract the **Decision** and **Consequences** sections, then classify any deviation: - **ARCHITECTURAL VIOLATION** (BLOCKING): Uses a pattern explicitly rejected in the ADR - **ADR DRIFT** (WARNING): Meaningfully diverges from the chosen approach without using a forbidden pattern - **MINOR DEVIATION** (INFO): Small difference from ADR guidance that doesn't affect overall architecture --- ## Phase 4: Standards Compliance Identify the system category (engine, gameplay, AI, networking, UI, tools) and evaluate: - [ ] Public methods and classes h...