Team UI

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 "Team UI" for me. The skill itself orchestrates the UI team through the full UX pipeline — authoring, visual design, implementation, review, polish — for one UI feature, using the template's /ux-design and /ux-review skills and studio templates; with no argument it prints usage and exits without spawning any agent or reading any design file. It first resolves review_mode, automation and team.size by running the template's hooks/yaml-helper.sh, outside this skill's folder, and announces the active set: at the default team.size individual the ui-programmer and ux-designer run; at small the accessibility-specialist and art-director join; at studio the engine UI specialist joins too, with an adversarial review pass. Phase 1a gathers context — the game concept or minimal-rigor brief, the player journey, the GDD UI requirements, the interaction patterns and the committed accessibility tier in design/accessibility-requirements.md — and reports every one of those five inputs as present or ABSENT before anything is designed: a missing accessibility-requirements file means there is no committed tier, the ux-designer states the tier it assumes, Phase 4 must later report accessibility as NOT ASSESSED rather than passed, and /ux-design accessibility is recommended; a missing interaction-patterns file is surfaced at once and the user chooses running /ux-design patterns first or proceeding with every pattern treated as new and a new library file written at completion — patterns are never invented from the feature name. Phase 1b authors the UX spec (design/ux/[feature-name].md, from the ux-spec template, or the hud-design template for a HUD) by invoking the /ux-design sub-skill or delegating to the ux-designer, and Phase 1c gates on /ux-review: no Phase 2 until APPROVED, a NEEDS REVISION spec is revised in place and re-reviewed, and proceeding past NEEDS REVISION or NOT ASSESSED is a conscious user decision recorded in the final report. Phase 2 delegates visual design to the art-director (art-bible treatment, contrast and never colour alone for state, asset requirements). Phase 3 spawns the engine UI specialist named by specialists.ui in project.yaml (explicitly: a null value there means UNSET, skip the specialist, never spawn "null"; with no engine configured the step is skipped and recorded as engine validation NOT ASSESSED) for engine framework guidance, then delegates implementation to the ui-programmer — UI never owns or modifies game state, all player-facing text goes through the localization system with no hardcoded strings, both keyboard/mouse and gamepad are supported, accessibility is implemented against the committed tier, and any new interaction pattern is added to design/ux/interaction-patterns.md before implementation is complete. Phase 4 runs the ux-designer, art-director and accessibility-specialist reviews in parallel; accessibility violations are blockers, and with no committed tier that gate reports NOT ASSESSED and is never reported as passed. Phase 5 polishes (skippable animations respecting motion-reduction preferences, UI sounds only through the audio event system, all resolutions and aspect ratios, pattern library and HUD visual budget checks). Sub-agents write working artifacts under production/ui/[feature-name]/ without a per-write prompt, under a bounded exception the file documents (orchestrator-named path, new artifact under production/, docs/ or tests/, phase gated by an AskUserQuestion); implementation code is outside that exception and follows one ask for the file set, and the sub-skills /ux-design and /ux-review are not covered by the exception at all and ask before writing — the UX spec itself sits under design/ for that reason. This orchestrator writes no files directly. Its frontmatter pins model: sonnet. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/team-ui/ folder at the pinned commit: 1 file 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/team-ui/ 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 dce06487831bdcea7f62ead4f47de38c6b6acd877fb047655bf82ed28cfcfb36 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: SKILL.md only. Nothing in the folder is a program; it is instructions 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 audited, read or modified. - Integrated-system reality, from the file: at use time the skill runs the template's hooks/yaml-helper.sh to resolve review_mode, automation and team.size, follows .claude/docs/automation-modes.md, config-resolution.md, technical-preferences.md and error-recovery-protocol.md, invokes the template's /ux-design and /ux-review skills and its UX, HUD, interaction-pattern and accessibility templates, reads my project's concept, journey, GDD, pattern and accessibility files under design/, and spawns template agents (ux-designer and ui-programmer at every size; art-director and accessibility-specialist at small and up; the engine UI specialist at studio) — agents, docs, templates, skills and project files that live outside this skill's folder and are absent in a standalone install, so it cannot run as designed on its own. - At use time its sub-agents write review and visual-design artifacts under production/ui/[feature-name]/ without a per-write prompt, but only inside the bounded exception the file documents (orchestrator-named path, new artifact under production/, docs/ or tests/, phase gated by an AskUserQuestion); the ui-programmer's implementation code under the code root is outside that exception and is written only after one ask for the file set, and the UX spec and pattern-library updates under design/ are produced by the /ux-design sub-skill or an agent asking first, because sub-skills are not covered by the exception. This orchestrator writes no files directly. No third-party service, account or credential is named in the file. - Do not design or implement any UI feature, do not spawn any team agent, do not invoke /ux-design or /ux-review, 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 team-ui folder into the agent's skills directory, in a folder named exactly "team-ui", keeping its 1 file in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: team-ui), the 1 file 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 (it resolves its settings through the template's yaml-helper hook, reads the template's design/ context files, invokes its /ux-design and /ux-review skills and spawns its UI team agents), and that at use time its working artifacts are written under production/ui/ under a documented bounded exception, implementation code only after one ask for the set, the UX spec asks first through the /ux-design sub-skill, and the accessibility gate reports NOT ASSESSED — never passed — when no committed accessibility tier exists). 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.