Router
Routes any game-development request to the right specialized skill(s): it detects the...
Install
npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill router -g -a claude-code -y- Repository
- gamedev-skills/awesome-gamedev-agent-skills6.4k
- Category
- Design
- Updated
- 8d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Routes any game-development request to the right specialized skill(s): it detects the engine (Godot, Unity, Unreal, Ebitengine, Bevy, Phaser, PixiJS, three.js, Defold, LÖVE, pygame, Roblox) and the task, then reads the chosen skill before acting. Use to make a game or to decide which skill applies, for players, levels, enemies, shaders, art direction, sprites, tiles, textures, 3D assets, UI/UX, cameras, game feel, physics, input, audio, saving, multiplayer, AI, dialogue, procedural generation, or performance, for genres (platformer, roguelike, RPG, FPS, tower-defense, card game, visual novel, survival-crafting, puzzle), and for shipping (game jam, Steam, itch). Start here when unsure which gamedev skill to use.
Master Router, Game-Development Skill Dispatcher
The entry point for game-development work. It fingerprints the project to pick one engine, classifies the task from the request, names the minimal set of specialized skills, and tells you to read them before acting. It dispatches and composes, it does not re-teach engine APIs.
When to use
- Use at the start of any game-development request, building or debugging a game, level, player, enemy, shader, UI, save system, multiplayer, input, audio, AI, dialogue, procedural content, or visual asset set, to decide which skill(s) to load.
- Use when the user names an engine or genre, says "make a game", or asks "which skill should I use?".
When not to use: once the right skill is loaded and the task is squarely inside it, work from that skill, don't re-run the router every turn. Re-route only when the task pivots to a new engine or concern (router step 6).
Routing algorithm
- Detect engine and version, project fingerprint → at most one engine skill set (or "unknown"), then read the project's version source. §1.
- Classify task, phrasing → discipline(s) + at most one genre + workflow(s). §2.
- Resolve, the minimal set: engine skill(s) + discipline(s) + genre + workflow(s). §3.
- Read (disclosure), open only the chosen
SKILL.mdbodies;references/only on demand. §4. - Compose, order: engine fundamentals → discipline concept → genre glue → workflow. §5.
- Fallback, preserve existing engines, including custom/proprietary ones; bind missing APIs from project evidence and state any gap. For a new project with no engine preference, see §6.
