What problem does it solve? Choosing and configuring a game engine (Unity, Godot, Unreal, or browser-based) is risky when done blindly: wrong versions, conflicting MCP servers, and irreversible changes can break a project. This Skill inspects the environment first and proposes one fully reversible, confirmation-gated setup plan before anything changes. ## Core Features & Use Cases - Read-only environment inspection: Runs toolchain-doctor checks and detects existing Unity, Godot, Unreal, browser, and project evidence before asking the user to choose an engine. - Engine comparison and recommendation: Compares viable engines by project fit, platform export, language, maturity, performance, accessibility, license, install size, and existing investment, then recommends one engine and one adapter. - Reversible transaction plan: Produces a single transaction with plan_id, pinned sources, downloads, licenses, permissions, backups, health checks, rollback operations, expiry, and digest, showing every file that would be materialized (AGENTS.md, .codex/agents/*.toml, .ai-game-studio/project.json, lock.json). - Use Case: A developer starting a new game project asks Codex to set up an engine; the Skill detects the OS, GPU, and existing tools, proposes Godot with exact pinned versions and rollback steps, and waits for explicit digest confirmation before applying anything. ## Quick Start Ask Codex to use the setup-engine skill to inspect this project and propose one reversible engine setup without changing anything yet.
