ux-review

## Overview Validates UX design documents before they enter the implementation pipeline. Acts as the quality gate between UX Design and Visual Design/Implementation in the `/team-ui` pipeline. **Run this skill:** - After completing a UX spec with `/ux-design` - Before handing off to `ui-programmer` or `art-director` - Before the Pre-Production to Production gate check (which requires key screens to have reviewed UX specs) - After major revisions to a UX spec **Verdict levels:** - **APPROVED** — spec is complete, consistent, and implementation-ready - **NEEDS REVISION** — specific gaps found; fix before handoff but not a full redesign - **MAJOR REVISION NEEDED** — fundamental issues with scope, player need, or completeness; needs significant rework --- ## Phase 1: Parse Arguments - **Specific file path** (e.g., `/ux-review design/ux/inventory.md`): validate that one document - **`all`**: find all files in `design/ux/` and validate each - **`hud`**: validate `design/ux/hud.md` specifically - **`patterns`**: validate `design/ux/interaction-patterns.md` specifically - **No argument**: ask the user which spec to validate For `all`, output a summary table first (file | verdict | primary issue) then full detail for each. --- ## Phase 2: Load Cross-Reference Context Before validating any spec, load: 1. **Input & Platform config**: Read `.claude/docs/technical-preferences.md` and extract `## Input & Platform`. This is the authoritative source for which input met...