Donchitos/Claude-Code-Game-Studios

adopt

Brownfield audit — do existing artifacts actually work? Numbered migration plan. Unlike /project-stage-detect, checks compliance not existence.

원문 언어: 영어

architecture-decision

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

원문 언어: 영어

architecture-review

Traceability matrix mapping GDD requirements to ADRs. Finds gaps, cross-ADR conflicts, engine compatibility. PASS/CONCERNS/NOT ASSESSED/FAIL.

원문 언어: 영어

art-bible

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

원문 언어: 영어

asset-audit

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

원문 언어: 영어

asset-spec

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

원문 언어: 영어

balance-check

Find balance outliers, broken progressions, degenerate strategies, economy imbalances in formulas and data. 'Check game balance'.

원문 언어: 영어

brainstorm

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

원문 언어: 영어

bug-report

Structured bug report from a description, or analyze code for potential bugs. Reproduction steps, severity.

원문 언어: 영어

bug-triage

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

원문 언어: 영어

changelog

Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.

원문 언어: 영어

code-review

Architectural code review — coding standards, SOLID, testability, performance concerns.

원문 언어: 영어

consistency-check

Scan GDDs against the entity registry for cross-document conflicts. Grep-first approach targets conflicting sections, different stats.

원문 언어: 영어

content-audit

Audit GDD content counts against what's implemented — planned vs built.

원문 언어: 영어

create-architecture

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

원문 언어: 영어

create-stories

Break one epic into implementable stories embedding TR-ID, ADR guidance, acceptance criteria. Reads the control manifest. After /create-epics.

원문 언어: 영어

day-one-patch

Day-one launch patch — focused fix for known issues found after gold master. Mini-sprint with QA gate and rollback.

원문 언어: 영어

design-review

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

원문 언어: 영어

design-system

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

원문 언어: 영어

dev-story

Implement a story: ADR guidelines, right programmer agent, code plus test. Then /story-done (/story-readiness before, /code-review after, at standard/full).

원문 언어: 영어

estimate

Estimate task effort from complexity, dependencies, velocity, risk. Structured estimate with confidence levels.

원문 언어: 영어

gate-check

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

원문 언어: 영어

hotfix

Emergency fix bypassing normal sprint process — hotfix branch, approvals tracked, backport verified, full audit trail.

원문 언어: 영어

launch-checklist

Launch readiness across every department: code, content, store, marketing, community, infrastructure, legal, go/no-go sign-offs.

원문 언어: 영어

map-systems

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

원문 언어: 영어

milestone-review

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

원문 언어: 영어

onboard

Onboarding doc for a new contributor or agent — project state, conventions, priorities relevant to the specified role.

원문 언어: 영어

patch-notes

Player-facing patch notes from git history and changelogs. Translates developer language into player communication.

원문 언어: 영어

perf-profile

Performance profiling — find bottlenecks, measure against budgets, produce ranked optimization recommendations.

원문 언어: 영어

playtest-report

Structured playtest report template, or turn existing playtest notes into structured feedback.

원문 언어: 영어

prototype

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

원문 언어: 영어

regression-suite

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

원문 언어: 영어

release-checklist

Pre-release checklist — build verification, certification requirements, store metadata, launch readiness.

원문 언어: 영어

retrospective

Sprint or milestone retrospective from completed work, velocity, blockers. Actionable insights for the next iteration.

원문 언어: 영어

review-all-gdds

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

원문 언어: 영어

scope-check

Scope creep check — current scope versus the original plan. Flags additions, quantifies bloat, recommends cuts. 'Any scope creep?'

원문 언어: 영어

settings

View or change project config — effective merged values, or set locally in project.local.yaml.

원문 언어: 영어

setup-engine

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

원문 언어: 영어

skill-improve

Improve a skill via a test-fix-retest loop — static checks, targeted fixes, keep or revert on score change.

원문 언어: 영어

skill-test

Validate skill files for structural compliance and behavioral correctness. Four modes: static linter, spec, category rubric, audit.

원문 언어: 영어