Route Any Gamedev Request to the Right Skill

Where this fits

You're building a 2D platformer in Godot and ask your agent to "add a double-jump with coyote time." Without a dispatcher, the agent either guesses a generic approach or wastes tokens reading ten unrelated skill files. The router skill solves this by fingerprinting your project (engine, genre, task) and pointing the agent to the exact specialized skill—like game-feel or physics—before it writes a single line of code. It's the front door for any gamedev request, from prototyping to shipping.

Why agents benefit

• Zero-guess dispatch: The router detects the engine (Godot, Unity, Unreal, Bevy, Phaser, PixiJS, three.js, LÖVE, pygame, Roblox) and classifies the task into one of 20+ categories (shaders, AI, audio, multiplayer, etc.), then names the minimal skill set to read.
• Composition over repetition: It doesn't re-teach APIs—it tells the agent which skills to load, so the agent can chain specialized knowledge (e.g., tiles + procedural-generation for a roguelike dungeon) without redundant context.
• Genre-aware routing: Recognizes platformer, roguelike, RPG, FPS, tower-defense, card game, visual novel, survival-crafting, and puzzle—so a "card game" request pulls the right mechanics skill, not a generic tutorial.
• Shipping shortcuts: Includes routing for game jam, Steam, and itch.io publishing, so the agent knows which packaging and storefront skills to invoke.
• Starts with a read-before-act rule: The router instructs the agent to read the chosen skill's README before acting, preventing hallucinated engine APIs and reducing trial-and-error loops.

Practical scenarios

Debugging a Unity shader with a vague error

You paste a shader compile error and ask "fix this." The router detects Unity + shaders, points to the shaders skill, and the agent reads the relevant section on surface shaders before touching your code—no more generic "try changing the syntax" advice.

Prototyping a Bevy roguelike in a game jam

Time is short. You say "build a grid-based roguelike with procedural rooms." The router picks Bevy, classifies genre (roguelike) and task (procedural generation), then loads tiles, procedural-generation, and game-feel skills. The agent composes them into a working vertical slice in minutes.

Switching a Phaser game from single-player to local multiplayer

You ask "add split-screen co-op to my Phaser platformer." The router sees Phaser + multiplayer + platformer, routes to multiplayer and input skills, and the agent implements the correct event handling and camera logic without re-reading the entire Phaser docs.

Add it to your agent workflow

Install the skill with:

npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill router

Then start any gamedev request with a direct prompt like:

Use the router skill. I'm making a Godot FPS with a focus on enemy AI and game feel. What skills should I read first?

The router will return a list like enemies, ai, game-feel, and physics—and your agent will load them before acting.

Compare before adopting

Before committing, evaluate the router against alternatives:

• Quality signals: Check the GitHub repo for recent commits, open issues, and whether the skill descriptions match your engine versions (e.g., Godot 4 vs 3).
• Maintenance freshness: The skill list is only useful if it tracks new engines and tasks—look for updates within the last 6 months.
• Alternatives: Some teams hardcode their own dispatch logic or use a generic "choose a skill" prompt. The router's value is its curated taxonomy—compare its coverage to your actual workflow.
• Workflow fit: If you only use one engine and a narrow task set, a static skill list might suffice. The router shines when you bounce between engines or genres.

Why it is worth tracking

With 800 stars and an active author (gamedev-skills), this router is a strong signal that the agent-skill ecosystem is maturing. It's the kind of meta-skill that reduces token waste and improves output consistency—two things every agent developer cares about. Track it now, and re-evaluate when you expand to new engines or shipping targets. For a broader view of how agent skills fit into your stack, see the OpenAgentSkill directory.