ux-review

Validate UX design documents for completeness and accessibility compliance.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/WindXRan/y3td --skill ux-review-windxran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-review
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/ux-review
Command: npx skills add https://github.com/WindXRan/y3td --skill ux-review-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents incomplete or inconsistent UX specs from reaching implementation by validating documentation coverage, accessibility compliance, GDD alignment, and pattern-library readiness before handoff.

Core Features & Use Cases

  • UX spec completeness gate: checks required sections (states, interactions, data requirements, events, transitions, accessibility, localization, and testable acceptance criteria).
  • Cross-reference validation: loads platform/input configuration, accessibility tier, interaction pattern library, referenced GDD UI requirements, and player journey context to ensure the UX spec is consistent with upstream commitments.
  • HUD and interaction pattern validation: runs dedicated checklists for hud-design.md and interaction-patterns.md, ensuring design coverage and consistency with established UI control standards.
  • Actionable verdict output: produces APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED with specific gaps and where to fix them.

Quick Start

Run the ux-review skill on your UX document by validating design/ux/hud.md.

Frequently Asked Questions about ux-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate UX specs for implementation readiness before handoff?

Validate UX specs for implementation readiness by checking documentation coverage, accessibility compliance, and GDD alignment. This process ensures incomplete interaction patterns and missing states are caught before downstream UI work begins.

What sections are required in a UX design document to pass a completeness gate?

A UX completeness gate requires states, interactions, data requirements, events, transitions, accessibility, localization, and testable acceptance criteria. Missing any of these sections will trigger a needs revision verdict.

Can I check HUD design documents against interaction pattern libraries?

Yes, you can check HUD design documents against interaction pattern libraries by running dedicated checklists. This ensures design coverage and consistency with established UI control standards and platform input configurations.

What is the best way to verify accessibility tier compliance in UX specs?

Verify accessibility tier compliance in UX specs by loading platform configuration and cross-referencing interaction pattern libraries. This ensures the UX spec remains consistent with upstream accessibility commitments.

Does UX validation check alignment with referenced Game Design Document UI requirements?

UX validation checks alignment with referenced Game Design Document UI requirements by loading GDD commitments and player journey context. It cross-references these against the UX spec to ensure upstream consistency.

What happens when a UX spec fails validation and has missing sections?

When a UX spec fails validation, it produces a structured verdict of needs revision or major revision needed. The output identifies specific missing sections and gaps with directions on where to fix them.