Donchitos/Claude-Code-Game-Studios

这个仓库里有 73 个技能，GitHub 星标 ★ 25,146。

• adoptBrownfield onboarding — audits existing project artifacts for template format co
• architecture-decisionCreates an Architecture Decision Record (ADR) documenting a significant technica
• architecture-reviewValidates completeness and consistency of the project architecture against all G
• art-bibleGuided, section-by-section Art Bible authoring. Creates the visual identity spec
• asset-auditAudits game assets for compliance with naming conventions, file size budgets, fo
• asset-specGenerate per-asset visual specifications and AI generation prompts from GDDs, le
• balance-checkAnalyzes game balance data files, formulas, and configuration to identify outlie
• brainstormGuided game concept ideation — from zero idea to a structured game concept docum
• bug-reportCreates a structured bug report from a description, or analyzes code to identify
• bug-triageRead all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, as
• changelogAuto-generates a changelog from git commits, sprint data, and design documents.
• code-reviewPerforms an architectural and quality code review on a specified file or set of
• consistency-checkScan all GDDs against the entity registry to detect cross-document inconsistenci
• content-auditAudit GDD-specified content counts against implemented content. Identifies what'
• create-architectureGuided, section-by-section authoring of the master architecture document for the
• create-control-manifestAfter architecture is complete, produces a flat actionable rules sheet for progr
• create-epicsTranslate approved GDDs + architecture into epics — one epic per architectural m
• create-storiesBreak a single epic into implementable story files. Reads the epic, its GDD, gov
• day-one-patchPrepare a day-one patch for a game launch. Scopes, prioritises, implements, and
• design-reviewReviews a game design document for completeness, internal consistency, implement
• design-systemGuided, section-by-section GDD authoring for a single game system. Gathers conte
• dev-storyRead a story file and implement it. Loads the full context (story, GDD requireme
• estimateEstimates task effort by analyzing complexity, dependencies, historical velocity
• gate-checkValidate readiness to advance between development phases. Produces a PASS/CONCER
• helpAnalyzes what is done and the users query and offers advice on what to do next.
• hotfixEmergency fix workflow that bypasses normal sprint processes with a full audit t
• launch-checklistComplete launch readiness validation covering every department: code, content, s
• localizeFull localization pipeline: scan for hardcoded strings, extract and manage strin
• map-systemsDecompose a game concept into individual systems, map dependencies, prioritize d
• milestone-reviewGenerates a comprehensive milestone progress review including feature completene
• onboardGenerates a contextual onboarding document for a new contributor or agent joinin
• patch-notesGenerate player-facing patch notes from git history, sprint data, and internal c
• perf-profileStructured performance profiling workflow. Identifies bottlenecks, measures agai
• playtest-reportGenerates a structured playtest report template or analyzes existing playtest no
• project-stage-detectAutomatically analyze project state, detect stage, identify gaps, and recommend
• propagate-design-changeWhen a GDD is revised, scans all ADRs and the traceability index to identify whi
• prototypeConcept prototype — validate the core idea is worth designing before writing GDD
• qa-planGenerate a QA test plan for a sprint or feature. Reads GDDs and story files, cla
• quick-designLightweight design spec for small changes — tuning adjustments, minor mechanics,
• regression-suiteMap test coverage to GDD critical paths, identify fixed bugs without regression
• release-checklistGenerates a comprehensive pre-release validation checklist covering build verifi
• retrospectiveGenerates a sprint or milestone retrospective by analyzing completed work, veloc
• reverse-documentGenerate design or architecture documents from existing implementation. Works ba
• review-all-gddsHolistic cross-GDD consistency and game design review. Reads all system GDDs sim
• scope-checkAnalyze a feature or sprint for scope creep by comparing current scope against t
• security-auditAudit the game for security vulnerabilities: save tampering, cheat vectors, netw
• setup-engineConfigure the project's game engine and version. Pins the engine in CLAUDE.md, d
• skill-improveImprove a skill using a test-fix-retest loop. Runs static checks, proposes targe
• skill-testValidate skill files for structural compliance and behavioral correctness. Three
• smoke-checkRun the critical path smoke test gate before QA hand-off. Executes the automated
• soak-testGenerate a soak test protocol for extended play sessions. Defines what to observ
• sprint-planGenerates a new sprint plan or updates an existing one based on the current mile
• sprint-statusFast sprint status check. Reads the current sprint plan, scans story files for s
• startFirst-time onboarding — asks where you are, then guides you to the right workflo
• story-doneEnd-of-story completion review. Reads the story file, verifies each acceptance c
• story-readinessValidate that a story file is implementation-ready. Checks for embedded GDD requ
• team-audioOrchestrate audio team: audio-director + sound-designer + technical-artist + gam
• team-combatOrchestrate the combat team: coordinates game-designer, gameplay-programmer, ai-
• team-levelOrchestrate level design team: level-designer + narrative-director + world-build
• team-live-opsOrchestrate the live-ops team for post-launch content planning: coordinates live
• team-narrativeOrchestrate the narrative team: coordinates narrative-director, writer, world-bu
• team-polishOrchestrate the polish team: coordinates performance-analyst, technical-artist,
• team-qaOrchestrate the QA team through a full testing cycle. Coordinates qa-lead (strat
• team-releaseOrchestrate the release team: coordinates release-manager, qa-lead, devops-engin
• team-uiOrchestrate the UI team through the full UX pipeline: from UX spec authoring thr
• tech-debtTrack, categorize, and prioritize technical debt across the codebase. Scans for
• test-evidence-reviewQuality review of test files and manual evidence documents. Goes beyond existenc
• test-flakinessDetect non-deterministic (flaky) tests by reading CI run logs or test result his
• test-helpersGenerate engine-specific test helper libraries for the project's test suite. Rea
• test-setupScaffold the test framework and CI/CD pipeline for the project's engine. Creates
• ux-designGuided, section-by-section UX spec authoring for a screen, flow, or HUD. Reads g
• ux-reviewValidates a UX spec, HUD design, or interaction pattern library for completeness
• vertical-slicePre-Production validation — build a production-quality end-to-end build to confi