ux-foundationlisted

# ux-foundation — The WHY Layer > Part of **super-ux** — see [system-map.md](references/system-map.md) > for the whole pipeline (foundation → flows → screens → scenarios → audits > → plans) and the four sync rules. After changes, run the linter > (`python3 docs/ux/lint.py`). Interfaces fail when built without knowing WHO uses them and WHY. This skill maintains `docs/ux/foundation.md`: **Personas → Jobs to Be Done → Customer journeys → User stories.** Scenarios (`ux-scenarios` skill) are built on top and trace to these IDs — the full chain gives every scenario its context. **Format contract:** [scenario-format.md](references/scenario-format.md) (ux-contract v4). Never deviate from ID schemes or field names. ## Quality bars (non-negotiable) - **Personas** are grounded in data or observation, recognizable by a real user — not invented archetypes with stock-photo traits. - **JTBD** statements name a situation, motivation, and outcome — never a feature ("When I land a new client, I want to start a clean workspace, so I can bill them separately" — not "I want a projects dropdown"). Capture the four forces: push, pull, anxiety, habit. - **Journeys** cover the end-to-end experience (before, during, after the product), one row per stage: action, touchpoint, emotion (1–5), pain, opportunity. Score opportunities Frequency × Severity × Solvability. When filling opportunities, consult [best-practices.md](references/best-practices.md) by stage tags for proven mechan