UX Review

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — INTEGRATED SYSTEM FIRST: this skill is one piece of the complete "Claude Code Game Studios" template (49 agents, 74 skills, studio templates and a studio CLAUDE.md, per the repository README). Each skill assumes that template is installed, with its conventions, its project.yaml / project.local.yaml configuration, its .claude/docs/ mode documents, its hooks (for example hooks/yaml-helper.sh, outside this skill's folder) and its .claude/scripts/ helpers. Installing this listing alone copies only this skill's folder, without the rest of the system: the skill may reference template agents, files, hooks or scripts that are absent outside the full template, and it may not run as designed on its own. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Install "UX Review" for me. Installing this listing alone copies only this skill's folder, without the rest of the system: the skill may reference template agents, files, hooks or scripts that are absent outside the full template, and it may not run as designed on its own. The skill itself validates a UX document, a HUD design or the interaction pattern library against checklists (completeness, states, input-method coverage, data architecture, accessibility, GDD alignment, pattern-library consistency, localization, acceptance criteria), after loading cross-reference context from the project: the platform block of project.yaml or .claude/docs/technical-preferences.md, the committed accessibility tier in design/accessibility-requirements.md, the pattern library, the referenced GDDs' UI Requirements sections and the player journey map. It returns one verdict: APPROVED, NOT ASSESSED, NEEDS REVISION or MAJOR REVISION NEEDED, with NOT ASSESSED ranked above APPROVED: a dimension with no criterion to check against (for example no committed accessibility tier, because design/accessibility-requirements.md is absent) is reported NOT ASSESSED, never as compliant. It is explicitly READ-ONLY: its Phase 5 protocol states it never edits or writes files and reports findings only; it may offer to help draft a fix afterwards but never auto-fixes. It resolves the workflow mode by running the template's hooks/yaml-helper.sh, a template file outside this skill's folder. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/ux-review/ folder at the pinned commit: 1 files in total) Pinned version: install the code at commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/Donchitos/Claude-Code-Game-Studios into a temporary folder, check out commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418, and copy the .claude/skills/ux-review/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 064b9ce2ad6b8dd954448dab6e5130da6c8bfc784e368c852202a71bf5a2c619 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file only: SKILL.md. Nothing in the folder is a program; it is instructions and checklists the agent follows at use time. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no project of mine is reviewed or modified. - Integrated-system reality, from the files: at use time the skill resolves the workflow mode by running the template's hooks/yaml-helper.sh (outside this skill's folder, absent standalone) and reads my project's config, UX documents, GDD sections and player journey locally. No network service is named. - At use time it writes NOTHING: the skill is read-only by its own protocol, it never edits or writes files, never auto-fixes a spec, and a dimension it could not check is reported NOT ASSESSED rather than passed. This is the exception to the family's usual ask-before-writing pattern: there is no write to ask about. - Do not review anything, do not run any template hook, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole ux-review folder into the agent's skills directory, in a folder named exactly "ux-review", keeping its 1 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: ux-review), the 1 files in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that it belongs to the full Claude Code Game Studios template and may not run standalone, and what it does inside the template). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.