Sponsored by

Find leads on Reddit on auto pilot

Topic: godot

72 skills in this topic.

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
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
start First-time onboarding — asks where you are, then guides you to the right workflow. No assumptions.
Donchitos/Claude-Code-Game-Studios 8,725
architecture-review Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /design-review.
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
asset-audit Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.
Donchitos/Claude-Code-Game-Studios 8,725
asset-spec Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.
Donchitos/Claude-Code-Game-Studios 8,725
ux-review Validates a UX spec, HUD design, or interaction pattern library for completeness, accessibility compliance, GDD alignment, and implementation readiness. Produces APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED verdict with specific gaps.
Donchitos/Claude-Code-Game-Studios 8,725
team-polish Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.
Donchitos/Claude-Code-Game-Studios 8,725
bug-report Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context.
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
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
code-review Performs an architectural and quality code review on a specified file or set of files. Checks for coding standard compliance, architectural pattern adherence, SOLID principles, testability, and performance concerns.
Donchitos/Claude-Code-Game-Studios 8,725
adopt Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this when joining an in-progress project or upgrading from an older template version. Distinct from /project-stage-detect (which checks what exists) — this checks whether what exists will actually work with the template's skills.
Donchitos/Claude-Code-Game-Studios 8,725
content-audit Audit GDD-specified content counts against implemented content. Identifies what's planned vs built.
Donchitos/Claude-Code-Game-Studios 8,725
test-setup Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. Run once during Technical Setup phase before the first sprint begins.
Donchitos/Claude-Code-Game-Studios 8,725
team-live-ops Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
Donchitos/Claude-Code-Game-Studios 8,725
create-epics Translate approved GDDs + architecture into epics — one epic per architectural module. Defines scope, governing ADRs, engine risk, and untraced requirements. Does NOT break into stories — run /create-stories [epic-slug] after each epic is created.
Donchitos/Claude-Code-Game-Studios 8,725
create-stories Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
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
design-review Reviews a game design document for completeness, internal consistency, implementability, and adherence to project design standards. Run this before handing a design document to programmers.
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
soak-test Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.
Donchitos/Claude-Code-Game-Studios 8,725
test-helpers Generate engine-specific test helper libraries for the project's test suite. Reads existing test patterns and produces tests/helpers/ with assertion utilities, factory functions, and mock objects tailored to the project's systems. Reduces boilerplate in new test files.
Donchitos/Claude-Code-Game-Studios 8,725