ux-flowslisted

# ux-flows — Design HOW Users Move > 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`). Turns user stories into user flows AND maintains the UI map: task analysis → flow diagram (mermaid) → the screen registry `screens.md` (every screen and state with Figma frame, wireframe, coverage, resources) → optional wireframes/Figma mockups. Also the home of UX improvement: heuristic evaluation of existing flows and traced redesign proposals. **Two files owned:** `flows.md` (flows referencing screens by `SCR-ID`) and `screens.md` (the canonical per-screen spec — the design map that ties UX, UI, Figma, and code together). A screen used by several flows is described once in `screens.md`. **Contracts:** [scenario-format.md](references/scenario-format.md) (ux-contract v4, `flows.md` section) and [ux-design-principles.md](references/ux-design-principles.md) — read the principles doc before designing; it is the thinking playbook (task-analysis method, flow rules, PRN-01..24 heuristics, improvement procedure). Proven tactics: [best-practices.md](references/best-practices.md) by stage tags. Visual identity (which style pack the frames and the built UI obey, via the **sheleg-design** companion): [visual-identity.md](references/visual-identity.md). **Real flows off the shelf, before you invent one:** if the session exposes a reference server — **Refero** (`mcp__r