Donchitos/Claude-Code-Game-Studios - 2ページ

reverse-document

Generate missing design or architecture docs from existing implementation — works backwards from code and prototypes.

原文の言語: 英語

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?'

原文の言語: 英語

security-audit

Security audit — save tampering, cheat vectors, network exploits, data exposure, input validation. Before public or multiplayer release.

原文の言語: 英語

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.

原文の言語: 英語

smoke-check

Critical-path smoke gate before QA hand-off — runs the automated suite. A failed check means the build is not QA-ready.

原文の言語: 英語

soak-test

Soak test protocol for extended play — what to observe and log for slow leaks, fatigue, late-appearing edge cases.

原文の言語: 英語

sprint-plan

New or updated sprint plan from the current milestone, completed work, and available capacity.

原文の言語: 英語

sprint-status

Fast, concise sprint snapshot — burndown and emerging risks for situational awareness. 'How is the sprint going?'

原文の言語: 英語

start

Guides a first-time user through onboarding and picks the right workflow. Use when the user is new, just cloned or installed the studio, has no idea or engine yet, asks where to begin, or wants to bring in an existing game.

原文の言語: 英語

story-done

Closes a finished story: verifies each acceptance criterion, checks for design or ADR deviations and updates its status. Use when the user says a story is done, finished or ready to close.

原文の言語: 英語

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

原文の言語: 英語

team-audio

Orchestrate the audio team — audio-director, sound-designer, technical-artist, gameplay-programmer — direction through implementation.

原文の言語: 英語

team-combat

Orchestrate the combat team — game-designer, gameplay-programmer, ai-programmer, technical-artist, sound-designer, qa-tester — design through implement and validate.

原文の言語: 英語

team-level

Orchestrate the level team — level-designer, narrative-director, world-builder, art-director, systems-designer, qa-tester — for complete area creation.

原文の言語: 英語

team-live-ops

Orchestrate the live-ops team — live-ops-designer, economy-designer, analytics-engineer, community-manager, writer — for a season or live event.

原文の言語: 英語

team-polish

Orchestrate the polish team — performance-analyst, technical-artist, sound-designer, qa-tester — to optimize and harden a feature or area.

原文の言語: 英語

team-release

Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.

原文の言語: 英語

team-ui

Orchestrate the UI team through the UX pipeline — authoring, visual design, implementation, review, polish. Uses /ux-design, /ux-review, studio templates.

原文の言語: 英語

tech-debt

Track, categorize and prioritize technical debt across the codebase — scans for debt indicators, maintains a register.

原文の言語: 英語

test-evidence-review

Quality review of test files and evidence — goes beyond existence, evaluates assertion coverage. ADEQUATE/INCOMPLETE/MISSING/NOT ASSESSED per story.

原文の言語: 英語

test-flakiness

Find flaky tests from CI logs — aggregates pass rates, spots intermittent failures, recommends quarantine. After multiple runs.

原文の言語: 英語

test-helpers

Generate engine-specific test helper libraries — assertion utilities, factory functions, mocks in the engine's test folder. Reduces boilerplate.

原文の言語: 英語

test-setup

Scaffold the test framework and CI — tests/ directory, engine test runner, GitHub Actions workflow. Once, before the first sprint.

原文の言語: 英語

ux-design

Section-by-section UX spec authoring for a screen, flow or HUD. Reads the player journey to provide context; also project-wide accessibility.

原文の言語: 英語

ux-review

Validate a UX spec, HUD design or pattern library — accessibility, GDD alignment, readiness. APPROVED / NOT ASSESSED / NEEDS REVISION / MAJOR REVISION NEEDED.

原文の言語: 英語

vertical-slice

Pre-production validation — end-to-end build to confirm the full loop is achievable before committing to Production. After GDDs, architecture, UX specs.

原文の言語: 英語

bug-triage

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

原文の言語: 英語

onboard

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

原文の言語: 英語

team-narrative

Orchestrate the narrative team — narrative-director, writer, world-builder, level-designer — for story, world lore, narrative-driven levels.

原文の言語: 英語

team-qa

Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.

原文の言語: 英語