setup-engine

Pin a game engine and version in repository metadata and reference docs.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/emcconnell/nova-scout --skill setup-engine-emcconnell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-engine
Source: https://github.com/emcconnell/nova-scout/tree/main/.claude/skills/setup-engine
Command: npx skills add https://github.com/emcconnell/nova-scout --skill setup-engine-emcconnell

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about setup-engine

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I pin a specific Unity or Godot version in my game project repository?

To pin a specific engine version, you configure repository metadata and update CLAUDE.md with the selected engine and version. This ensures all contributors and agents reference the exact configuration.

What is the best way to document game engine migration steps for breaking changes?

Documenting engine migration steps involves creating reference docs in docs/engine-reference detailing breaking changes and migration guidance. This is particularly necessary when upgrading to engine versions beyond the LLM training cutoff.

Can I get a recommendation on whether to use Godot, Unity, or Unreal for my new game?

Yes, guided engine selection recommends Godot, Unity, or Unreal by interactively evaluating your project goals, platform targets, team experience, and language preferences to determine the best fit.

How do I update technical preferences and agent routing for a game engine project?

You update technical preferences and agent routing by populating .claude/docs/technical-preferences.md with naming conventions, input defaults, and specialist routing for code, shaders, and UI components.

Does engine setup support looking up Unreal Engine versions released after the LLM training cutoff?

Yes, engine setup supports looking up newer versions by performing WebSearch and WebFetch to retrieve current release information when a requested engine version exceeds the LLM knowledge cutoff.