Donchitos/Claude-Code-Game-Studios - 2페이지

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.

원문 언어: 영어

start

First-time onboarding — asks where you are, then guides you to the right workflow.

원문 언어: 영어

story-done

End-of-story completion review — verifies each acceptance criterion, checks GDD/ADR deviations, prompts code review, updates status.

원문 언어: 영어

story-readiness

Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.

원문 언어: 영어

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-narrative

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

원문 언어: 영어

team-polish

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

원문 언어: 영어

team-qa

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

원문 언어: 영어

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-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.

원문 언어: 영어

create-control-manifest

Flat must-do/never-do rules sheet per system and layer, extracted from Accepted ADRs. ADRs explain why; this is actionable.

원문 언어: 영어

create-epics

Turn GDDs plus architecture into epics — one per architectural module, with untraced requirements. Then /create-stories [epic-slug].

원문 언어: 영어

help

What should I do next? Use when stuck or you don't know what to do.

원문 언어: 영어

localize

Localization pipeline — find hardcoded strings, extract string tables, cultural review, VO, RTL, enforce string freeze.

원문 언어: 영어

project-stage-detect

Analyze project state, detect stage, identify gaps, recommend next steps. 'Where are we in development?'

원문 언어: 영어

propagate-design-change

A GDD changed — scan ADRs and the traceability index for now-stale architectural decisions. Impact report, guides resolution.

원문 언어: 영어

qa-plan

QA test plan for a sprint — classifies stories by Logic/Integration/Visual/UI, covers automated tests, manual cases, smoke scope.

원문 언어: 영어

quick-design

Lightweight spec for small changes — tuning adjustments, minor mechanics. Embeds directly into stories; skips full GDD.

원문 언어: 영어

reverse-document

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

원문 언어: 영어

security-audit

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

원문 언어: 영어

sprint-status

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

원문 언어: 영어

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.

원문 언어: 영어