game-dev
Skill26 starsChanged yesterdayMITView on GitHub
Entry point for game development work: routes a task to the right game-dev skill and states the project conventions. Use when starting or continuing work on a game project, or when it is unclear which game-dev skill applies.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- notque/vexjoy-agenttheir own version, first seen Nov 10, 2026
- TheArchitectit/awesome-cline-skillstheir own version, first seen Oct 13, 2026
- notque/claude-code-toolkittheir own version, first seen Oct 8, 2026
- grounded-play/hunker-bunkertheir own version, first seen Sep 25, 2026
- BigY0shi/super-skillstheir own version, first seen May 7, 2026
- acatovic/gothicvania-codex-demotheir own version, first seen Feb 16, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- notque/vexjoy-agent★ 450same name
- notque/claude-code-toolkit★ 448same name
- acatovic/gothicvania-codex-demo★ 25same name
- TheArchitectit/awesome-cline-skills★ 8same name
- BigY0shi/super-skills★ 4same name
- grounded-play/hunker-bunker★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository46 other files it gives its agents.
- asaasSkill
- betterauth-integrationSkill
- bullmq-game-queuesSkill
- character-design-narrativeSkill
- ci-cd-gameSkill
- claude-agent-sdkSkill
- database-performance-tuningSkill
- elevenlabs-sound-musicSkill
- foundry-vtt-devSkill
- game-anti-cheatSkill
- game-backend-architectureSkill
- game-blenderSkill
- game-clientSkill
- game-design-fundamentalsSkill
- game-architectSkill
- game-balanceSkill
- game-buildSkill
- game-expandSkill
- game-loreSkill
- game-questSkill
- game-reviewSkill
- game-economy-designSkill
- game-godotSkill
- game-localizationSkill
- gameplay-analyticsSkill
- game-save-loadSkill
- game-state-syncSkill
- game-unitySkill
- judgeSkill
- level-designSkill
- matchmaking-systemSkill
- mmo-designSkill
- monitoring-game-opsSkill
- nuvemshop-sdkSkill
- openclaw-genieSkill
- postgres-game-schemaSkill
- procedural-genSkill
- quest-mission-designSkill
- quest-narrative-coherenceSkill
- react-animationsSkill
- redis-game-patternsSkill
- skill-progression-treesSkill
- story-structure-gameSkill
- stripe-game-paymentsSkill
- ui-ux-gameSkill
- worldbuildingSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 91
Run all game logic on the server and treat the client as display only.
- Very specific: line 93
Read postgres-game-schema before writing database code.
- Distinctive: line 94
Keep shared code free of genre-specific mechanics.
- Distinctive: line 98
If a skill in the table is not installed, run:
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Game Dev
Find the task in the table, then load the skill named beside it. Commands run a whole workflow; start with them when one fits.
Route
Design
| Need | Skill |
| Design loop, core loop, difficulty, rewards | game-design-fundamentals |
| Currencies, sinks and faucets, loot, crafting, shops | game-economy-design |
| Translation: string IDs, plurals, text expansion, pseudo-localization | game-localization |
| Level layout, pacing, encounter placement, difficulty curve | level-design |
| Persistent world with many players: shards, economy at scale, alts, roles, guilds, endgame, live ops | mmo-design |
| Dungeons, maps, terrain, seeds | procedural-gen |
| Quests, missions, objectives, rewards | quest-mission-design |
| HUD, menus, onboarding, accessibility | ui-ux-game |
Art and assets
| Need | Skill |
| Sound effects, music, voice | elevenlabs-sound-music |
| 3D models from Blender: headless export, glTF and FBX, LODs, collision, baking | game-blender |
Engineering
| Need | Skill |
| Login, sessions, roles, WebSocket auth | betterauth-integration |
| Queues, delayed jobs, scheduled work | bullmq-game-queues |
| Cheating: input validation, hidden state, dupes, detection, bans | game-anti-cheat |
| Game server, WebSocket, rooms, tick loop | game-backend-architecture |
| Browser client: stack choice (web, Phaser, PixiJS, Three.js), loop, input, assets | game-client |
| Godot 4: GDScript or C#, headless export, WebSocket client to our server | game-godot |
| Saves, slots, save versions and migration, cloud sync conflicts | game-save-load |
| Lag, desync, jitter; prediction, reconciliation, interpolation | game-state-sync |
| Unity: Unity CLI and batch mode, API traps, WebSocket client to our server | game-unity |
| Player events, retention, funnels | gameplay-analytics |
| Pairing players, lobbies, ranks | matchmaking-system |
| Tables, player data, inventory, Drizzle | postgres-game-schema |
| Leaderboards, presence, rate limits, cache-aside | redis-game-patterns |
| Skill trees, talent trees, unlock graphs | skill-progression-trees |
| Payments, purchases, subscriptions, webhooks | stripe-game-payments |
Narrative
| Need | Skill |
| Characters, NPCs, dialogue, arcs | character-design-narrative |
| Check new content against existing lore and quests | quest-narrative-coherence |
| Branching story, acts, player agency | story-structure-game |
| World, factions, geography, timeline | worldbuilding |
Infrastructure
| Need | Skill |
| Pipelines, deploys, migrations, a database per pull request | ci-cd-game |
| Logging, alerts, server health, tick time, error rates | monitoring-game-ops |
Workflows
| Need | Skill |
| Start a project: interview, research, MVP plan | /game-architect (game-architect) |
| Check economy, difficulty or progression balance | /game-balance (game-balance) |
| Build one component from the plan | /game-build (game-build) |
| Add a post-MVP feature to the plan | /game-expand (game-expand) |
| Add a faction, location, NPC or event to the lore | /game-lore (game-lore) |
| Design one quest end to end | /game-quest (game-quest) |
| Audit code against the design rules | /game-review (game-review) |
Installed as the Claude Code plugin, the commands are /game-dev:<name>, for example /game-dev:game-build.
Project files
docs/mvp-first-draft.md: the MVP plan, created bygame-architect, then extended bygame-expand.docs/build-registry.md: components built so far, created and kept bygame-build.docs/world-lore.md: canonical world state, created bygame-architect, then kept bygame-lore.docs/quest-registry.md: every quest, created bygame-architect(or bygame-questwhen missing), then kept bygame-quest.
Rules
- Run all game logic on the server and treat the client as display only. A client the player controls can be edited.
- Apply
quest-narrative-coherencebefore writing a quest, character or lore entry. New content then cannot contradict what exists. - Read
postgres-game-schemabefore writing database code. Queries written without the schema drift from it. - Keep shared code free of genre-specific mechanics. Genre-specific logic in shared code breaks the next game that reuses it.
Missing skill
If a skill in the table is not installed, run:
bunx skills add fcsouza/agent-skills --skill <name>New project
Paste templates/game-project-claude.md into the game repo as its CLAUDE.md and fill in the placeholders.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

