Sponsored by

Find leads on Reddit on auto pilot

Agent skills
claude-code

Topic: claude-code

35,830 skills in this topic.

smoke-check Run the critical path smoke test gate before QA hand-off. Executes the automated test suite, verifies core functionality, and produces a PASS/FAIL report. Run after a sprint's stories are implemented and before manual QA begins. A failed smoke check means the build is not ready for QA.
Donchitos/Claude-Code-Game-Studios 8,725
story-readiness Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is story X ready to implement'.
Donchitos/Claude-Code-Game-Studios 8,725
changelog Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
Donchitos/Claude-Code-Game-Studios 8,725
help Analyzes what is done and the users query and offers advice on what to do next. Use if user says what should I do next or what do I do now or I'm stuck or I don't know what to do
Donchitos/Claude-Code-Game-Studios 8,725
playtest-report Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
Donchitos/Claude-Code-Game-Studios 8,725
create-architecture Guided, section-by-section authoring of the master architecture document for the game. Reads all GDDs, the systems index, existing ADRs, and the engine reference library to produce a complete architecture blueprint before any code is written. Engine-version-aware: flags knowledge gaps and validates decisions against the pinned engine version.
Donchitos/Claude-Code-Game-Studios 8,725
balance-check Analyzes game balance data files, formulas, and configuration to identify outliers, broken progressions, degenerate strategies, and economy imbalances. Use after modifying any balance-related data or design. Use when user says 'balance report', 'check game balance', 'run a balance check'.
Donchitos/Claude-Code-Game-Studios 8,725
bug-triage Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
Donchitos/Claude-Code-Game-Studios 8,725
art-bible Guided, section-by-section Art Bible authoring. Creates the visual identity specification that gates all asset production. Run after /brainstorm is approved and before /map-systems or any GDD authoring begins.
Donchitos/Claude-Code-Game-Studios 8,725
skill-test Validate skill files for structural compliance and behavioral correctness. Three modes: static (linter), spec (behavioral), audit (coverage report).
Donchitos/Claude-Code-Game-Studios 8,725
retrospective Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration.
Donchitos/Claude-Code-Game-Studios 8,725
hotfix Emergency fix workflow that bypasses normal sprint processes with a full audit trail. Creates hotfix branch, tracks approvals, and ensures the fix is backported correctly.
Donchitos/Claude-Code-Game-Studios 8,725
start First-time onboarding — asks where you are, then guides you to the right workflow. No assumptions.
Donchitos/Claude-Code-Game-Studios 8,725
perf-profile Structured performance profiling workflow. Identifies bottlenecks, measures against budgets, and generates optimization recommendations with priority rankings.
Donchitos/Claude-Code-Game-Studios 8,725
onboard Generates a contextual onboarding document for a new contributor or agent joining the project. Summarizes project state, architecture, conventions, and current priorities relevant to the specified role or area.
Donchitos/Claude-Code-Game-Studios 8,725
design-system Guided, section-by-section GDD authoring for a single game system. Gathers context from existing docs, walks through each required section collaboratively, cross-references dependencies, and writes incrementally to file.
Donchitos/Claude-Code-Game-Studios 8,725
patch-notes Generate player-facing patch notes from git history, sprint data, and internal changelogs. Translates developer language into clear, engaging player communication.
Donchitos/Claude-Code-Game-Studios 8,725
release-checklist Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.
Donchitos/Claude-Code-Game-Studios 8,725
qa-plan Generate a QA test plan for a sprint or feature. Reads GDDs and story files, classifies stories by test type (Logic/Integration/Visual/UI), and produces a structured test plan covering automated tests required, manual test cases, smoke test scope, and playtest sign-off requirements. Run before sprint begins or when starting a major feature.
Donchitos/Claude-Code-Game-Studios 8,725
create-control-manifest After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).
Donchitos/Claude-Code-Game-Studios 8,725
consistency-check Scan all GDDs against the entity registry to detect cross-document inconsistencies: same entity with different stats, same item with different values, same formula with different variables. Grep-first approach — reads registry then targets only conflicting GDD sections rather than full document reads.
Donchitos/Claude-Code-Game-Studios 8,725
launch-checklist Complete launch readiness validation covering every department: code, content, store, marketing, community, infrastructure, legal, and go/no-go sign-offs.
Donchitos/Claude-Code-Game-Studios 8,725
day-one-patch Prepare a day-one patch for a game launch. Scopes, prioritises, implements, and QA-gates a focused patch addressing known issues discovered after gold master but before or immediately after public launch. Treats the patch as a mini-sprint with its own QA gate and rollback plan.
Donchitos/Claude-Code-Game-Studios 8,725
sprint-status Fast sprint status check. Reads the current sprint plan, scans story files for status, and produces a concise progress snapshot with burndown assessment and emerging risks. Run at any time during a sprint for quick situational awareness. Use when user asks 'how is the sprint going', 'sprint update', 'show sprint progress'.
Donchitos/Claude-Code-Game-Studios 8,725