Browse Skills

Content Audit compares specified content counts from game design documents against implemented content in the codebase, producing a gap report. Use it to see what is planned vs built and identify high-priority missing content.

Create Architecture produces docs/architecture/architecture.md, the master architecture document that translates all approved GDDs into a concrete technical blueprint. It reads engine references, validates decisions, and flags knowledge gaps before sprint planning.

Create Control Manifest produces a flat actionable rules sheet for programmers, extracting what to do and what to avoid from Accepted ADRs, technical preferences, and engine reference docs. Use it after architecture review to keep implementation consistent.

Create Epics translates approved game design documents and architecture into one epic per architectural module, defining scope, governing ADRs, engine risk, and untraced requirements. Use it after architecture review and before creating stories.

Create Stories breaks a single epic into implementable, traceable story files for game development. Run it after /create-epics to decompose each epic into stories with acceptance criteria, TR-IDs, ADR guidance, story types, and test evidence paths.

Day-One Patch scopes, prioritizes, implements, and QA-gates a focused patch for known issues discovered after gold master but before or immediately after public launch. Use it after a gold master build is locked and known bugs or cert feedback require a safe, minimal fix with a rollback plan.

Design Review analyzes a game design document for completeness, internal consistency, implementability, and adherence to project design standards. Use it before handing a design document to programmers to catch gaps and broken references.

Dev Story reads a story file, loads full context (story, GDD, ADR, control manifest), routes to the right programmer agent, implements code and test, and confirms each acceptance criterion. Use after /story-readiness and before /code-review.

Estimate analyzes task complexity, dependencies, historical velocity, and risk factors to produce a structured effort estimate with confidence levels. Use it before committing to a task to get optimistic, expected, and pessimistic day ranges plus a recommended budget and risk breakdown.

Game Design System guides Claude Code through an interactive, section-by-section process to author game design documents (GDDs), from Overview to Acceptance Criteria, with user approval at each step. Use it when you need a consistent, technically grounded per-system GDD ready for design review.

Game Design System guides section-by-section authoring of a single game system's GDD, gathering context from existing docs, cross-referencing dependencies, and writing incrementally to file. Use it to design game mechanics with consistency against a systems index and registry.

Gate Check validates readiness to advance between development phases. It produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts, used when someone asks whether the project is ready to move to the next stage.