Donchitos/Claude-Code-Game-Studios - Seite 2

reverse-document

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

Quellsprache: Englisch

review-all-gdds

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

Quellsprache: Englisch

scope-check

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

Quellsprache: Englisch

security-audit

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

Quellsprache: Englisch

settings

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

Quellsprache: Englisch

setup-engine

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

Quellsprache: Englisch

skill-improve

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

Quellsprache: Englisch

skill-test

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

Quellsprache: Englisch

smoke-check

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

Quellsprache: Englisch

soak-test

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

Quellsprache: Englisch

sprint-plan

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

Quellsprache: Englisch

sprint-status

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

Quellsprache: Englisch

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.

Quellsprache: Englisch

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.

Quellsprache: Englisch

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.

Quellsprache: Englisch

team-audio

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

Quellsprache: Englisch

team-combat

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

Quellsprache: Englisch

team-level

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

Quellsprache: Englisch

team-live-ops

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

Quellsprache: Englisch

team-polish

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

Quellsprache: Englisch

team-release

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

Quellsprache: Englisch

team-ui

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

Quellsprache: Englisch

tech-debt

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

Quellsprache: Englisch

test-evidence-review

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

Quellsprache: Englisch

test-flakiness

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

Quellsprache: Englisch

test-helpers

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

Quellsprache: Englisch

test-setup

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

Quellsprache: Englisch

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.

Quellsprache: Englisch

ux-review

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

Quellsprache: Englisch

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.

Quellsprache: Englisch

bug-triage

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

Quellsprache: Englisch

onboard

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

Quellsprache: Englisch

team-narrative

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

Quellsprache: Englisch

team-qa

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

Quellsprache: Englisch