router
Routes any game-development request to the right specialized skill(s): it detects the engine (Godot, Unity, Unreal, Bevy, Phaser, PixiJS, three.js, 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, 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). S
npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill router --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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, or procedural content — 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 1. **Detect engine** — project fingerprint → at most one engine skill set (or "unknown"). §1. 2. **Classify task** — phrasing → discipline(s) + at most one genre + workflow(s). §2. 3. **Resolve** — the minimal set: engine skill(s) + discipline(s) + genr
- When to use
- Routing algorithm
- 1. Engine detection (project fingerprint)
- 2. Task classification (phrasing → category)
- 3. Routing table (task → category → skill)
- 3a. Engine skills — read the one matching the detected engine + sub-task
- 3b. Disciplines — load with the engine skill (concept ↔ engine API)
- 3c. Genres — compose engine + disciplines (bind to the detected engine)
- 3d. Workflows — engine-independent process & shipping
- 4. Read protocol (progressive disclosure)
- 5. Composition rules
- 6. Unknown-engine & no-skill fallback
- Worked examples
- References
What does the router skill do?
Routes any game-development request to the right specialized skill(s): it detects the engine (Godot, Unity, Unreal, Bevy, Phaser, PixiJS, three.js, 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, 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). S
How do I install it?
Run `npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill router --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From gamedev-skills/awesome-gamedev-agent-skills, a repository with 406 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.