setup-engine

To pin a game engine version, you need to update CLAUDE.md with the specific engine and version. This skill automates that by using interactive prompts to select an engine, verifying the version via WebSearch, and explicitly writing the pinned version into your project configuration.

The best way to prepare for a game engine upgrade is to run a pre-upgrade audit of your source code. This skill scans your src/ directory for deprecated or changed API usage and presents the findings before any version changes are applied to your configuration files.

Version pinning handles APIs outside the LLM training data by setting a documentation risk level and refreshing the engine reference docs. It uses WebSearch to gather current web sources and populates the docs/engine-reference directory to fill knowledge gaps.

Yes, you can use this to choose between Godot, Unity, and Unreal. It provides a guided interactive decision flow that recommends an engine based on your project concept, target platforms, and personal experience level before pinning the version.

You need to refresh engine reference documentation when you are starting a new project, looking up an engine-only version, or performing a controlled engine upgrade. It ensures your docs/engine-reference directory contains accurate API data for versions beyond the model's knowledge horizon.

You should pin an engine version in CLAUDE.md to prevent engine-version mismatch and ensure reliable downstream development. Using the latest release without pinning risks the AI generating code for deprecated or unfamiliar APIs, causing integration failures.