mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-06-27 04:51:46 +00:00
* Add UPGRADING.md migration guide and link from README Covers v0.1→v0.2 upgrade with three strategies (git merge, cherry-pick, manual copy), file safety categories, and post-upgrade verification steps. Structured to support future version sections. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Rename /design-systems to /map-systems + /design-system and fix all references Split the monolithic /design-systems skill into two focused skills: - /map-systems: systems decomposition and index creation - /design-system: guided section-by-section GDD authoring Updated all cross-references across 14 files: README, UPGRADING, WORKFLOW-GUIDE, quick-start, skills-reference, game-concept template, systems-index template, brainstorm, design-review, gate-check, project-stage-detect, setup-engine, and start skills. Fixed skill counts from 36 to 37 everywhere. Added /map-systems and /design-system to quick-start Paths A and B workflows. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix cross-reference gaps, broken hooks, and stale workflow chains - Fix log-agent.sh parsing agent_type instead of agent_name (always logged "unknown") - Fix GDD status lifecycle: design-system now writes Approved/Designed/In Review - Clean up settings.local.json vestigial Bash grants from development - Delete orphaned docs marked for removal in UPGRADING.md - Add /design-system to next-steps in /start, /brainstorm, /setup-engine - Fix WORKFLOW-GUIDE: add /map-systems + /design-system to Appendix C Workflow 1 - Fix invalid /map-systems map argument in WORKFLOW-GUIDE Step 2.1 - Update map-systems frontmatter to document [system-name] argument - Update commit hook to validate all 8 required GDD sections (was 5) - Update README template count 28 → 29, add 5 missing templates to quick-start Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add custom status line with 7-stage production pipeline Introduces a status line showing context %, model name, and production stage at a glance. Aligns gate-check and project-stage-detect to a unified 7-stage model (Concept → Systems Design → Technical Setup → Pre-Production → Production → Polish → Release). Stage is determined by explicit override (production/stage.txt) or auto-detected from project artifacts. Epic/Feature/Task breadcrumb appears conditionally in Production+ stages via a structured STATUS block in active.md. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add v0.2→v0.3 upgrade guide and PR validation test suite - UPGRADING.md: add v0.2.0→v0.3.0 section documenting breaking rename of /design-systems→/map-systems, new /design-system skill, statusline.sh, gate-check stage advancement, and safe-to-overwrite file list Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
3.5 KiB
3.5 KiB
Available Skills (Slash Commands)
| Command | Purpose |
|---|---|
/start |
First-time onboarding — asks where you are, then guides you to the right workflow |
/design-review |
Review a game design document for completeness and consistency |
/code-review |
Architectural code review for a file or changeset |
/playtest-report |
Generate a structured playtest report template |
/balance-check |
Analyze game balance data and flag outliers |
/sprint-plan |
Generate or update a sprint plan |
/bug-report |
Create a structured bug report |
/architecture-decision |
Create an Architecture Decision Record (ADR) |
/asset-audit |
Audit assets for naming, sizing, and pipeline compliance |
/milestone-review |
Review milestone progress and generate status report |
/onboard |
Generate onboarding context for a new contributor or agent |
/prototype |
Scaffold a throwaway prototype to test a mechanic or technical approach |
/release-checklist |
Generate and validate a pre-release checklist for the current build |
/changelog |
Auto-generate changelog from git commits and sprint data |
/retrospective |
Run a structured sprint or milestone retrospective |
/estimate |
Produce a structured effort estimate with complexity and risk breakdown |
/hotfix |
Emergency fix workflow with audit trail, bypassing normal sprint process |
/tech-debt |
Scan, track, prioritize, and report on technical debt across the codebase |
/scope-check |
Analyze feature or sprint scope against original plan, flag scope creep |
/localize |
Localization workflow: scan for hardcoded strings, extract, validate translations |
/perf-profile |
Structured performance profiling with bottleneck identification and recommendations |
/project-stage-detect |
Automatically analyze project state, detect stage, identify gaps, and recommend next steps |
/reverse-document |
Generate design or architecture documents from existing implementation (works backwards from code) |
/team-combat |
Orchestrate combat team: game-designer + gameplay-programmer + ai-programmer + technical-artist + sound-designer + qa-tester |
/team-narrative |
Orchestrate narrative team: narrative-director + writer + world-builder + level-designer |
/team-ui |
Orchestrate UI team: ux-designer + ui-programmer + art-director |
/team-release |
Orchestrate release team: release-manager + qa-lead + devops-engineer + producer |
/team-polish |
Orchestrate polish team: performance-analyst + technical-artist + sound-designer + qa-tester |
/team-audio |
Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer |
/team-level |
Orchestrate level team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester |
/launch-checklist |
Complete launch readiness validation across all departments |
/patch-notes |
Generate player-facing patch notes from git history and internal data |
/brainstorm |
Guided ideation using professional studio methods (MDA, SDT, Bartle, verb-first) |
/gate-check |
Validate readiness to advance between development phases (PASS/CONCERNS/FAIL) |
/map-systems |
Decompose game concept into systems, map dependencies, prioritize design order, guide per-system GDDs |
/design-system |
Guided, section-by-section GDD authoring for a single game system with cross-referencing and incremental writing |
/setup-engine |
Configure engine + version, detect knowledge gaps, populate version-aware reference docs |