workflows

awesome-gamedev-agent-skills

Game-development expertise for AI coding agents — install once, and a router loads the right skill for whatever you're building.

Agent Skills are small capability files an AI agent loads only when it needs them. This repo gives your agent 66 game-dev skills and a router that picks the right ones for you. You describe what you're building; the agent loads the matching engine and task skills before it writes code.

• Cross-engine. Godot, Unity, Unreal, Phaser, PixiJS, three.js, Bevy, pygame, LÖVE, Roblox.
• You don't pick skills. The router detects your engine and task and loads only what fits.
• Built to trust. Every skill is written from primary docs, version-pinned to a stated engine release, and checked by a validator.

Contents

• Quick start
• What you can ask
• How the router picks skills
• Catalog
• Agent compatibility
• Contributing

Quick start

One command, any agent. The skills CLI detects the coding agent you already use and installs the router plus all 66 skills into the right place:

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

Add --list to preview first, -g to install for every project, or -a <agent> to target a specific tool (-a cursor, -a claude-code, -a gemini-cli, …). The same SKILL.md files load natively in Claude Code, Cursor, Windsurf, Cline, Codex, Gemini CLI, GitHub Copilot, Kiro, and dozens more — there's nothing to convert.

Claude Code plugin (alternative). This repo is also a Claude Code plugin marketplace, so you can install it with Claude's own commands:

claude plugin marketplace add gamedev-skills/awesome-gamedev-agent-skills
claude plugin install gamedev@awesome-gamedev-agent-skills

Building in only one engine? Install a smaller bundle — router plus your engine:

claude plugin install router@awesome-gamedev-agent-skills
claude plugin install godot@awesome-gamedev-agent-skills    # or: unity · unreal · web-engines · other-engines

Prefer to copy the files by hand, or want the exact per-tool paths? See docs/INSTALLATION.md.

Then just talk to your agent — see below.

What you can ask

Describe the task in plain language. The router figures out the skills:

You say	Skills it loads for you
"add a double jump to my Godot player"	godot-2d-movement + platformer
"make an inventory for my Unity RPG"	unity-scriptableobjects + rpg + save-systems
"procedural dungeon roguelike in Godot"	godot-tilemap + procedural-gen + roguelike
"how should I design save slots?"	save-systems
"publish my game on itch with butler"	itch-publish

You never type the skill names on the right. That's the router's job.

How the router picks skills

You never name a skill. On each request the router does three things:

1. Detects your engine from project files — a project.godot means Godot, a *.uproject means Unreal, and so on. If it can't tell, it just asks.
2. Reads your request for the task — a concept (AI, shaders, saving), a genre (platformer, roguelike), or a shipping step (game jam, Steam).
3. Loads only the matching skills, in order: engine basics first, then the concept, then any genre glue. It re-routes if you switch to something new.

That's why "add a double jump to my Godot player" loads godot-2d-movement + platformer and nothing else.

The exact detection signals and routing table