Topic: ai-assisted-development
271 skills in this topic.
-
design-review
Reviews a game design document for completeness, internal consistency, implementability, and adherence to project design standards. Run this before handing a design document to programmers.
Donchitos/Claude-Code-Game-Studios 8,725
-
estimate
Estimates task effort by analyzing complexity, dependencies, historical velocity, and risk factors. Produces a structured estimate with confidence levels.
Donchitos/Claude-Code-Game-Studios 8,725
-
code-review
Performs an architectural and quality code review on a specified file or set of files. Checks for coding standard compliance, architectural pattern adherence, SOLID principles, testability, and performance concerns.
Donchitos/Claude-Code-Game-Studios 8,725
-
team-polish
Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.
Donchitos/Claude-Code-Game-Studios 8,725
-
project-stage-detect
Automatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts. Use when user asks 'where are we in development', 'what stage are we in', 'full project audit'.
Donchitos/Claude-Code-Game-Studios 8,725
-
security-audit
Audit the game for security vulnerabilities: save tampering, cheat vectors, network exploits, data exposure, and input validation gaps. Produces a prioritised security report with remediation guidance. Run before any public release or multiplayer launch.
Donchitos/Claude-Code-Game-Studios 8,725
-
content-audit
Audit GDD-specified content counts against implemented content. Identifies what's planned vs built.
Donchitos/Claude-Code-Game-Studios 8,725
-
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
Donchitos/Claude-Code-Game-Studios 8,725
-
day-one-patch
Prepare a day-one patch for a game launch. Scopes, prioritises, implements, and QA-gates a focused patch addressing known issues discovered after gold master but before or immediately after public launch. Treats the patch as a mini-sprint with its own QA gate and rollback plan.
Donchitos/Claude-Code-Game-Studios 8,725
-
hotfix
Emergency fix workflow that bypasses normal sprint processes with a full audit trail. Creates hotfix branch, tracks approvals, and ensures the fix is backported correctly.
Donchitos/Claude-Code-Game-Studios 8,725
-
sprint-status
Fast sprint status check. Reads the current sprint plan, scans story files for status, and produces a concise progress snapshot with burndown assessment and emerging risks. Run at any time during a sprint for quick situational awareness. Use when user asks 'how is the sprint going', 'sprint update', 'show sprint progress'.
Donchitos/Claude-Code-Game-Studios 8,725
-
team-live-ops
Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
Donchitos/Claude-Code-Game-Studios 8,725
-
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
Donchitos/Claude-Code-Game-Studios 8,725
-
start
First-time onboarding — asks where you are, then guides you to the right workflow. No assumptions.
Donchitos/Claude-Code-Game-Studios 8,725
-
scope-check
Analyze a feature or sprint for scope creep by comparing current scope against the original plan. Flags additions, quantifies bloat, and recommends cuts. Use when user says 'any scope creep', 'scope review', 'are we staying in scope'.
Donchitos/Claude-Code-Game-Studios 8,725
-
create-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Donchitos/Claude-Code-Game-Studios 8,725
-
design-system
Guided, section-by-section GDD authoring for a single game system. Gathers context from existing docs, walks through each required section collaboratively, cross-references dependencies, and writes incrementally to file.
Donchitos/Claude-Code-Game-Studios 8,725
-
map-systems
Decompose a game concept into individual systems, map dependencies, prioritize design order, and create the systems index.
Donchitos/Claude-Code-Game-Studios 8,725
-
architecture-review
Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /design-review.
Donchitos/Claude-Code-Game-Studios 8,725
-
create-architecture
Guided, section-by-section authoring of the master architecture document for the game. Reads all GDDs, the systems index, existing ADRs, and the engine reference library to produce a complete architecture blueprint before any code is written. Engine-version-aware: flags knowledge gaps and validates decisions against the pinned engine version.
Donchitos/Claude-Code-Game-Studios 8,725
-
ux-design
Guided, section-by-section UX spec authoring for a screen, flow, or HUD. Reads game concept, player journey, and relevant GDDs to provide context-aware design guidance. Produces ux-spec.md (per screen/flow) or hud-design.md using the studio templates.
Donchitos/Claude-Code-Game-Studios 8,725
-
retrospective
Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration.
Donchitos/Claude-Code-Game-Studios 8,725
-
balance-check
Analyzes game balance data files, formulas, and configuration to identify outliers, broken progressions, degenerate strategies, and economy imbalances. Use after modifying any balance-related data or design. Use when user says 'balance report', 'check game balance', 'run a balance check'.
Donchitos/Claude-Code-Game-Studios 8,725
-
onboard
Generates a contextual onboarding document for a new contributor or agent joining the project. Summarizes project state, architecture, conventions, and current priorities relevant to the specified role or area.
Donchitos/Claude-Code-Game-Studios 8,725