setup-engine

Configure, pin, and upgrade Godot, Unity, and Unreal engine versions and reference docs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/naxoruto/TE-limonchero-3d --skill setup-engine-naxoruto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-engine
Source: https://github.com/naxoruto/TE-limonchero-3d/tree/main/.claude/skills/setup-engine
Command: npx skills add https://github.com/naxoruto/TE-limonchero-3d --skill setup-engine-naxoruto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pin and manage game engine versions and reference docs for a project by configuring, pinning, and upgrading engine settings.

Core Features & Use Cases

  • Pin engine version in CLAUDE.md and surface engine settings to the project.
  • Detect knowledge gaps and fetch/update engine reference docs via WebSearch.
  • Support upgrades and migrations with guided workflows for in-project consistency.

Quick Start

Invoke /setup-engine with no arguments to start guided engine selection and auto-populate CLAUDE.md and 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 game engine version for my project?

You can pin a game engine version by invoking the guided setup, which configures and locks your engine settings directly in CLAUDE.md to ensure project-wide version consistency and automated engine setup.

How do I fetch reference docs for a game engine version beyond training data?

Fetching reference docs for newer game engine versions is handled automatically via WebSearch, which detects knowledge gaps and updates the in-project reference material to match your pinned engine version.

Does this engine setup workflow support Unity, Godot, and Unreal?

Yes, the engine setup workflow supports Unity, Godot, and Unreal, allowing you to pin versions, manage configurations, and synchronize reference documentation across these game engines.

What is the best way to manage game engine upgrades and migrations?

The best way to manage engine upgrades and migrations is using guided workflows that update your pinned settings in CLAUDE.md and refresh reference docs, maintaining in-project consistency during version transitions.

Why do I need version pinning for game engine documentation?

Version pinning for game engine documentation is needed to prevent API mismatches and ensure reference accuracy, automatically synchronizing your project docs with the exact engine version specified in CLAUDE.md.