A review process that checks a game UX document, HUD design, or interaction library for completeness, accessibility, consistency with the game design, and implementation readiness. UX means how an interface works for the player.

Use it to review interface specifications, HUDs, and interaction patterns before visual design or programming.

It finds unclear requirements and missing accessibility or player needs before the document reaches implementation. The result is a verdict with specific issues to fix.

ux-review — Skill for Claude Code by IdoCohen560

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add IdoCohen560/claude-unity-game-studio --skill ux-review

Clone the repo

git clone --depth 1 https://github.com/IdoCohen560/claude-unity-game-studio

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/ux-review/github.svg)](https://agentmods.dev/skills/idocohen560/claude-unity-game-studio/ux-review)

Your own site

<a href="https://agentmods.dev/skills/idocohen560/claude-unity-game-studio/ux-review"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/ux-review/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/idocohen560/claude-unity-game-studio/ux-review"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/ux-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,442 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 94% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00051	$0.02442
Opus 5	$0.00026	$0.01221
Sonnet 5	$0.00010	$0.00488
Haiku 4.5	$0.00005	$0.00244

Measured 8d ago against content hash bd57bed7d607, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

ux-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

94% identical to ux-review — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

examples/my-first-game/.claude/skills/ux-review/SKILL.md · 263 lines

How it starts

The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Overview

Validates UX design documents before they enter the implementation pipeline. Acts as the quality gate between UX Design and Visual Design/Implementation in the /team-ui pipeline.

Run this skill:

After completing a UX spec with /ux-design
Before handing off to ui-programmer or art-director
Before the Pre-Production to Production gate check (which requires key screens to have reviewed UX specs)
After major revisions to a UX spec

Verdict levels:

APPROVED — spec is complete, consistent, and implementation-ready
NEEDS REVISION — specific gaps found; fix before handoff but not a full redesign
MAJOR REVISION NEEDED — fundamental issues with scope, player need, or completeness; needs significant rework

Phase 1: Parse Arguments

Specific file path (e.g., /ux-review design/ux/inventory.md): validate that one document
all: find all files in design/ux/ and validate each
hud: validate design/ux/hud.md specifically
patterns: validate design/ux/interaction-patterns.md specifically
No argument: ask the user which spec to validate

For all, output a summary table first (file | verdict | primary issue) then full detail for each.

Phase 2: Load Cross-Reference Context

Before validating any spec, load:

Input & Platform config: Read .claude/docs/technical-preferences.md and extract ## Input & Platform. This is the authoritative source for which input methods the game supports — use it to drive the Input Method Coverage checks in Phase 3A, not the spec's own header. If unconfigured, fall back to the spec header.
The accessibility tier committed to in design/accessibility-requirements.md (if it exists)
The interaction pattern library at design/ux/interaction-patterns.md (if it exists)
The GDDs referenced in the spec's header (read their UI Requirements sections)
The player journey map at design/player-journey.md (if it exists) for context-arrival validation

Read the full file on GitHub · 263 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

8d ago First seen · 263 lines · 51 tokens per session scan A bd57bed7d607

Subscribe to this mod's changes

ux-review is a skill published in the GitHub repository IdoCohen560/claude-unity-game-studio (19 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 2,442 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to ux-review, differing in 1 line, and is treated as a copy.

Claude Code Design and UX Game development claude claude-ai claude-code-plugin claude-code-skill claude-code-skills

accessibility

Audits code for WCAG 2.2 AA compliance and provides design guidance for accessible components. Covers semantic HTML, ARIA, keyboard nav, contrast, focus management, and motion.

RealDougEubanks/ClaudeMarketplace · 41 tokens

abd-design

ABD Design agent: produces architecture diagrams, component breakdowns, data flow, and design decisions from the current plan.

RealDougEubanks/ClaudeMarketplace · 26 tokens

swarm

Run a multi-agent audit of a codebase by spawning specialized parallel subagents (security, performance, tests, architecture, dead-code), then synthesize their findings into a single prioritized action plan. Use this whenever the user runs /swarm, asks to "audit the repo," "review this codebase," "find issues across…

Zintellix/Claude-Skills · 138 tokens

ux-review