awesome-gamedev-agent-skills

awesome-gamedev-agent-skills

Make games with your AI coding agent, in the engine you already use. 79 skills for 12 engines: say what you’re building, and a router loads the right 2 or 3 skills before your agent writes code.

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

Agent Skills are small capability files an AI agent loads only when it needs them. This repo gives your agent 79 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, Ebitengine, Phaser, PixiJS, three.js, Bevy, pygame, LÖVE, Defold, Roblox.
• You don’t pick skills. The router detects your engine and task and loads only what fits.
• Art direction, not one-off generations. The asset workflow locks a visual target, builds families, normalizes outputs deterministically, and checks them inside the game.
• Checked on the real engines. Every skill is written from official engine docs and pinned to a current release (Godot 4.7.2, Unity 6.3 LTS, Unreal 5.8, Phaser 4.2.1, three.js r187 and more, checked 2026-11-11). Code examples were run or compiled on the real toolchains for 10 of the 12 engines, and in 366 blind test prompts the right skill loaded for 98.7% of the requests that needed one. Results, method and limits · version support.

Sponsors

Sponsored · Infistar

Open slot · Become a sponsor

Want to reach game developers who build with AI coding agents? Email [email protected]. Sponsor slots are monthly. Sponsored entries are labelled as sponsored and have no effect on which skills the router picks.

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 79 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 CLI needs Node.js 22.20 or later. 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 · ebitengine · web-engines · other-engines

Install tip. If your agent already has many skills, install the router and your engine’s bundle instead of everything. Agents list every skill’s description within a size limit, and past that limit some descriptions are cut, which makes the right skill harder to pick. In Claude Code the limit is 1% of the context window; raise it with the skillListingBudgetFraction setting (for example 0.02) or set a character count with the SLASH_COMMAND_TOOL_CHAR_BUDGET environment variable (Claude Code skills docs).

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

Want to read the catalog as web pages instead? Every skill, engine group, and per-agent install path is browsable at gamedev-skills.github.io/awesome-gamedev-agent-skills, generated straight from the SKILL.md files in this repo.

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 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.

Catalog

79 skills across 9 categories — each links to its SKILL.md below.

Engines

Godot — 16 (skills/godot/) · Godot 4.7

Unity — 9 (skills/unity/) · Unity 6.3 LTS (6000.3)

Unreal — 6 (skills/unreal/) · Unreal Engine 5.8 (5.9 in Preview)

Ebitengine — 1 (skills/ebitengine/) · Ebitengine v2.10.6 · Go 1.25+

Web engines — 6 (skills/web-engines/) · Phaser 4.2 · PixiJS 8.22 · three.js r187

Other engines — 12 (skills/other-engines/) · Bevy · pygame · LÖVE · Defold · Roblox

Disciplines — 15 (skills/disciplines/)

Cross-engine concepts that load alongside the detected engine skill.

Genres — 9 (skills/genres/)

Compositional templates that orchestrate engine + discipline skills; they never re-teach primitives.

Workflows — 5 (skills/workflows/)

Agent compatibility

Every skill here is a plain SKILL.md folder in the Agent Skills open standard — the format Anthropic launched as Claude Skills — metadata plus a Markdown playbook the agent reads on demand.

The same file loads natively across the ecosystem: Claude Code, Claude, Cursor, Windsurf, Cline, OpenAI Codex, Gemini CLI, GitHub Copilot, Kiro, Antigravity, VS Code, and many more. Oh My Pi (omp) reads the same format natively as well. There are no editor-specific rule files to maintain and nothing to convert.

Install with one command. The universal CLI detects your agent and writes the skills to the right place:

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

Or copy by hand. Drop a skill’s <name>/ folder into your agent’s skills directory:

The exact per-agent paths, triggers, and the handful of optional fields that vary by agent are in docs/COMPATIBILITY.md.

Demo

One plain-English request goes in; the minimal right skills come out, then version-pinned code. Here’s the shape of a single exchange (illustrative):

> add a double jump to my player

Detected Godot (project.godot). Loading godot-2d-movement for the controller
and platformer for jump feel — skipping the other 76 skills.

extends CharacterBody2D

@export var speed := 220.0
@export var jump_velocity := -380.0
@export var max_jumps := 2

var _jumps_left := max_jumps

func _physics_process(delta: float) -> void:
    if not is_on_floor():
        velocity += get_gravity() * delta   # Godot 4.7 baseline
    else:
        _jumps_left = max_jumps

    if Input.is_action_just_pressed("ui_accept") and _jumps_left > 0:
        velocity.y = jump_velocity
        _jumps_left -= 1

    velocity.x = Input.get_axis("ui_left", "ui_right") * speed
    move_and_slide()

Repository layout

skills/        79 specialized skills, grouped by engine / discipline / genre / workflow
router/        the master router skill (+ references/)
docs/          authoring standard, installation, compatibility
templates/     SKILL.md template
scripts/       validate-skills.py, generate-site.py and tooling
tests/         regression tests for the validator

Contributing

Contributions are welcome. Read CONTRIBUTING.md and the authoring standard in docs/SKILL-FORMAT.md. Every skill must pass the validator and the rubric before merge:

python scripts/validate-skills.py

Maintainer

awesome-gamedev-agent-skills was created and is maintained by Abhishek Barali.

License

Apache-2.0. See NOTICE for attribution and trademark notes.