ux-scenarioslisted

# ux-scenarios — Maintain the Scenario Base > Part of **super-ux** — see [system-map.md](references/system-map.md) > for the whole pipeline and the four sync rules. After changes, run the > linter (`python3 docs/ux/lint.py`). AI-generated interfaces go bad when UI is built without a model of user behavior. This skill keeps one: `docs/ux/scenarios.md` in the target project is the source of truth for everything the user can do, see, and hit — every feature, every button, every state, every error, every result. **Format contract:** [scenario-format.md](references/scenario-format.md) (ux-contract v4). Read it before writing or editing scenarios. Never deviate from its field names, ID rules, statuses, or checklists. **The WHY and HOW layers:** when `docs/ux/foundation.md` exists (personas, JTBD, journeys, stories — `ux-foundation` skill) and/or `docs/ux/flows.md` (task analysis, user flows — `ux-flows` skill), scenarios are derived FROM them: one scenario set per flow, covering the happy path, every error edge, and every alt branch of the flow diagram; `Traces:` filled with story + flow IDs; traceability rules enforced (every must/should story covered; every flow node/edge covered; every scenario serves a story or job — a scenario serving nothing is a candidate for deletion, not implementation). Steps are written use-case style: user action -> observable system response. If the upper layers are missing on a non-trivial product, recommend `ux-foundation` → `ux-flows` first; pr