ux-check
UX Check
A screen works when a first-time user knows what they can do, does it, and always knows what just happened. This skill checks that, mechanically where possible, and makes the agent play the user instead of waiting to be told something is broken.
Scope
This skill owns behavior and coverage: whether controls look like what they do, whether every state exists, whether flows have an exit and an end, whether destructive actions are guarded.
Neighbors own the rest. Once a state exists, its words belong to ux-writing and its visual finish to ui-polish. Motion timing lives in motion. This skill decides what exists and how it behaves, never how it reads or looks.
Three contested lines, settled here: whether a confirmation should exist at all is this skill (undo beats a dialog); the wording of a dialog that must exist is ux-writing. Semantics, keyboard, alt text and focus order are this skill; the visible focus ring and contrast ratios are ui-polish. Accessible names (alt, aria-label, title) are this skill whole. They are written once, so splitting existence from wording gave two places to check one string and nothing else.
Response-time budgets below (feedback within 100 ms, progress past a second) are perception thresholds for whether the interface answered, not animation values. Every duration of an animation belongs to motion.
Skills outside this line can own the same ground (better-accessibility, improve-ui and the like). If one is loaded, follow it and report only what it does not cover. One defect, one finding, whoever raised it.