ux-review

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game UX documents often reach implementation with missing error 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 structured APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED verdict with specific blocking and advisory issues. ## Core Features & Use Cases - Checklist-driven validation: Runs completeness, quality, input-method coverage, data architecture, accessibility, GDD alignment, pattern consistency, and localization checks against UX specs, with dedicated checklists for HUD designs and pattern libraries. - Cross-reference context loading: Reads project input/platform configuration, accessibility tier commitments, referenced GDD UI requirements, and the player journey map to validate specs against authoritative sources rather than the spec's own claims. - Structured verdict output: Produces a review report listing completeness scores, blocking versus advisory issues, GDD coverage gaps, and accessibility compliance, plus next-step guidance for each verdict level. - Use Case: After drafting an inventory screen spec with a UX design workflow, run this Skill on design/ux/inventory.md to confirm error states, gamepad navigation, and colorblind-safe indicators are documented before handing off to a UI programmer. ## Quick Start Use the ux-review skill to validate the UX spec at design/ux/inventory.md and report its verdict with any 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 UX spec before implementation?

Run the ux-review skill with the spec's 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 UX design review checklist cover for games?

The checklist covers completeness of required sections, error/empty/loading states, keyboard and gamepad input coverage, data ownership rules, accessibility tier compliance, GDD requirement alignment, pattern library consistency, localization limits, and acceptance criteria quality.

Can I review all UX documents at once?

Yes. Passing 'all' validates every file in design/ux/ and outputs a summary table of file, verdict, and primary issue before full per-document detail. You can also target 'hud' or 'patterns' for those specific documents.

Does the UX review skill modify my design documents?

No. The skill is strictly read-only and never edits or writes files. It reports findings and offers to help draft fixes only after you explicitly request it, and the verdict is advisory rather than blocking.

What accessibility standards does the review check against?

It reads the committed tier from design/accessibility-requirements.md and enforces matching rules: no color-only indicators at Basic, focus order and contrast ratios at Standard, and screen reader announcements at Comprehensive, plus colorblind alternatives for color-coded elements.