ux-review

To validate a UX spec for implementation readiness, you cross-reference the design document against technical input configurations and accessibility requirements to produce an APPROVED, NEEDS REVISION, or MAJOR REVISION NEEDED verdict with specific section-level gaps to fix.

UX spec validation is the process of checking UX design documents, HUD designs, and interaction pattern libraries for completeness, accessibility compliance, and GDD alignment. You need it to prevent UX-to-implementation handoff failures before production work starts.

You check HUD design accessibility and state coverage by validating hud-design.md-based specs to confirm HUD states, visual budgets, and adaptation rules align with the authoritative input and platform configuration before generating a readiness verdict.

Yes, you can validate interaction-patterns.md-based catalogs by cross-referencing interactive components against the authoritative input and platform configuration to ensure navigation and interaction maps are consistent before implementation.

UX spec validation requires read-only cross-referencing of existing ux-spec.md, hud-design.md, or interaction-patterns.md files. It cannot generate new designs; it only identifies blocking and advisory issues, missing sections, and untestable acceptance criteria within the provided documents.

The best way to ensure GDD alignment is to verify that referenced UI requirements in the UX spec are fully covered and that acceptance criteria, including performance and resolution thresholds where required, are testable before issuing an implementation approval verdict.