UX Design

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 Design" 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 authors UX specifications section by section for a game screen or flow, the HUD, the interaction pattern library, or project-wide accessibility requirements (argument selects the mode; outputs: design/ux/[screen].md, design/ux/hud.md, design/ux/interaction-patterns.md, or design/accessibility-requirements.md, the one mode that writes outside design/ux/). In the default collaborative mode it works Question, Options, Decision, Draft, Approval for every section, asks 'May I write to [filepath]?' before the skeleton and before each section write, and writes each approved section to file immediately. Disclosed in its own phase files: after writing the skeleton and after each section, it updates production/session-state/active.md with the current screen and progress (the session-state record that also lets an interrupted session resume), and the cross-reference phase updates it again at handoff; in guided/autonomous template modes the asking follows the template's automation-modes document instead. It coordinates specialist template agents (ux-designer as primary; art-director, ui-programmer, game-designer, narrative-director, accessibility-specialist per topic) through the Agent tool, but the agents never write files: this session owns all writes. Its per-mode section guidance lives in its references/ files (phase files 2-gather-context, 3-file-skeleton, 4-authoring, 5-crossref-handoff plus sections-hud, sections-patterns, sections-ux-spec), and the accessibility guidance itself lives in the template's .claude/docs/templates/guidance/, outside this folder. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/ux-design/ folder at the pinned commit: 8 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-design/ 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 4afc2b07ed5c854906f6a6bebd06f7f10ddc174a80ce30d0df2beddb80cfe101 - references/2-gather-context.md: SHA-256 b8c7dac24f6ea2fdd7ef278bf5074a4cba6c068e500154099231dad0997d2b8e - references/3-file-skeleton.md: SHA-256 ec58c4982148229b4d336f217c92f9fdf71029e22e68b9d0d0e51e909b22a901 - references/4-authoring.md: SHA-256 c0df1eb0c791565c660e93ee813cc96dcc4a5f687ac25406cd75f8801f3abd40 - references/5-crossref-handoff.md: SHA-256 b1785beef772c20984ce2f545edd29104a5587df8fca57f1d4d7d547af5aaa00 - references/sections-hud.md: SHA-256 41f737fdc05271030b85f8d8af1e2030d9558eca831376bb4fd92a3d4243b054 - references/sections-patterns.md: SHA-256 f22f4012b3d7e7a78ebe3b18d7aee67319aef65b2799405d6a8e5a5717e8fe75 - references/sections-ux-spec.md: SHA-256 fce8ca3eb9ab452328e2f1b20ceb01c707a3be9d6a74b5acf481ecdb6a1e9219 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 8 files: SKILL.md plus 7 files under references/ (phase files and per-mode section guidance). Nothing in the folder is a program; they are instructions and guidance the skill reads 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 designed or modified. - Integrated-system reality, from the files: at use time the skill resolves studio configuration by running the template's hooks/yaml-helper.sh (outside this skill's folder, absent standalone), loads authoring guides from the template's .claude/docs/templates/guidance/, and may delegate questions to specialist template agents via the Agent tool. All of that is local to my project and the template; no network service is named. - At use time it writes the UX document section by section, asking before the skeleton and before each section in collaborative mode; disclosed: after the skeleton and each section write it also updates production/session-state/active.md (its progress/resume record), and the accessibility mode writes to design/accessibility-requirements.md, outside design/ux/. Sub-agents it consults never write files themselves. - Do not design anything, do not run any template hook or agent, 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-design folder into the agent's skills directory, in a folder named exactly "ux-design", keeping its 8 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: ux-design), the 8 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.