ux-review

Validate UX design documents and HUD specifications for completeness and accessibility.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill ux-review-hechaoyannet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-review
Source: https://github.com/HechaoYannet/3kingdom-unity/tree/main/.claude/skills/ux-review
Command: npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill ux-review-hechaoyannet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates UX design documents (ux-specs, HUD design, and interaction-pattern libraries) to ensure completeness, accessibility compliance, GDD alignment, and readiness for implementation, reducing handoffs errors and rework.

Core Features & Use Cases

  • Validation & Gatekeeping: audits UX specs for missing sections, inconsistent terminology, and alignment with GDDs.
  • Accessibility & Compliance: checks for accessibility requirements and platform-targeted constraints.
  • Handoff Readiness: certifies specs are implementation-ready for UI programmers and art/design leads.
  • Use Case: during a design-to-development handoff, run ux-review to surface gaps before coding begins.

Quick Start

Run this skill on your ux-spec.md to validate completeness, accessibility, and handoff readiness.

Frequently Asked Questions about ux-review

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

FAQPage Schema
How do I validate a UX design spec before handing it off to UI programmers?

To validate a UX design spec before handoff, you must audit the document for completeness, accessibility compliance, and alignment with GDDs. This process ensures the spec contains necessary sections on purpose, navigation, data, and acceptance criteria, certifying it is implementation-ready.

What sections are required for a UX spec to pass a design quality gate?

A UX spec requires structured sections on purpose, context, navigation, data, accessibility, and acceptance criteria to pass a quality gate. It must also include cross-references to pattern libraries and Game Design Documents to ensure full readiness for UI programming.

When do I need to run a UX spec validation check?

You need to run a UX spec validation check during design reviews, gate checks, and design-to-development handoffs. Running this audit before coding begins surfaces missing sections, inconsistent terminology, and accessibility gaps, reducing rework for UI programmers.

Can I use a UX review tool to check accessibility requirements and platform constraints?

Yes, a UX review tool checks UX design documents for specific accessibility requirements and platform-targeted constraints. This validation mechanism ensures HUDs and interaction-pattern libraries comply with necessary standards before implementation.

How do I ensure my HUD specifications align with the Game Design Document?

To ensure HUD specifications align with a Game Design Document, you must cross-reference the UX specs against the GDD during a gate check. This validation surfaces inconsistencies between the design document and the established game design requirements.

Why does my UX handoff fail the implementation readiness check?

A UX handoff fails the implementation readiness check when the design document has missing sections, inconsistent terminology, or lacks accessibility compliance. Validating the UX spec before handoff surfaces these gaps to prevent implementation errors and rework.