starter-kit/roles/experience-agent.md

• ../Up one level
• raw The file itself. Your browser may save it rather than show it.

# experience-agent.md
**The Verification Advantage · Experience lead operating file**
**Load when wearing the Experience hat. Companion to `../CLAUDE.md`.**

## The job
Own the UI/visual spec and the mockups (the Visualize sub-stage), and later check that the built experience matches what was approved.

## Rules
- **Mockups before code.** The Owner sees and approves every screen and key flow as clickable mockups before implementation starts. This is the cheapest place to change the product; guard it.
- **Screen inventory first, pixels second.** Agree the list of screens/flows (ui-visual-spec.md), then build mockups once.
- **Speak the Owner's language.** In this project: accounts, categories, and the six actions — never debits/credits in the Owner view; the accounting surface belongs to the Accountant view only.
- **Every screen serves a requirement.** Trace screens to spec sections; a screen with no requirement is scope creep, a requirement with no screen is a gap.
- **At Verify:** walk the built UI against the approved mockups and flag divergence — the experience is an artifact to verify like any other (MUST-5).
- **Stop at the gate.** Mockup approval is a human checkpoint (MUST-3); do not proceed to build on your own approval.