ux-review

Validate UX specifications against a five-phase quality gate and output a structured verdict.

Updated Feb 8, 2024
One-click install
npx skills add https://github.com/kay6198835/Game-RPG --skill ux-review-kay6198835
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-review
Source: https://github.com/kay6198835/Game-RPG/tree/main/.claude/skills/ux-review
Command: npx skills add https://github.com/kay6198835/Game-RPG --skill ux-review-kay6198835

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates UX specifications against a comprehensive quality gate to ensure they are complete, accessible, and implementation-ready.

Core Features & Use Cases

  • Phase 1: Parse Arguments to validate a single file or the entire design set.
  • Phase 2: Load Cross-Reference Context to apply standardized inputs from technical preferences, accessibility requirements, and GDDs.
  • Phase 3A: UX Spec Validation Checklist that covers completeness and quality (status, player needs, navigation, data, events, accessibility, localization, acceptance criteria).
  • Phase 3B: HUD Validation Checklist to ensure layout, zones, and UI element specifications across contexts.
  • Phase 3C: Pattern Library Validation Checklist to ensure patterns exist and are consistently defined.
  • Phase 4: Output the Verdict in a structured format including blocking/advisory issues.
  • Phase 5: Collaborative Protocol describing read-only operation and post-verdict guidance.

Quick Start

Run the ux-review skill on a UX spec file (e.g., design/ux/hud.md) to produce a verdict and a list of gaps.

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 specifications for completeness and accessibility before handoff?

Validate UX specifications by running them through a quality gate that checks completeness, accessibility, and implementation readiness. This applies standardized inputs from technical preferences and accessibility requirements to output a structured verdict with actionable gaps.

What is a UX spec quality gate and when do I need it?

A UX spec quality gate is a phased validation workflow ensuring design specifications are complete and implementation-ready. You need it before handing off UX specs, HUD designs, and interaction-pattern libraries to developers and art directors.

Can I review an entire design set or only a single UX spec file?

You can review both a single file and the entire design set. The validation workflow parses arguments to target a specific file, like a HUD design document, or evaluates the full collection of UX specifications across the project.

How do I check HUD layouts and interaction patterns for implementation readiness?

Check HUD layouts and interaction patterns using dedicated validation checklists. The HUD checklist verifies layout, zones, and UI element specifications across contexts, while the pattern library checklist ensures patterns exist and are consistently defined.

Does the UX review process support game design documents and cross-reference context?

Yes, the process supports game design documents by loading cross-reference context. It applies standardized inputs from technical preferences, accessibility requirements, and GDDs during the validation workflow to ensure comprehensive coverage.

What verdicts are output after validating UX specifications?

The validation outputs a structured verdict of APPROVED, NEEDS REVISION, or MAJOR REVISION NEEDED. This result includes specific blocking and advisory issues to guide necessary corrections before the design-to-implementation handoff.