What it does. 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.
- 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?".
Highlights
- Use at the start of any game-development request — building or debugging a game, level,
- Use when the user names an engine or genre, says "make a game", or asks "which skill should I
- disciplines (cross-engine concepts):
create-game-assets
, game-ai
, ai-behavior-trees-utility-ai
, procedural-gen
, dialogue-systems
,
- genres (whole-game templates):
platformer
, roguelike
, rpg
, fps-shooter
,
- workflows (process/shipping):
game-jam
, prototype-fast
, steam-publish
,
When to use it. Routes any game-development request to the right specialist among 67 portable skills covering Godot, Unity, Unreal, Phaser, three.js, Bevy and LOVE.
Install
npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill router
Or copy the skill folder manually:
git clone https://github.com/gamedev-skills/awesome-gamedev-agent-skills.git
cp -r awesome-gamedev-agent-skills/router/ ~/.claude/skills/router
Source: gamedev-skills/awesome-gamedev-agent-skills — 802 stars, Apache-2.0, last pushed 2026-08-24.