ux-review

Validates UX specs, HUD designs, and interaction pattern libraries against completeness and accessibility checklists.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill ux-review-claretagrapelike32
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-review
Source: https://github.com/claretagrapelike32/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/ux-review
Command: npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill ux-review-claretagrapelike32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game UX documents often reach implementation with missing states, undocumented input mappings, or accessibility gaps that cause costly rework. This Skill acts as a read-only quality gate that reviews UX specs, HUD designs, and interaction pattern libraries before handoff, producing a clear APPROVED, NEEDS REVISION, or MAJOR REVISION NEEDED verdict with specific blocking and advisory issues. ## Core Features & Use Cases - Structured Validation Checklists: Runs dedicated checklists for UX specs, HUD designs, and pattern libraries covering completeness, states, input methods, data ownership, localization, and acceptance criteria. - Cross-Reference Alignment: Loads project input/platform config, accessibility requirements, GDD UI requirements, and player journey maps to verify the spec matches committed constraints. - Verdict Report with Severity Levels: Outputs a structured review report separating blocking issues from advisory findings, with concrete fix guidance per issue. - Use Case: After drafting an inventory screen spec with a UX design workflow, run this review before handing off to a UI programmer to catch a missing error state, undefined gamepad focus order, or unmet accessibility tier. ## Quick Start Ask the AI to run the ux-review skill on design/ux/inventory.md and report the verdict with all blocking issues.

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 game UX spec before implementation?

Run the ux-review skill against the spec file path, such as design/ux/inventory.md. It checks required sections, states, input coverage, accessibility, and GDD alignment, then returns an APPROVED, NEEDS REVISION, or MAJOR REVISION NEEDED verdict with specific gaps.

What does a HUD design review checklist cover?

The HUD checklist verifies information architecture against GDD systems, layout zones with safe margins, per-element specifications, gameplay context states, visual budget limits, platform adaptation, and colorblind variants for color-coded elements.

Does the ux-review skill modify my design documents?

No, the skill is strictly read-only. It reports findings and verdicts without editing files, and it never blocks you from proceeding; the verdict is advisory and you decide whether to accept the documented risk.

Can I review all UX specs in a project at once?

Yes, passing the argument 'all' validates every file in design/ux/ and outputs a summary table of file, verdict, and primary issue before the detailed per-document reports. You can also target 'hud' or 'patterns' specifically.

How does the review check accessibility compliance?

It reads the committed tier from design/accessibility-requirements.md and verifies the spec meets it, checking color-only indicators for Basic tier, focus order and contrast for Standard tier, and screen reader announcements for Comprehensive tier.

When should I run a UX review in the game development pipeline?

Run it after completing a UX spec, before handing off to UI programmers or art directors, before the Pre-Production to Production gate check, and after any major spec revision.