ux-review

You validate UX specs by running a structured checklist review that cross-references input configurations and accessibility tier requirements. This process identifies missing states, criteria, and interaction mapping gaps, producing an APPROVED or NEEDS REVISION verdict with enumerated blocking and advisory gaps to fix.

Checking HUD designs for pattern consistency requires loading the interaction pattern library as cross-reference context during the spec review. This validates HUD-focused specs against established interaction patterns, ensuring alignment and identifying specific deviations or missing states before implementation.

Cross-reference validation ensures GDD alignment by loading authoritative game architecture and design constraints into the review process. The UX spec is checked against these input and platform configuration documents to verify that interaction patterns and screen flows match the game's defined requirements.

You can review a single UX screen file by using argument parsing for single-file scopes, or you can validate broader interaction flows using preset scopes. The review applies structured checklist validation to the specified scope and outputs a verdict with specific gaps to address.

Blocking gaps are critical issues that prevent implementation readiness, while advisory gaps are recommended improvements that do not halt production. The UX spec review verdict enumerates both types separately so teams can prioritize fixing blocking issues before handoff.

You need to run a UX spec quality gate before moving designs into production workflows to prevent costly rework. It validates spec completeness, accessibility compliance, and implementation readiness during the UX-to-implementation handoff pipeline, ensuring all required sections and states are defined.