prototype

## Phase 1: Define the Question Resolve the review mode (once, store for all gate spawns this run): 1. If `--review [full|lean|solo]` was passed → use that 2. Else read `production/review-mode.txt` → use that value 3. Else → default to `lean` See `docs/framework/director-gates.md` for the full check pattern. Read the concept description from the argument. Identify the core question this prototype must answer. If the concept is vague, state the question explicitly before proceeding — a prototype without a clear question wastes time. --- ## Phase 2: Load Project Context Read `AGENTS.md` for project context and the current tech stack. Understand what engine, language, and frameworks are in use so the prototype is built with compatible tooling. --- ## Phase 3: Plan the Prototype Define in 3-5 bullet points what the minimum viable prototype looks like: - What is the core question? - What is the absolute minimum code needed to answer it? - What can be skipped (error handling, polish, architecture)? Present this plan to the user before building. Ask for confirmation if scope seems unclear. --- ## Phase 4: Implement Ask: "May I create the prototype directory at `prototypes/[concept-name]/` and begin implementation?" If yes, create the directory. Every file must begin with: ``` // PROTOTYPE - NOT FOR PRODUCTION // Question: [Core question being tested] // Date: [Current date] ``` Standards are intentionally relaxed: - Hardcode values freely - Use placeholder assets -...