Skip to content

UX Spec Review

Checks UX design docs for completeness, accessibility, and readiness before implementation.

Stars
32,965
Licence
MIT
Files
1 file

What it does

Once installed, the agent reviews a UX specification, HUD design, or interaction pattern library against a detailed checklist covering completeness, player need, input method coverage (keyboard, gamepad, touch), states, data ownership, accessibility, and alignment with game design documents. It returns a verdict of APPROVED, NOT ASSESSED, NEEDS REVISION, or MAJOR REVISION NEEDED, with specific gaps listed. It is written for a game-studio workflow that uses a '/ux-design' and '/team-ui' pipeline.

Great for

  • Game teams using the Claude Code Game Studios setup who want a quality gate before UX specs go to implementation
  • Designers who want a structured self-check of a UX spec before handoff
  • Producers checking whether key screens meet pre-production to production requirements

Skip it if

  • Projects without written UX specs or game design documents, since the checks depend on files like design/ux/ and referenced GDDs (the review will be marked NOT ASSESSED or have little to check)
  • Non-game software where the player-focused checklist and HUD concepts do not apply

Try asking

  • “/ux-review design/ux/inventory.md”
  • “/ux-review hud”
  • “/ux-review all”
  • “/ux-review patterns”
Step-by-step guide: how to use UX Spec ReviewInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 1 original files, the MIT licence and an attribution note.

    ux-review.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip ux-review.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip ux-review.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Run it right after /ux-design so the spec carries the '> **Template**:' header, which selects the correct checklist.
  • Commit an accessibility tier in design/accessibility-requirements.md; without it the verdict may be NOT ASSESSED.
  • Read the NOT ASSESSED reasons first, since they name which checks lacked a source of truth to compare against.

What's inside

  • SKILL.md

Redistributed unmodified from Donchitos/Claude-Code-Game-Studios under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.