setup-engine

Configure and pin game engine versions in CLAUDE.md for Claude Code projects.

277|65|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/pixel-cellar/Claude-Code-Game-Studios --skill setup-engine-pixel-cellar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-engine
Source: https://github.com/pixel-cellar/Claude-Code-Game-Studios/tree/main/.claude/skills/setup-engine
Command: npx skills add https://github.com/pixel-cellar/Claude-Code-Game-Studios --skill setup-engine-pixel-cellar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the configuration and locking of game engine versions for Claude Code projects, preventing drift between development and production references and ensuring consistent toolchains.

Core Features & Use Cases

  • Engine locking: Lock the engine and version in CLAUDE.md to prevent accidental upgrades that could break builds.
  • Knowledge-gap detection: Detect when a requested version lies outside the model's training data and trigger WebSearch to supplement engine references.
  • Documentation synchronization: Update CLAUDE.md and generate engine reference documents to keep the tech stack current for the team.
  • Guided selection: Provide interactive prompts for engine and version selection when no arguments are supplied.

Quick Start

Run /setup-engine unity to begin guided selection and lock the engine version for your project.

Frequently Asked Questions about setup-engine

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

FAQPage Schema
How do I lock a game engine version in CLAUDE.md to prevent build drift?

Locking a game engine version in CLAUDE.md involves configuring and pinning the specific engine version for your Claude Code project. This prevents accidental upgrades and ensures consistent builds across development and production environments.

What is knowledge-gap detection when setting up engine versions?

Knowledge-gap detection identifies when a requested engine version lies outside the model's training data. It triggers a WebSearch to supplement engine references, ensuring the project maintains up-to-date technical documentation for newer releases.

How do I configure engine selection for a Claude Code project without specifying parameters?

Configuring engine selection without parameters triggers guided interactive prompts for engine and version selection. This interactive workflow helps you choose the correct game engine and lock the version without needing command-line arguments.

Does the setup engine workflow support automated documentation synchronization?

The setup engine workflow supports automated documentation synchronization by updating CLAUDE.md and generating engine reference documents. This keeps the tech stack current for the entire team after version discovery and locking.

Why does engine version locking matter for deterministic builds?

Engine version locking matters for deterministic builds because it prevents drift between development and production references. By pinning the game engine version, you ensure the toolchain remains consistent and avoid unexpected breaking changes.