---
name: setup-engine
description: "Use when you need the /setup-engine or $setup-engine game-production workflow. Configure a game's engine and version, update AGENTS.md and docs/technical-preferences.md, populate version-aware engine reference docs, and set engine specialist routing."
---

# Setup Engine

Run the Codex Game Studios setup-engine workflow.

Before acting, read `DETAILS.md` for the full workflow. Apply project guidance
from the target project's `AGENTS.md`. Use this plugin's bundled baselines from
`../../references/engine-reference/` and template files from
`../../project-template/`.

If the current project does not already have bundled agents installed in
`.codex/agents/` or does not have a root `AGENTS.md`, run the runtime installer
from the plugin root first:

```bash
python3 scripts/install_codex_runtime.py <target-project>
```

`$setup-engine` supports:

- `$setup-engine`
- `$setup-engine godot|unity|unreal`
- `$setup-engine <engine> <version>`
- `$setup-engine refresh`
- `$setup-engine upgrade [old-version] [new-version]`

`$setup-engine` is a technical utility workflow. It has no director gates and
does not invoke director agents.

Never guess the engine version. If the user does not provide a version, verify
the latest stable version from official sources and ask the user to confirm.

Before important writes, show a concise summary and wait for approval. Important
writes include root `AGENTS.md`, `docs/technical-preferences.md`, and
`docs/engine-reference/<engine>/...`.

`$setup-engine` does not spawn or edit engine specialist agents directly. It
writes specialist routing into `docs/technical-preferences.md`; later workflows
use that routing to decide when `godot-*`, `unity-*`, or `ue-*` specialists are
appropriate.