What problem does it solve?
This Skill streamlines selecting, pinning, and documenting a game's engine and version in a repository so teams avoid ambiguous engine configurations, mismatched tooling, and undocumented breaking changes that hinder development and agent reasoning.
Core Features & Use Cases
- Guided engine selection: Interactive flow to recommend Godot, Unity, or Unreal based on project goals, platform targets, team experience, and language preference.
- Version management & pinning: Look up or accept a provided engine version, evaluate LLM knowledge risk, and pin the engine/version in CLAUDE.md and docs/engine-reference.
- Technical preferences & routing: Populate .claude/docs/technical-preferences.md with naming conventions, input/platform defaults, performance/testing prompts, and specialist routing for code/shaders/UI.
- Reference docs, refresh, and upgrade: Create or refresh docs/engine-reference/<engine>/ with migration and breaking-change guidance when versions exceed LLM training data; run audits for upgrades and produce migration notes.
- Use case: Onboarding a new game repo or migrating to a newer engine release while ensuring agents and contributors reference the same pinned engine and documented migration steps.
Quick Start
Run /setup-engine and follow the guided prompts to select an engine, choose or confirm a version, update CLAUDE.md, and create or refresh the engine reference docs.