Claude-Code-Game-Studios
Review Skills in Donchitos/Claude-Code-Game-Studios, with license, maintenance context, and source paths.
- Skills
- 26
- Repository stars
- 23,609
- Identity status
- Source-linked
Provenance
Source and identity
- Profile type
- Repository
- Canonical name
- Claude-Code-Game-Studios
- Public sources
- 1
- License context
- MIT
Source entries
Agent Skills from Claude-Code-Game-Studios
Repository stars and maintenance signals provide context, but do not automatically become an individual Skill's quality score.
Donchitos/Claude-Code-Game-Studios
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
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
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
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
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
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
dev-story
Read a story file and implement it. Loads the full context (story, GDD requirement, ADR guidelines, control manifest), routes to the right programmer agent for the system and engine, implements the code and test, and confirms each acceptance criterion. The core implementation skill — run after /story-readiness, before /code-review and /story-done.
Donchitos/Claude-Code-Game-Studios
gate-check
Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to X', 'can we advance to production', 'check if we can start the next phase', 'pass the gate'.
Donchitos/Claude-Code-Game-Studios
localize
Full localization pipeline: scan for hardcoded strings, extract and manage string tables, validate translations, generate translator briefings, run cultural/sensitivity review, manage VO localization, test RTL/platform requirements, enforce string freeze, and report coverage.
Donchitos/Claude-Code-Game-Studios
map-systems
Decompose a game concept into individual systems, map dependencies, prioritize design order, and create the systems index.
Donchitos/Claude-Code-Game-Studios
prototype
Concept prototype — validate the core idea is worth designing before writing GDDs. Run right after /brainstorm and /setup-engine. Routes to HTML, Engine, or Paper path based on game type. Produces a throwaway build and a PROCEED/PIVOT/KILL verdict.
Donchitos/Claude-Code-Game-Studios
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.
Pinned paths
Every entry links to a specific source path and commit when available.
Repository context
Activity, license, and repository-level popularity are shown as context.
Open the source
Inspect the public repository