Choose a game engine and version, record the choice in project configuration, and prepare reference documents for newer releases. The skill also supports refreshing those references and guiding migration between engine versions.
Configure engine and version. Pins it in CLAUDE.md; WebSearch fills reference docs when the version is beyond LLM training data.
Review the instructions the agent will receive before you install.
When this skill is invoked:
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys workflow
Tier awareness. The workflow tier resolved above governs which design
artifact this skill expects and the finish path it recommends in §12:
minimal — the design artifact is the one-page design/game-brief.md
(no GDDs, systems decomposition, or per-system design at this tier).
/setup-engine runs first in the minimal path, so a missing brief here is
normal, not a gap. The finish path is the 4-step floor.standard / full — the design artifact is design/gdd/game-concept.md
and the finish path is the full pipeline.If the block did not render (shell preprocessing disabled), assume minimal (the default).
Four modes:
/setup-engine godot 4.6 — engine and version provided/setup-engine unity — engine provided, version will be looked up/setup-engine — fully guided mode (engine recommendation + version)/setup-engine refresh — update reference docs (see Section 10)/setup-engine upgrade [old-version] [new-version] — migrate to a new engine version (see Section 11)Read references/2-guided-mode.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Read references/3-version.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Read references/4-claude-md-stack.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Read references/5-technical-preferences.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
project.yaml (Primary Config Store)Read references/5.5-project-yaml.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Read references/6-knowledge-gap.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Read references/7-reference-docs.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Read references/7.5-scaffold.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Read references/8-verify.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Ask: "May I add a Version Awareness section to the engine specialist agent files?" before making any edits.
For the chosen engine's specialist agents, verify they have a "Version Awareness" section. If not, add one following the pattern in the existing Godot specialist agents.
The section should instruct the agent to:
docs/engine-reference/<engine>/VERSION.mdIf invoked as /setup-engine refresh:
docs/engine-reference/<engine>/VERSION.md to get
the current engine and versionRead references/11-upgrade.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Read references/12-output-summary.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
project.yaml is the primary config store (v1.1). Always dual-write engine
config to BOTH project.yaml (primary) and technical-preferences.md (legacy
mirror). If the two ever diverge, project.yaml is authoritative.references/godot-language-config.md exactly. NEVER add "C++ via GDExtension" to the Language field. GDScript projects may use GDExtension, but it is not a primary project language. The godot-gdextension-specialist in the routing table is available for when native extensions are needed — it does not make C++ a project language.Moved out of this file so it costs nothing on non-Godot runs.
When the chosen engine is Godot, read
references/godot-language-config.md
and use the subsection for the chosen language:
Load discipline. On any engine other than Godot, never load it — nothing in Sections 4, 5 or 5.5 needs it, and reading it anyway spends the tokens the split exists to save. On Godot, read it once when you first reach Section 4 and keep using it for Sections 5 and 5.5; do not re-read it at each reference.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Audit an existing project's design documents and supporting files to check whether their formats work with the template's skills. Get a numbered migration plan that prioritizes gaps and required changes, rather than simply listing what exists.
Document a technical decision in an architecture decision record, or ADR. Capture its context, alternatives, and consequences, assign a record number, and distinguish a proposed decision from an accepted one so dependent work reflects its actual status.
Review whether game design requirements are covered by documented architecture decisions. Identify missing coverage, conflicting decisions, and engine compatibility concerns, with an optional matrix linking requirements to development stories and tests.
Create a game's art direction document, defining its visual rules, mood, shapes, colors, and production standards. Review and approve sections individually, with guidance that connects character, environment, and interface design to the game's concept and technical constraints.
Audit game asset files for naming rules, size limits, formats, and broken references. Receive a report of measured violations and suggested fixes, with clear explanations of checks that lack data or cannot be assessed for the engine.
Turn game design documents and character profiles into asset specifications and image generation prompts. Define appearance, dimensions, file formats, and naming rules, then maintain an asset list that tracks progress and identifies shared assets.