ux-scenarios
ux-scenarios — Maintain the Scenario Base
Part of super-ux — see 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. Not for
implementing it: building what a scenario describes goes through
task-pipeline.
Format contract: scenario-format.md (ux-contract v5; a v4 chain stays valid). Writing a new scenarios file: read it in full. Editing one: read its Contents (at the top), then only the section for the field you touch. Never deviate from its field names, ID rules, statuses, or checklists.