Engine Setup

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

1. Parse Arguments

Four modes:

• Full spec: /setup-engine godot 4.7, engine and version provided
• Engine only: /setup-engine unity, engine provided, version will be looked up
• No args: /setup-engine, fully guided mode (engine recommendation + version)
• Refresh: /setup-engine refresh, update reference docs (see Section 10)
• Upgrade: /setup-engine upgrade [old-version] [new-version], migrate to a new engine version (see Section 11)

---

2. Guided Mode (No Arguments)

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.

3. Look Up Current Version

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.

4. Update CLAUDE.md Technology Stack

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.

5. Populate Technical Preferences