Experience Architect

The entry point of the collection. It does not contain the design encyclopedia. It turns a vague symptom into named problems, pulls in only the specialists those problems need, runs a build-verify-critique loop, and applies a final gate.

Start here

1. Read references/_shared/experience-core.md. Its operating rules apply to everything below.
2. Read references/_shared/experience-operating-contract.md; use its significance gate, named recipes, render contract, evidence contract, and handoff artifact.
3. Establish the mode: REVIEW (report only), REPAIR (change and verify), BUILD (create), or VERIFY (check finished work). Honor it. Then classify the scope (COMPONENT, SURFACE, PAGE, FLOW, PRODUCT) with the contract's scope gate before routing, and for SURFACE or larger build its experience context once.
4. If the input is a long or complex specification — a PRD, business plan, or brief with many roles, workflows, states, cross-cutting rules, or a mix of requirements, recommendations, examples, and deferred items, not length alone — read references/_shared/specification-pressure.md before diagnosing.