What problem does it solve? Choosing and configuring a game engine (Unity, Godot, Unreal, or browser-based) is risky: wrong picks, unmanaged installs, and undocumented changes can break a project. This Skill inspects the environment, compares viable engines, and produces a fully auditable, reversible setup plan before anything is changed. ## Core Features & Use Cases - Read-only environment detection: Runs toolchain-doctor checks and detects existing Unity, Godot, Unreal, browser, and project evidence before asking the user to choose. - Engine comparison and recommendation: Compares engines by project fit, platform export, team language, maturity, performance, accessibility, license, install size, and existing investment, then recommends one engine and one adapter. - Transactional planning: Produces a single transaction with plan_id, exact actions, pinned sources, downloads, licenses, backups, health checks, rollback operations, expiry, and a digest that must be explicitly confirmed before any apply step. - Use Case: A team starting a new game project asks the assistant to evaluate their Windows machine, compare Godot versus Unity for a 2D mobile title, and receive a pinned, reversible setup plan showing every file that would be written, including AGENTS.md and .ai-game-studio/project.json. ## Quick Start Ask the assistant to use the setup-engine skill to inspect this machine and propose a reversible engine setup plan without changing anything yet.
