ui-ux-review

# UI/UX Review Review the interface users actually receive, not only the component source. ## Establish the surface 1. Identify routes, primary flows, target users, supported viewports, themes, content states, and the design system or brand constraints. 2. Inspect the diff and direct consumers before forming findings. 3. Run the deterministic audit helper against relevant HTML/CSS/JS when a static surface is available: ```bash python3 skills/ui-ux-review/scripts/audit_ui.py ./path/to/ui ``` Zero supported source files is inconclusive and exits with status 2. Use `--allow-empty` only when an empty UI scope is intentional; it is not proof that a surface is clean. 4. Extract the current token and component system with `frontend-design` when consistency claims depend on it; compare against existing tokens before proposing a redesign language. 5. Render the surface in a browser. Capture normal, empty, error, loading, permission, narrow, intermediate, and desktop states that matter to the request. If runtime access is blocked, mark visual findings unverified. ## Review passes ### Experience and hierarchy Check whether the first viewport explains the page, the primary action is obvious, copy is scannable, labels are specific, and repeated containers add meaning rather than noise. ### Interaction and accessibility Check semantics, names, keyboard order, focus visibility, contrast, target size, error recovery, reduced motion, screen-reade...