Setup Engine

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — INTEGRATED SYSTEM FIRST: this skill is one piece of the complete "Claude Code Game Studios" template (49 agents, 74 skills, studio templates and a studio CLAUDE.md, per the repository README). Each skill assumes that template is installed, with its conventions, its project.yaml / project.local.yaml configuration, its .claude/docs/ mode documents, its hooks (for example hooks/yaml-helper.sh, outside this skill's folder) and its .claude/scripts/ helpers. Installing this listing alone copies only this skill's folder, without the rest of the system: the skill may reference template agents, files, hooks or scripts that are absent outside the full template, and it may not run as designed on its own. No account, no key and no payment are needed to copy the files, and nothing is run during installation. At use time this one also makes network calls (WebSearch and WebFetch for engine version lookups, reference docs and migration guides, all disclosed below) and runs local engine probes and template scripts. Install "Setup Engine" for me. The skill itself configures the game engine and version for a game project, in four modes: full spec (engine and version given), engine only (the version is looked up), no arguments (fully guided selection, with questions on experience and target platform), refresh (update the engine reference docs), and upgrade (migrate to a new engine version). It looks the current version up with WebSearch rather than guessing, shows the proposed CLAUDE.md Technology Stack and asks "May I write these engine settings to CLAUDE.md?", then dual-writes the engine configuration to project.yaml (the primary config store) and .claude/docs/technical-preferences.md (the legacy mirror), determines the knowledge gap for the chosen version, and creates reference docs under docs/engine-reference/<engine>/ — using WebSearch and WebFetch when the version is beyond the model's training data, and never filling a gap from training data. For Godot it can scaffold project.godot when one is absent (shown, then asked: "May I create project.godot at the repo root?"); for Unity and Unreal it does not create the project and tells the user to create it in the editor first. It may also add a Version Awareness section to the engine specialist agent files, after asking. It runs local probes allowed in its frontmatter (godot --version, a headless import, command -v godot, uname -s) and the template's .claude/scripts/project-coherence.sh, resolves the workflow tier by running the template's hooks/yaml-helper.sh (outside this skill's folder), and follows its twelve phase files under references/ in turn. Its frontmatter pins model: sonnet. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/setup-engine/ folder at the pinned commit: 13 files in total) Pinned version: install the code at commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/Donchitos/Claude-Code-Game-Studios into a temporary folder, check out commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418, and copy the .claude/skills/setup-engine/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 37c08d68ed58b70e6880e269e711e2617b89f2f165d9bba5d966e326e73e9a17 - references/11-upgrade.md: SHA-256 4099ab07db41a6ef9cc7c19280c52e1241b3c1cb46621aeffed3365ab466d248 - references/12-output-summary.md: SHA-256 0d722f38faecad23c1acf89aa085d6bf9a5db3f0814129c11869a013b2dc90bb - references/2-guided-mode.md: SHA-256 77ef8e043ef536db796f3d32a78d960ecde7a8320caf568f30b7b93036128ffa - references/3-version.md: SHA-256 e39430dbb5b1e0afe002568fb150ebd123de5079be48d5a257ada36a22be74ac - references/4-claude-md-stack.md: SHA-256 a122df4ebb9167c2defa5a8b9dc5b6a4a649e29f0c48eb43795a1230fb24d2cf - references/5-technical-preferences.md: SHA-256 fc332503d281bfbd6163b89f835276ba4ad3f3d6d17ec6df673ffbe2d0103aa5 - references/5.5-project-yaml.md: SHA-256 853492f39487b65f8155d8dc972e7861adbd01087068c3c525a2954f45b601bd - references/6-knowledge-gap.md: SHA-256 694517ca40542c55b671af5c47afe39420dbe9170b29f749e479894acef67a27 - references/7-reference-docs.md: SHA-256 f072c0a70331e75f7931b5b9ed4d63c9b10b5455e044683616220b4f7846704e - references/7.5-scaffold.md: SHA-256 4906f271bd3020520dfe22716f65fb1a8df60554946faf74be810611cb383e22 - references/8-verify.md: SHA-256 9d75412fd622ec9a51686a9ba81bc9e3f81b097eee0cba22e8cf67bd38d15fa1 - references/godot-language-config.md: SHA-256 82b2aad2ad6a63616c30a5168f720eb6e83ca40e585bddf82dc13395a0a7d404 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 13 files: SKILL.md plus 12 files under references/ (11-upgrade, 12-output-summary, 2-guided-mode, 3-version, 4-claude-md-stack, 5-technical-preferences, 5.5-project-yaml, 6-knowledge-gap, 7-reference-docs, 7.5-scaffold, 8-verify, godot-language-config). Nothing in the folder is a program; the reference files are instructions the skill reads and follows, phase by phase, at use time. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no project of mine is audited, read or modified. - Integrated-system reality, from the files: at use time the skill runs the template's hooks/yaml-helper.sh to resolve the workflow tier, reads and writes CLAUDE.md, project.yaml and .claude/docs/technical-preferences.md, uses WebSearch and WebFetch for version lookups, reference docs and migration guides (network calls to the web, disclosed in the prerequisites), and runs local probes (godot --version, a headless Godot import) and the template's .claude/scripts/project-coherence.sh — the hook, the scripts and the .claude/docs/ files live outside this skill's folder and are absent in a standalone install, so it cannot run as designed on its own. - At use time its writes are shown or asked first: the CLAUDE.md Technology Stack (asked), the project.yaml / technical-preferences.md dual-write, the engine reference docs under docs/engine-reference/<engine>/ (creation asked, and existing docs are never overwritten without asking), a Godot project.godot scaffold (shown, then asked; never overwriting an existing one), and Version Awareness sections in the engine specialist agent files (asked first). The data it sends at use time is limited to web search and fetch queries about engine versions, APIs and migration guides; no project file is uploaded by the skill itself, and no account or credential is named in the files. - Do not configure any engine, do not run godot, any template hook or script, do not use WebSearch or WebFetch, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole setup-engine folder into the agent's skills directory, in a folder named exactly "setup-engine", keeping its 13 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: setup-engine), the 13 files in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that it belongs to the full Claude Code Game Studios template and may not run standalone (it resolves its tier through the template's yaml-helper hook and writes the template's CLAUDE.md, project.yaml and docs files), and that at use time it makes WebSearch/WebFetch calls about engine versions, runs local engine probes, and writes its configuration and reference docs only after showing or asking). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.