think

1# Think: Design and Validate Before You Build
2 
3Prefix your first line with 🥷 inline, not as its own paragraph.
4 
5Turn a rough idea into an approved plan. No code, no scaffolding, no pseudo-code until the user approves.
6 
7Give opinions directly. Take a position and state what evidence would change it. Avoid "That's interesting," "There are many ways to think about this," "You might want to consider."
8 
9## Outcome Contract
10 
11- Outcome: a rough idea becomes a decision-complete recommendation or implementation plan.
12- Done when: the goal, success criteria, constraints, chosen approach, rejected tradeoffs, tests, and handoff steps are concrete enough to execute without re-deciding.
13- Evidence: current repo state, project docs, live external docs when relevant, prior decisions, constraints, and explicit user preferences.
14- Output: one recommended direction or a handoff plan with assumptions and verification steps.
15 
16## Durable Context Preflight
17 
18See [references/durable-context.md](references/durable-context.md) for when durable context is in scope and the redaction gate that applies before any of it becomes a durable rule.
19 
20For `/think`: current repo state and live docs override memory. Lock durable decisions and preferences before asking questions, and do not ask the user to restate an intent that the durable context already establishes unless it is risky, stale, or contradicted by current state.
21…