Claude Code Game Studios skills

Section-by-section UX spec authoring for a screen, flow or HUD. Reads the player journey to provide context; also project-wide accessibility.

Configure engine and version. Pins it in CLAUDE.md; WebSearch fills reference docs when the version is beyond LLM training data.

Decompose a concept into individual systems, map dependencies, prioritize design order, create the systems index.

Orchestrate the UI team through the UX pipeline — authoring, visual design, implementation, review, polish. Uses /ux-design, /ux-review, studio templates.

Section-by-section GDD authoring for one system — walks through each required section, cross-references dependencies.

Author the Art Bible — visual identity gating asset production. Run before /map-systems.

Holistic cross-GDD review — contradictions between systems, dominant strategies, economic imbalance, cognitive overload, pillar drift.

Reviews one design document for completeness, internal consistency, implementability, and design standards. Before handing to programmers.

Ready to advance between development phases? PASS/CONCERNS/NOT ASSESSED/FAIL with blockers and required artifacts. 'Can we move to production?'

Lightweight spec for small changes — tuning adjustments, minor mechanics. Embeds directly into stories; skips full GDD.

Per-asset visual specs plus AI generation prompts from GDDs and character profiles. After the art bible.

Concept prototype before GDDs — throwaway HTML, Engine or Paper build, PROCEED/PIVOT/KILL/NOT ASSESSED. After /brainstorm and /setup-engine.

Create an ADR documenting a technical decision: context, alternatives considered, consequences.

Guided concept ideation using professional studio techniques, player psychology, creative exploration.

Audit assets against naming conventions, file size budgets, format standards. Finds orphaned assets, missing references.

Author the architecture blueprint before code is written. Validates decisions against the pinned engine, flags knowledge gaps.

Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.

New or updated sprint plan from the current milestone, completed work, and available capacity.

Map test coverage to GDD critical paths, find fixed bugs lacking regression tests, flag drift from new features.

Milestone progress review — completeness, quality metrics, risk, go/no-go recommendation. At checkpoints or before a deadline.

Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.

Pre-production validation — end-to-end build to confirm the full loop is achievable before committing to Production. After GDDs, architecture, UX specs.

Critical-path smoke gate before QA hand-off — runs the automated suite. A failed check means the build is not QA-ready.

Find flaky tests from CI logs — aggregates pass rates, spots intermittent failures, recommends quarantine. After multiple runs.