Game Development Agent Router

Problem

Game-development requests often cross several engineering surfaces: engine, gameplay, shaders, UI, save systems, multiplayer, input, audio, AI, dialogue, or procedural content. If an agent immediately loads all related material, the context can balloon and the response can drift away from the project’s actual tech stack. This skill does not re-teach engine APIs. It first decides which specialized skills should be loaded, then keeps the follow-up work inside the right boundary.

How It Works

It acts as an entry router for game-development requests. The core loop is classify, read, then compose.
- Detect engine: use the project fingerprint to select at most one engine skill set, or mark it as unknown.
- Classify task: infer the relevant disciplines, at most one genre, and required workflows from the request wording.
- Resolve minimal set: combine engine, discipline, genre, and workflow skills while avoiding unrelated context.
- Disclose on demand: open only the selected SKILL.md bodies, and read references/ only when needed.
- Compose order: proceed as engine fundamentals → discipline concepts → genre glue → workflow to reduce cross-layer confusion.
- Fallback: if the engine is unknown or no skill fits, state the gap or default to Godot.

Boundaries

Use it at the start of requests such as “make a game,” “debug a level, enemy, UI, audio, or save system,” or when the user asks which skill to use. Once the correct skill is loaded and the task has not pivoted, continue working inside that skill instead of re-running the router every turn. Return to the routing layer only when the task moves to a new engine or a new engineering concern.