# Gamedev Agent Skills: 79 game-dev skills with a router (gamedev-skills/awesome-gamedev-agent-skills) — skill card for AI agents

> AgentGid skill card. Checked on 2026-11-14 against commit c6ca6c4 (version 2.0.0).
> Every fact comes from the pack's own files at that commit. Numbers marked "as reported" are the author's.
> Human page: https://agentgid.com/skills/gamedev-skills/awesome-gamedev-agent-skills/

## Explain it to a non-programmer
Your AI coding assistant learns how to make games in the engine you already use: Godot, Unity, Unreal, Roblox, Phaser, three.js and six more. You say what you want in plain words, a router looks at your project, picks the 2 or 3 matching playbooks and the assistant reads them before it writes code.

## Who it is for
- You make a game with Claude Code, Cursor, Codex, Gemini CLI, Copilot or a similar assistant
- Your game is in Godot, Unity, Unreal, Ebitengine, Bevy, Phaser, PixiJS, three.js, Defold, LÖVE, pygame or Roblox
- You want help with game parts like jump feel, enemy AI, save slots, menus, shaders or level layout
- You want to ship to Steam or itch.io, enter a game jam or test an idea fast
- Not for: You don't use an AI coding assistant
- Not for: You need Unity VFX Graph, React Three Fiber or Steamworks calls in game code: the router names these as gaps

## What it is
- Kind: knowledge, scripts
- License: Apache-2.0
- Repository: https://github.com/gamedev-skills/awesome-gamedev-agent-skills

## What it does
- A router skill finds the engine from project files (project.godot means Godot, *.uproject means Unreal) and asks once if it can't tell
- It reads the request for a concept (AI, saving, shaders), a genre (platformer, roguelike) or a shipping step (jam, Steam)
- It loads only the matching skills, in order: engine basics, then the concept, then genre glue, then workflow
- It reads the project's pinned engine version first and warns when the project is newer than the skill's baseline
- Engine skills own the code; discipline skills (15) teach portable techniques; genre skills (9) compose them; workflow skills (5) cover jams, prototypes, Steam, itch.io and design docs
- When a vendor's own tools (Unity, Roblox Studio MCP, Epic, OpenAI game-studio) are already in the session, it lets them drive the editor and never installs them for you
- Never cuts: The router never invents an engine or a skill name, and keeps a custom or in-house engine instead of switching

## Skills
| Skill | Call | Changes code? | In plain words |
|---|---|---|---|
| router | auto at the start of a game request (Claude Code plugin: /gamedev:router) | no | Finds your engine and task and picks the 2 or 3 skills to read |
| godot-gdscript | auto | yes | GDScript 2.0: typing, exports, await, porting Godot 3 code |
| godot-nodes-scenes | auto | yes | Scene tree, instancing, autoloads, and a checker for broken paths |
| godot-signals-groups | auto | yes | Signals, event buses and groups |
| godot-2d-movement | auto | yes | 2D platformer and top-down movement with a headless landing test |
| godot-tilemap | auto | yes | Tile maps: atlases, terrain autotiling, placing tiles while the game runs |
| godot-physics | auto | yes | Bodies, areas, collision layers, raycasts, Jolt |
| godot-ui-control | auto | yes | Menus and HUD layout: anchors, containers, themes, focus |
| godot-animation | auto | yes | AnimationPlayer, AnimationTree state machines, tweens |
| godot-shaders | auto | yes | Godot shaders with a headless compile check |
| godot-3d-essentials | auto | yes | 3D cameras, lights, environment, materials, GridMap |
| godot-resources | auto | yes | Custom data resources (.tres) and threaded loading |
| godot-audio | auto | yes | Audio players, buses, looping, beat sync |
| godot-multiplayer | auto | yes | Online play with ENet and RPCs, tested with two headless instances |
| godot-export | auto | yes | Export presets, command-line export, web headers |
| godot-csharp | auto | yes | C# in Godot and mixing it with GDScript |
| godot-gdscript-headless-testing | auto | yes | GDScript tests run headless, also in CI |
| unity-csharp-scripting | auto | yes | MonoBehaviour lifecycle, serialization, .meta files, compile checks |
| unity-input-system | auto | yes | Input System actions, maps and control schemes |
| unity-physics | auto | yes | 3D and 2D physics: rigidbodies, collisions, raycasts, joints |
| unity-animation | auto | yes | Animator states, blend trees, root motion, IK |
| unity-scriptableobjects | auto | yes | ScriptableObject config assets and event channels |
| unity-tilemap-2d | auto | yes | Tile Palette, tilemap colliders, Rule Tiles |
| unity-navmesh | auto | yes | NavMesh baking and agents for enemy movement |
| unity-build-pipeline | auto | yes | Build settings, IL2CPP vs Mono, scripted and CI builds |
| unity-build-size | auto | yes | Finds what makes a Unity build too large, per platform |
| unreal-blueprints | auto | yes | Blueprint classes, casts, interfaces, event dispatchers |
| unreal-cpp-gameplay | auto | yes | Unreal C++ gameplay classes and command-line builds |
| unreal-enhanced-input | auto | yes | Input actions, mapping contexts, remappable keys |
| unreal-behavior-trees | auto | yes | Behavior Trees, Blackboards, EQS and StateTree for AI |
| unreal-niagara | auto | yes | Niagara particle effects |
| unreal-packaging | auto | yes | Shipping builds, cooking, reading build logs |
| ebitengine-game | auto | yes | 2D games in Go: starter project, input, pixel art, audio, tests, builds |
| phaser-core | auto | yes | Phaser 4.2 setup, scenes, loading, moving from Phaser 3 |
| phaser-arcade-physics | auto | yes | Phaser Arcade Physics: bodies, gravity, colliders, bullet pools |
| pixijs-rendering | auto | yes | PixiJS 8 for games: assets, sprites, dragging |
| threejs-scene-setup | auto | yes | three.js scene, camera, renderer, resize, controls |
| threejs-gltf-loading | auto | yes | Loading compressed 3D models and blending their animations |
| threejs-materials-lighting | auto | yes | three.js materials, lights, shadows, HDR environments |
| bevy-ecs | auto | yes | Bevy ECS systems, schedules and states, with headless tests |
| pygame-core | auto | yes | pygame-ce game loop, sprites, headless tests |
| love2d-core | auto | yes | LÖVE callbacks, fixed steps, crisp pixel art, saves |
| defold-core | auto | yes | Defold collections, game objects, messages, factories, builds |
| roblox-luau | auto | yes | Roblox Luau services, script types, typed Luau, code checks |
| roblox-datastores | auto | yes | Saving player data safely, session locking, leaderboards |
| roblox-ui | auto | yes | Roblox screens: scaling, layouts, safe areas, gamepad and touch |
| roblox-networking | auto | yes | Remotes, server authority, rate limits, stopping cheats |
| roblox-characters | auto | yes | Character spawn, rigs, respawn and tools |
| roblox-physics | auto | yes | Roblox constraints, collision groups, raycasts, network ownership |
| roblox-studio-workflow | auto | yes | Safe edits to an existing place, proven with a test run or Studio MCP |
| roblox-simulator-economy | auto | yes | Simulator and tycoon economy: costs, income, rebirths, egg odds |
| create-game-assets | auto | yes | Plans and checks a matching set of game art, with a record of where each file came from |
| game-ai | auto | yes | Enemy and NPC AI: state machines, steering, A* pathfinding |
| ai-behavior-trees-utility-ai | auto | yes | Behavior trees and utility AI code in any language |
| procedural-gen | auto | yes | Seeded random levels, dungeons, noise terrain, loot tables |
| dialogue-systems | auto | yes | Branching dialogue with Ink, Yarn Spinner or a data file |
| save-systems | auto | yes | Save slots, autosave, safe writes, upgrading old saves |
| audio-design | auto | yes | Mixing, volume sliders, ducking, adaptive music |
| shader-programming | auto | yes | How effects like dissolve and outline work, GLSL and HLSL |
| physics-tuning | auto | yes | Fixes jitter, objects passing through walls, floaty physics |
| level-design | auto | yes | Player metrics, gating with a soft-lock check, blockouts, pacing |
| input-systems | auto | yes | Named actions, stick deadzones, buffered presses, rebinding |
| game-feel | auto | yes | Screen shake, hit-stop, squash and stretch, knockback |
| game-ui-ux | auto | yes | HUD and menu rules: scaling, safe areas, gamepad focus, accessibility |
| camera-systems | auto | yes | Follow cameras, orbit, first-person look, split-screen |
| performance-optimization | auto | yes | Measure first, then fix the biggest cause of low frame rate |
| platformer | auto | yes | Jump feel numbers, wall jumps, checkpoints, and a jump calculator |
| roguelike | auto | yes | Runs, permadeath, meta-progression, daily seeds, field of view |
| rpg | auto | yes | Stats, XP curves, damage formulas, items, quests |
| fps-shooter | auto | yes | Hitscan vs projectiles, recoil, time-to-kill |
| tower-defense | auto | yes | Paths, wave pacing, targeting, gold economy, a wave-curve checker |
| card-game | auto | yes | Cards as data, deck zones, shuffles, deckbuilders |
| visual-novel | auto | yes | Routes, endings, save anywhere, backlog, typewriter text |
| survival-crafting | auto | yes | Gathering, recipes, carry weight, spoilage, base building |
| puzzle | auto | yes | Match-3, Sokoban, undo, levels checked by a solver |
| game-jam | auto | yes | Plans a game jam entry against the clock and gets it submitted |
| prototype-fast | auto | yes | Builds a throwaway test of one idea and helps you decide to keep, kill or retune it |
| steam-publish | auto | yes | Writes and checks the Steam upload scripts and walks you through store review |
| itch-publish | auto | yes | Uploads builds to itch.io with butler, one channel per platform |
| game-docs | auto, only when you ask for design docs or a GDD already exists | no | Writes or updates a one-page game design document and short feature notes |

### router
- Asks for: Your request in plain words
- Asks for: Your project folder (it reads project.godot, *.uproject, package.json and similar)
- Gives: One line naming the engine it found and the skills it loads, and why
- Gives: A note when your engine version is newer than the skills' baseline
- Gives: A plain statement of any gap no skill covers
- Say: "Add a double jump to my Godot player"

### create-game-assets
- Asks for: Your engine, view and target size
- Asks for: Existing art or a style you want kept
- Asks for: Whether an image tool is available, or licensed packs to use
- Gives: An art direction brief
- Gives: An asset manifest listing every sprite, size, source and licence
- Gives: A size, transparency and colour report per file
- Gives: A contact sheet to look at
- Say: "Make a cohesive pixel-art player, enemies and tiles for my game"

### game-jam
- Asks for: The jam page URL or its rules
- Asks for: Jam length and theme
- Asks for: Your engine
- Gives: JAM.md with rules, deadline in UTC and your time, and a cut list
- Gives: A one-sentence concept
- Gives: A scope budget and hour-by-hour timeline
- Gives: Build checks before you submit
- Say: "I'm entering a 48-hour jam, help me scope it"

### prototype-fast
- Asks for: The one question the prototype must answer
- Asks for: A timebox
- Gives: prototypes/<idea>/BRIEF.md with keep and kill signals
- Gives: A greybox build with a debug readout of the values being judged
- Gives: A keep, kill or retune call written into the brief
- Say: "Prototype this: is a grappling hook fun in my game?"

### steam-publish
- Asks for: Your App ID and depot IDs (you get them in Steamworks)
- Asks for: A separate build account you created
- Gives: app_build and depot_build scripts
- Gives: A script check with check_steam_build.py
- Gives: A preview run that uploads nothing, then an upload to a beta branch first
- Say: "Set up SteamPipe uploads for my game"

### itch-publish
- Asks for: The itch.io page URL (you create the page)
- Asks for: Your build folders
- Asks for: A version number
- Gives: A dry-run file list before any upload
- Gives: butler push commands per platform channel
- Gives: A list of page settings for you to fix, including the AI generation disclosure
- Say: "Publish my game on itch with butler"

### game-docs
- Asks for: Your game idea or planning chat
- Asks for: At most one short round of answers
- Gives: GDD.md of about one page
- Gives: design.md notes for the 2 or 3 core-loop features, with starting numbers marked as assumptions
- Gives: A docs check with check_docs.py
- Say: "Draft a GDD for my game"

## Know before installing
- It switches on by itself: the router says to use it at the start of any game-development request.
- Installing all 79 skills can push other skills out of your assistant's list; the author suggests the router plus your engine's bundle.
- Some skills ship small Python check scripts the assistant runs on your files; one needs the Pillow library installed with pip.
- Image generation usually costs money per image; the art skill tells the assistant to state the batch size and ask you first.
- Account steps stay with you: Steam and itch.io logins, passwords and fees are for you to do, and the skills say never to commit login tokens.
- Existing projects keep their engine version; the pinned baselines are only for new projects.

## Install (official commands)
- Any agent (skills CLI): `npx skills add gamedev-skills/awesome-gamedev-agent-skills` — Installs the router and all 79 skills. Add --list to preview, -a <agent> for one agent, -g for every project, --skill <name> for a subset. Needs Node.js 22.20 or later. Remove: `npx skills remove`.
- Claude Code (plugin): `claude plugin marketplace add gamedev-skills/awesome-gamedev-agent-skills` && `claude plugin install gamedev@awesome-gamedev-agent-skills` — Or a smaller set: router@awesome-gamedev-agent-skills plus godot, unity, unreal, ebitengine, web-engines or other-engines, and disciplines, genres, workflows.
- Claude Code (manual copy): `mkdir -p .claude/skills` && `cp -R skills/godot/godot-tilemap .claude/skills/` && `cp -R router .claude/skills/router` — Copy each skill folder you want, and always the router. ~/.claude/skills/ makes them global. Remove: `delete the folders from .claude/skills/`.
- Codex, Gemini CLI, GitHub Copilot, Antigravity, Cursor, Windsurf, Cline, Kiro, Oh My Pi: Copy a skill's folder into the agent's skills folder: .agents/skills/, .cursor/skills/, .devin/skills/, .cline/skills/, .kiro/skills/ or .omp/skills/.

## What runs on the user's machine
- Code on the machine: yes (check scripts inside some skills, run by the assistant when a skill's checks call for them)
- Network: none
- Install: Markdown skills plus a plugin manifest. No hooks, nothing runs at install or session start.
- Asset checks (create-game-assets): asset_report.py and build_preview_sheet.py read your images and write a contact sheet PNG where you point them. Need Pillow.
- Project checks: Read-only checkers for Godot, Unity, Defold, Ebitengine, Steam build scripts, Unity build size and design docs; they read files and print a report.
- Ebitengine starter: new_game.py copies the bundled starter into a new or empty folder and writes go.mod; it does not run go or touch the network. package_macos_app.py builds a .app and calls lipo.
- Tuning helpers: jump_tuner.py (platformer) and td_curve_check.py (tower defense) compute numbers locally.
- Commands the skills suggest: Some skills tell the assistant to run third-party tools that download packages: npx @gltf-transform/cli, npx playwright install chromium, pip install pygame-ce, butler, steamcmd. These are suggestions in the text, not code in the pack.

## Examples (from the pack's own files)
- The router's announcement (README demo, marked illustrative): output format defined in README.md
- A prototype brief: output format defined in skills/workflows/prototype-fast/SKILL.md

## Author's numbers (as reported, not run by AgentGid)
- In 366 blind test prompts the right skill loaded for 98.7% of the requests that needed one (Model judges (Claude Opus 5.5 and Haiku 5.5) saw only skill names and descriptions; one run per cell). Source: gamedev-skills/awesome-gamedev-agent-skills/README.md
- Code examples were run or compiled on the real toolchains for 10 of the 12 engines. Source: gamedev-skills/awesome-gamedev-agent-skills/README.md
- Not run: the Unity Editor, Unreal Editor, Roblox Studio and .NET builds of Godot C#. Source: gamedev-skills/awesome-gamedev-agent-skills/evals/RESULTS.md

## Steps only the person can do
- Create the Steamworks partner account, pay the Steam Direct fee, make a separate build account and report the App ID and depot IDs (https://partner.steamgames.com/) Then: The assistant writes and checks the build scripts and runs a preview upload
- Create the itch.io page and run butler login yourself (https://itch.io/game/new) Then: The assistant runs the dry run and the butler push commands
- For Roblox Studio MCP work, open a place in Studio and enable the MCP server (https://create.roblox.com/docs/studio/mcp) Then: The assistant edits and tests the place through Studio MCP tools

## Mistakes to avoid
- Not: Install all 79 skills on top of many other skills. Instead: Install the router plus your engine's bundle, or raise the skill listing budget. Why: Agents cut skill descriptions past a size limit, which makes the right skill harder to pick
- Not: Copy the skill folders but leave out the router. Instead: Copy router/ alongside the skills. Why: The router is itself a skill and does the routing
- Not: Load a genre skill such as platformer on its own. Instead: Load it with the engine's movement skill. Why: The genre skill has tuning numbers but no engine code
- Not: Upgrade an existing project to the skills' engine baseline without being asked. Instead: Keep the project's pinned version and check APIs against it. Why: The baseline is only for new projects

## Lines in the pack aimed at agents (ask the person first)
- "It needs `npm i -D playwright` and `npx playwright install chromium`" (skills/web-engines/phaser-core/SKILL.md): Installs a browser and a dev dependency; the same line says to ask the user if they don't want that. Ask first.
- "npx @gltf-transform/cli optimize in.glb out.glb" (skills/web-engines/threejs-gltf-loading/SKILL.md): Unpinned npx downloads a package at run time; ask before running, and note it overwrites model files when input and output are the same.
- "Install the only dependency with `python -m pip install -r scripts/requirements.txt` when it is not already available." (skills/disciplines/create-game-assets/SKILL.md): Installs Pillow into the user's Python; ask first or use a virtual environment.

## May I use it like this?
- commercial-app: yes (Apache-2.0: keep the license and NOTICE)
- redistribute-files: conditions (Apache-2.0: include the license and the NOTICE file, mark changed files)
- client-work: yes (Apache-2.0 allows use for others)
- inside-app-bundle: conditions (Starter code from ebitengine-game bundles Go Fonts under their own license file)

## Which one to pick
- If You want separate game-dev skills with a router for many engines in your existing setup: skill:gamedev-skills/awesome-gamedev-agent-skills
- If You want a whole Claude Code project folder with role agents, phases and gate checks for making one game: skill:Donchitos/Claude-Code-Game-Studios
- If You work only in Unreal Engine and want a Claude Code plugin of Unreal skills: skill:EpicGames/unreal-engine-skills-for-claude-code-plugin

## Works well with
- agent:claude-code: The repo is a Claude Code plugin marketplace with per-engine plugins
- asset:kenney: CC0 game art packs to source licensed assets the art skill records
- mcp:com-roblox-studio-mcp: roblox-studio-workflow edits and tests a place through Studio MCP when it is connected
- tool:phaser: The phaser-core and phaser-arcade-physics skills target Phaser 4.2

## Works in and needs
- Works in Claude Code: plugin or skills folder
- Works in Codex, Gemini CLI, GitHub Copilot, Antigravity: skills folder (.agents/skills/)
- Works in Cursor: skills folder (.cursor/skills/)
- Works in Windsurf: skills folder (.devin/skills/)
- Works in Cline: skills folder (.cline/skills/)
- Works in Kiro: skills folder (.kiro/skills/)
- Works in Any agent with a skills folder: skills CLI
- Needs Node.js 22.20 or later: Only for the skills CLI install
- Needs Python 3 with Pillow: The create-game-assets check scripts
- Needs Steam partner account, steamcmd, butler: Only for the steam-publish and itch-publish workflows

## How to tell it works
In a game project, ask "add a double jump to my player". The assistant should first say which engine it detected and which two skills it is loading, then write code for that engine version. That line is how you know the router is on.

## Safety
Install from github.com/gamedev-skills/awesome-gamedev-agent-skills. The skills are instructions your assistant follows; the publishing skills leave logins, passwords and fees to you. The README carries a sponsored affiliate link, which the author says does not affect which skills the router picks.
