Game Assets
glifxyz/glif-mcp-server
Make art and media for a game you are building with Glif: character reference sheets, consistent characters, pixel-art sprite sheets with animation cycles, seamless and PBR textures, 3D models, item…
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…
Install Router
$ npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill router -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gamedev-skills/awesome-gamedev-agent-skills router --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/gamedev-skills/awesome-gamedev-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/router .claude/skills/router && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "router" agent skill from https://github.com/gamedev-skills/awesome-gamedev-agent-skills/tree/main/router into .claude/skills/router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "router", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/gamedev-skills/awesome-gamedev-agent-skills/tree/main/routerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill router -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gamedev-skills/awesome-gamedev-agent-skills router --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gamedev-skills/awesome-gamedev-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/router .agents/skills/router && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "router" agent skill from https://github.com/gamedev-skills/awesome-gamedev-agent-skills/tree/main/router into .agents/skills/router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "router", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill router -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gamedev-skills/awesome-gamedev-agent-skills router --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gamedev-skills/awesome-gamedev-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/router .cursor/skills/router && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "router" agent skill from https://github.com/gamedev-skills/awesome-gamedev-agent-skills/tree/main/router into .cursor/skills/router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "router", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/gamedev-skills/awesome-gamedev-agent-skills.git --path router--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill router -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gamedev-skills/awesome-gamedev-agent-skills router --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gamedev-skills/awesome-gamedev-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/router .gemini/skills/router && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "router" agent skill from https://github.com/gamedev-skills/awesome-gamedev-agent-skills/tree/main/router into .gemini/skills/router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "router", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install gamedev-skills/awesome-gamedev-agent-skills routerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill router -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gamedev-skills/awesome-gamedev-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/router .github/skills/router && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "router" agent skill from https://github.com/gamedev-skills/awesome-gamedev-agent-skills/tree/main/router into .github/skills/router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "router", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill router -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gamedev-skills/awesome-gamedev-agent-skills router --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gamedev-skills/awesome-gamedev-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/router .opencode/skills/router && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "router" agent skill from https://github.com/gamedev-skills/awesome-gamedev-agent-skills/tree/main/router into .opencode/skills/router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "router", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
router- GitHub stars
- 1.4k
- Token cost
- ~3.8k tokens
- SKILL.md length
- 1,538 words
- Files
- 4 (incl. references)
- Skills in repo
- 53
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
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…
- Works in 6 steps: Engine detection (project fingerprint) → Task classification (phrasing → category) → Routing table (task → category → skill) → …
- Decide which skill applies — for players
- SKILL.md covers When to use, Routing algorithm, 1. Engine detection (project… and 2. Task classification…, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Router is an agent skill from gamedev-skills/awesome-gamedev-agent-skills. 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, 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…
Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `agents/openai.yaml`, `references/engine-detection.md` and `references/routing-table.md`).
It sits in Game Development, covering Game development. It works with Godot and Three.js. The repository describes itself as: 74 game-dev skills for AI coding agents — Godot, Unity, Unreal, Phaser, PixiJS, three.js, Bevy, pygame, LÖVE, Roblox. Portable SKILL.md Agent Skills (the format Anthropic… The licence is Apache-2.0.
When your agent uses it
- Decide which skill applies — for players
- Procedural generation
- For genres (platformer
- Survival-crafting
Example prompts
- “Use the router skill to route any game-development request to the right specialized skill(s): it detects the engine (Godot, Unity, Unreal, Bevy…”
- “/router”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 0a70cfc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Router loads about 3.8k tokens when it runs, and up to ~8.1k if it reads all its reference files. Until then it costs about 177 tokens; SKILL.md has 1,538 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from gamedev-skills/awesome-gamedev-agent-skills at commit 0a70cfc, republished under its Apache-2.0 licence (© gamedev-skills). 1,538 words, ~3,818 tokens.
Download SKILL.mdSave it as
.claude/skills/router/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- router
- description
- 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, 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 — engine unknown or no skill fits → ask or default to Godot; state any gap. §6.
1. Engine detection (project fingerprint)
Scan for the highest-confidence signal; choose exactly one engine. Stop at the first match.
| # | Engine | Primary signal | Skill set root |
|---|---|---|---|
| 1 | Godot | project.godot | skills/godot/ |
| 2 | Unreal | *.uproject | skills/unreal/ |
| 3 | Unity | Assets/ and ProjectSettings/ProjectVersion.txt | skills/unity/ |
| 4 | Bevy | Cargo.toml with a bevy dependency | skills/other-engines/bevy-ecs/ |
| 5 | Phaser | package.json dep phaser | skills/web-engines/phaser-* |
| 6 | PixiJS | package.json dep pixi.js | skills/web-engines/pixijs-rendering/ |
| 7 | three.js | package.json dep three | skills/web-engines/threejs-* |
| 8 | LÖVE | conf.lua / main.lua calling love.* | skills/other-engines/love2d-core/ |
| 9 | pygame | *.py with import pygame | skills/other-engines/pygame-core/ |
| 10 | Roblox | *.rbxl(x) / *.project.json (Rojo) | skills/other-engines/roblox-* |
For secondary signals, the Godot-C#/Unity/Bevy and multi-web disambiguation rules, monorepos,
and plain-text engine mentions, read references/engine-detection.md.
After identifying the engine, read its version from project metadata or dependency locks before
choosing APIs. Existing projects keep their pinned version unless migration is requested; the
catalog baseline is only for new projects. The exact version sources are in the detection reference
and ../docs/VERSION-SUPPORT.md.
2. Task classification (phrasing → category)
After the engine, read the request for task signals (three additive categories):
- disciplines (cross-engine concepts):
create-game-assets,game-ai,ai-behavior-trees-utility-ai,procedural-gen,dialogue-systems,save-systems,audio-design,shader-programming,physics-tuning,level-design,input-systems,game-feel,camera-systems,game-ui-ux,performance-optimization. Triggered by concept words ("sprite sheet", "art direction", "texture", "pathfinding", "save slots", "fragment shader", "screen shake", "camera follow", "HUD/menu", "optimize/low FPS"). - genres (whole-game templates):
platformer,roguelike,rpg,fps-shooter,tower-defense,card-game,visual-novel,survival-crafting,puzzle. Triggered by genre words ("make a roguelike", "deckbuilder"). - workflows (process/shipping):
game-jam,prototype-fast,steam-publish,itch-publish. Triggered by process words ("publish on Steam", "vertical slice").
File signals sharpen this: *.yarn/*.ink → dialogue-systems/visual-novel; steam_appid.txt
→ steam-publish; *.inputactions → unity-input-system.
3. Routing table (task → category → skill)
3a. Engine skills — read the one matching the detected engine + sub-task
- Godot (
skills/godot/): languagegodot-gdscript/godot-csharp; structuregodot-nodes-scenes,godot-signals-groups; 2Dgodot-2d-movement,godot-tilemap; 3Dgodot-3d-essentials; physicsgodot-physics; UIgodot-ui-control; animationgodot-animation; shadersgodot-shaders; datagodot-resources; audiogodot-audio; netcodegodot-multiplayer; headless CLI testsgodot-gdscript-headless-testing; shipgodot-export. - Unity (
skills/unity/): scriptingunity-csharp-scripting; inputunity-input-system; physicsunity-physics; animationunity-animation; dataunity-scriptableobjects; 2Dunity-tilemap-2d; AI navunity-navmesh; shipunity-build-pipeline. - Unreal (
skills/unreal/): visual scriptingunreal-blueprints; C++ gameplayunreal-cpp-gameplay; inputunreal-enhanced-input; AIunreal-behavior-trees; VFXunreal-niagara; shipunreal-packaging. - Web (
skills/web-engines/):phaser-core,phaser-arcade-physics;pixijs-rendering;threejs-scene-setup,threejs-gltf-loading,threejs-materials-lighting. - Other (
skills/other-engines/):bevy-ecs,pygame-core,love2d-core; Roblox foundationroblox-luau, persistenceroblox-datastores, UIroblox-ui, remotes/securityroblox-networking, character lifecycleroblox-characters, simulation/queriesroblox-physics, and in-Studio operationroblox-studio-workflow.
3b. Disciplines — load with the engine skill (concept ↔ engine API)
Concept (says:) | Discipline skill | Pairs with (engine API) |
|---|---|---|
| art direction, game assets, sprites, tilesets, textures, icons, 3D props | create-game-assets | engine importer/rendering skill; imagegen when available |
| enemy AI, behavior tree, pathfinding, steering | game-ai | unity-navmesh / unreal-behavior-trees / Godot nav |
| BT runtime, blackboard, decorator, selector/sequence, utility AI, response curve, consideration | ai-behavior-trees-utility-ai | game-ai (model choice) / unreal-behavior-trees (engine assets) |
| procedural, noise, seed, dungeon generator | procedural-gen | engine tilemap/grid skill |
| dialogue, Yarn, Ink, conversation tree | dialogue-systems | engine UI skill |
| save/load, slots, persistence | save-systems | roblox-datastores / engine IO |
| adaptive music, mixer, ducking, SFX | audio-design | godot-audio / Unity AudioMixer |
| shader, fragment, dissolve/outline | shader-programming | godot-shaders / engine material |
| jitter, tunneling, fixed timestep | physics-tuning | godot-physics / unity-physics |
| whitebox, blockout, tile layout, pacing | level-design | godot-tilemap / unity-tilemap-2d |
| rebind, gamepad, input buffering | input-systems | unity-input-system / unreal-enhanced-input / Godot InputMap |
| screen shake, hit-stop, juice, squash & stretch, "make it punchy" | game-feel | engine animation/tween + camera-systems (shake) |
| camera follow, deadzone, look-ahead, orbit, first-person | camera-systems | godot-2d-movement / godot-3d-essentials / Cinemachine |
| HUD, menu, UI layout, scaling, safe area, focus nav | game-ui-ux | godot-ui-control / Unity UI (UGUI/UI Toolkit) |
| low FPS, optimize, draw calls, GC spike, pooling, profiler | performance-optimization | engine profiler + physics-tuning |
For Roblox, compose cross-engine concepts with the focused engine skill: HUD/menu requests use
roblox-ui + game-ui-ux (+ input-systems for gameplay bindings); remote exploit or
replication requests use roblox-networking + roblox-luau; respawn/rig requests use
roblox-characters; physical simulation/query requests use roblox-physics (+
physics-tuning for stability); direct place editing also uses roblox-studio-workflow.
3c. Genres — compose engine + disciplines (bind * to the detected engine)
Genre (says:) | composes |
|---|---|
| platformer, jump, double jump | godot-2d-movement (or engine physics) + godot-tilemap/unity-tilemap-2d + level-design + camera-systems + game-feel |
| roguelike, procedural dungeon, permadeath | procedural-gen + godot-tilemap/unity-tilemap-2d + game-ai + save-systems + game-feel |
| RPG, stats, inventory, quests | godot-resources/unity-scriptableobjects + dialogue-systems + save-systems + game-ui-ux |
| FPS, first-person, hitscan | godot-3d-essentials/unreal-cpp-gameplay + input-systems + game-ai + camera-systems + game-feel |
| tower defense, waves, lanes | game-ai + engine movement + level-design + game-ui-ux |
| card game, deckbuilder, TCG | godot-resources/unity-scriptableobjects + game-ui-ux (+ engine UI) |
| visual novel, branching story | dialogue-systems + save-systems + game-ui-ux |
| survival, crafting, gathering | save-systems + godot-resources/unity-scriptableobjects + procedural-gen + game-ui-ux |
| puzzle, match-3, grid logic | godot-tilemap/unity-tilemap-2d + level-design + game-feel |
Show full SKILL.md (622 more words)Show less
3d. Workflows — engine-independent process & shipping
game-jam (jam, 48-hour, Ludum Dare/GMTK) · prototype-fast (vertical slice, MVP, greybox) ·
steam-publish (Steam, Steamworks, depot; steam_appid.txt) · itch-publish (itch.io, butler;
.itch.toml).
For the exhaustive per-skill trigger list and every engine binding, read
references/routing-table.md.
4. Read protocol (progressive disclosure)
- Preloaded: only each skill's
name+descriptionare in context. Decide from those plus the fingerprint — do not pre-read bodies. - On selection: read the body of each chosen
skills/<category>/<name>/SKILL.md— and only those. Never bulk-load a whole category. - On demand: read a skill's bundled
references/files only when the subtask needs that depth (the skill body says when). - Re-route on pivot: if the task changes (movement → saving), select and read the newly relevant skill instead of keeping everything loaded.
Announce what you load and why, e.g.: "Detected Godot (project.godot). Loading
godot-2d-movement for the controller and platformer for jump feel; will open the platformer
skill's feel-tuning.md reference if you want coyote-time/buffering."
5. Composition rules
- One engine set, additive concepts. Exactly one engine skill set; add the disciplines the task needs and usually at most one genre. Workflows attach independently.
- Order: engine fundamentals → discipline concept → genre orchestration → workflow. For asset production, approve the visual target before generating a family, then finish with the engine import settings and an in-context capture.
- Ownership on overlap: the engine skill owns API/syntax; the discipline skill owns the portable concept/algorithm and defers to the engine skill for code; the genre skill owns structure/glue and links out instead of re-teaching a primitive.
- Hand-offs: when a genre's
composesnames a slot like*-2d-movement, bind it to the detected engine. If that engine lacks the exact skill, see §6 andreferences/routing-table.md("Binding gaps").
6. Unknown-engine & no-skill fallback
Engine unknown (no fingerprint, no engine named):
- Check the request for a plain-text engine name ("in Unity", "using Phaser"). If found, adopt it.
- If the task is a pure concept/genre/workflow question, route straight to the engine-agnostic
discipline/genre/workflow skill — no engine needed ("what's a good save format?" →
save-systems). - Only if engine choice actually blocks the answer, ask one targeted question ("Which engine — Godot, Unity, Unreal, or a web/other engine?"). If the user has no preference and one is needed, default to Godot (the most fully covered engine here) and say so.
- Never invent an engine or load an engine skill on a guess.
Engine known but no skill covers the subtask: load the closest engine skill plus the relevant
discipline and state the gap plainly (e.g. "no dedicated Unity 2D-movement skill; using
unity-csharp-scripting + unity-physics"). Never fabricate a skill name.
Conflicting/multiple genres: pick the dominant genre from the phrasing; mention the secondary and offer to load it if the user confirms.
Worked examples
| Request | Detected engine | Skills loaded (in order) |
|---|---|---|
| "add a double jump to my Godot player" | Godot (project.godot) | godot-2d-movement → platformer |
| "make an inventory for my Unity RPG" | Unity (Assets/+ProjectSettings/) | unity-scriptableobjects → rpg → save-systems |
| "procedural dungeon roguelike in Godot" | Godot | godot-tilemap → procedural-gen → roguelike |
"branching dialogue from a .yarn file" | (none required) | dialogue-systems (+ engine UI skill if an engine is detected) |
| "how do I design save slots with migration?" | (none) | save-systems only |
| "publish my game on itch with butler" | (any/none) | itch-publish only |
| "I want to make a game but don't know what to use" | unknown → ask, default Godot | router asks once; then e.g. godot-nodes-scenes |
| "make hits feel punchy in my Godot game" | Godot (project.godot) | game-feel (+ camera-systems for shake) |
| "the camera should follow my player smoothly" | (detected engine) | camera-systems (+ engine movement skill) |
| "my Unity game drops to 30 FPS, optimize it" | Unity (Assets/+ProjectSettings/) | performance-optimization (profile first) → engine skill |
| "make a cohesive pixel-art player and enemy set" | (detected engine) | create-game-assets → relevant engine import/rendering skill |
References
- Full engine fingerprints, secondary signals, and disambiguation:
references/engine-detection.md. - Exhaustive per-skill trigger words, engine bindings, and binding gaps:
references/routing-table.md.
© gamedev-skills, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in router of gamedev-skills/awesome-gamedev-agent-skills.
- SKILL.md
- agents/openai.yaml
- references/engine-detection.md
- references/routing-table.md
Open the folder on GitHubat commit 0a70cfc
Compare with similar skills
Router next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Router this skillgamedev-skills/awesome-gamedev-agent-skills | 1.4k | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Game Assetsglifxyz/glif-mcp-server | 213 | — | ~831 | Automated safety check: Pass | MIT | |
| Engine Selectionsickn33/agentic-awesome-skills | 47k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Game Developmentsickn33/agentic-awesome-skills | 47k | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Godot Gdscript Patterns925236118/AlphaAgent | 103 | 10 repos | ~5k | Automated safety check: Pass | MIT | |
| 2D Map and Scene Generator0x0funky/agent-sprite-forge | 4.4k | — | ~2.9k | Automated safety check: Pass | MIT |
Similar skills
Engine Selection
sickn33/agentic-awesome-skills
Selects game engines and frameworks by platform, genre, and architecture (full canvas shell vs hybrid DOM shell + guest viewport).
Game Development
sickn33/agentic-awesome-skills
Game development orchestrator. An agent skill from sickn33/agentic-awesome-skills.
Godot Gdscript Patterns
925236118/AlphaAgent
Master Godot 4 GDScript patterns including signals, scenes, state machines, and optimization.
2D Map and Scene Generator
0x0funky/agent-sprite-forge
Plans and builds 2D game maps and scenes, from tilemaps and parallax backgrounds to HD-2D plates, with collision checks, a playable HTML preview and Tiled, Godot or LDtk export.
Godot UI Integration
zimo-xiao-zheng/godot-ui-integration
Build or revise Godot UI from an approved design, separated art, or a visual reference when scene structure, gameplay binding, and runtime visual verification all matter.
More from gamedev-skills/awesome-gamedev-agent-skills
All 53 skills in this repoCreate Game Assets
gamedev-skills/awesome-gamedev-agent-skills
Plan, generate, source, normalize, and validate cohesive visual game assets.
Roblox UI
gamedev-skills/awesome-gamedev-agent-skills
Build production Roblox interfaces with ScreenGui/PlayerGui lifecycle, responsive UDim2 layouts, safe insets, reusable editable Instances, cross-device input and selection, restrained motion…
AI Behavior Trees Utility AI
gamedev-skills/awesome-gamedev-agent-skills
Build a production behavior-tree runtime (Blackboard, action/condition leaves, sequence/selector/parallel composites, decorators) and a Utility AI system (response curves — linear, exponential…
Bevy Ecs
gamedev-skills/awesome-gamedev-agent-skills
Structure a Bevy app around its Entity Component System: build the App with plugins, define Component/Resource types, write systems with Query/Res/Commands, filter and order systems, and use the…
Card Game
gamedev-skills/awesome-gamedev-agent-skills
Build a card game: card data, deck/hand/discard zones, draw/shuffle/reshuffle, a turn structure, costs, and effect resolution.
Fps Shooter
gamedev-skills/awesome-gamedev-agent-skills
Build a first-person shooter: move+mouse-look controller, hitscan or projectile shooting, weapons, health, and enemy AI.
Related
Categories
Questions about Router
What does Router 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…. Router is an agent skill from gamedev-skills/awesome-gamedev-agent-skills.js, LÖVE, pygame, Roblox) and the task, then reads the chosen skill before acting.
When should I use Router?
Router fits situations like: decide which skill applies — for players; procedural generation; for genres (platformer; survival-crafting.
How do I install Router in Claude Code?
Run `npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill router -a claude-code`. Or copy the skill folder (router in gamedev-skills/awesome-gamedev-agent-skills) into .claude/skills/router in your project. Claude Code loads it when a task matches its description.
How do I install Router in Codex?
Run `npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill router -a codex`. Or copy the skill folder (router in gamedev-skills/awesome-gamedev-agent-skills) into .agents/skills/router in your project. Codex loads it when a task matches its description.
Can I use Router in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill router -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/router, .gemini/skills/router, .github/skills/router and .opencode/skills/router in your project.
What does Router need to run?
SKILL.md names no scripts, command-line tools or credentials: Router is instructions for the agent only.
Does Router access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Router safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Router use?
Router is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Router use?
About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.3k tokens, read only when the agent opens those files.
What are the alternatives to Router?
Skills that share tags, products or a category with Router: Game Assets (glifxyz/glif-mcp-server, 213 stars), Engine Selection (sickn33/agentic-awesome-skills, 47k stars), Game Development (sickn33/agentic-awesome-skills, 47k stars) and Godot Gdscript Patterns (925236118/AlphaAgent, 103 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Router?
gamedev-skills (a GitHub organization) maintains it in gamedev-skills/awesome-gamedev-agent-skills, which has 1,389 GitHub stars. The repository holds 53 skills in this directory. The repository was last updated on October 9, 2026.
Source: gamedev-skills/awesome-gamedev-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.