ux-review

Validating UX design specs requires checking required sections like purpose, player context, states, navigation, layout zones, events, transitions, accessibility, and localization. A deterministic review parses these sections and cross-references context files to produce a verdict with specific blocking gaps.

UX spec cross-reference alignment loads platform input configurations, accessibility requirements, interaction pattern libraries, and referenced GDD UI requirements to detect mismatches. It ensures the UX document is consistent with established game design documents and interaction standards before implementation.

Yes, you can check HUD design documents for accessibility compliance and input-method coverage using dedicated HUD review modes. These modes apply tailored completeness and consistency checklists to validate player-facing HUD elements against platform input configurations and accessibility requirements.

UX validation works for both interaction pattern libraries and player-facing HUD documents. It applies dedicated completeness and consistency checklists tailored to each document type, ensuring both pattern definitions and HUD layouts meet required UX standards.

You should run a UX review on design documents before implementation handoff and after major UX revisions. This timing prevents designs with missing sections, unclear player needs, or accessibility and input-method gaps from moving into implementation and causing costly rework.

To review a UX spec and find missing sections, specify the document file path to trigger a deterministic read-only review. The review parses required UX spec sections, loads cross-reference context files, and produces a verdict identifying specific blocking gaps that must be resolved.