74 Game-Dev Skills With a Router That Picks Them for You

Game development spans engine APIs, cross-engine disciplines, genre conventions, and shipping steps — no single skill covers all of it, and picking from a stack of 74 would be its own full-time job. The 3k-star gamedev-skills/awesome-gamedev-agent-skills repository solves the picking: install everything once, and a router skill loads only the ones your current task needs.

Why This Skill Matters

Despite the "awesome-" in the name, this is not a link list — the repo itself ships 74 Agent Skills format skills plus the router, Apache-2.0 licensed and organized across the catalog the README prints: 16 Godot skills pinned to Godot 4.7, 8 Unity skills on Unity 6.3 LTS (6000.3), 6 Unreal skills for UE 5.8, 6 web-engine skills (Phaser 4.2, PixiJS 8.21, three.js r186), and 10 for other engines (Bevy 0.19, pygame-ce 2.5.8, LÖVE 11.5, Roblox) — with 15 cross-engine discipline skills (AI, procedural generation, save systems, shaders, game feel, and more), 9 genre templates (platformer, roguelike, RPG, tower defense, and so on), and 4 workflow skills (game jam, fast prototyping, Steam and itch publishing) layered on top.

Every skill is written from primary docs and version-pinned to a stated engine release, and a validator (scripts/validate-skills.py) checks them — trust infrastructure you rarely get in a prompt pack.

Installation

One command works for any agent — the skills CLI detects which one you use and installs the router plus all 74 skills to the right place:

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

--list previews first, -g installs for every project, and -a <agent> targets a specific tool. Claude Code users have a plugin-marketplace alternative:

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

Building in a single engine? Install a smaller bundle — the router plus just your engine:

claude plugin install router@awesome-gamedev-agent-skills
claude plugin install godot@awesome-gamedev-agent-skills

The README documents the same bundle pattern for unity, unreal, web-engines, and other-engines.

Real Workflow: Add a Feature Without Naming a Skill

Describe the task in plain language — the README's own example table shows what the router does with it:

add a double jump to my Godot player

The router works in three steps on each request. It detects your engine from project files (a project.godot means Godot, a *.uproject means Unreal; if it cannot tell, it asks), reads your request for the task, and loads only the matching skills in order — engine basics first, then the concept, then any genre glue. For the double-jump request it loads godot-2d-movement plus platformer and nothing else, and it re-routes when you switch to something new.

The same pattern covers art production and shipping. Asking to "make a cohesive pixel-art player, enemies, and tiles" routes to create-game-assets plus the detected engine's importer skill; asking to "publish my game on itch with butler" routes to itch-publish. You never type the skill names — that is explicitly the router's job.

Tips

• Engine selection is exclusive (exactly one engine), while disciplines, genres, and workflows are additive on top — that composition rule is documented in the router skill itself.
• The full catalog is browsable as web pages at gamedev-skills.github.io/awesome-gamedev-agent-skills, generated straight from the SKILL.md files.
• Every skill is a plain SKILL.md folder in the Agent Skills open standard, so the same files load natively in Claude Code, Cursor, Windsurf, Cline, Codex, Gemini CLI, GitHub Copilot, Kiro, and more — nothing to convert.
• Per-agent manual-copy paths are documented too: .claude/skills/ for Claude Code, .agents/skills/ shared by Codex, Gemini CLI, GitHub Copilot, and Antigravity, .cursor/skills/ for Cursor, and so on.

When Not to Use This

The version pins are the honest boundary. Skills are written against stated engine releases — Godot 4.7, Unity 6.3 LTS, Unreal 5.8, Bevy 0.19 — so if your project sits on a much older or newer release, check the repo's version-support documentation before trusting a skill's API details. And the router loads exactly one engine per project, so a multi-engine codebase gets one engine's context at a time by design.

See the leaderboard for more skills.