Skip to content
Back to search

everything-game-dev-code

MarketplaceWorks with Claude CodeGitHub

A universal scaffold for AI-assisted game development. 42 agents, 51 commands, 86 skills. Multi-engine (Unity, Unreal, Godot, HTML). Multi-harness (Claude Code, Codex, Cursor, OpenCode, Kiro).

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

Its scripts were only partly scanned.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/MRCalderon3D/everything-game-dev-code with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/MRCalderon3D/everything-game-dev-code'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/mrcalderon3d--everything-game-dev-code/badge.svg)](/listings/mrcalderon3d--everything-game-dev-code)

HTML

<a href="/listings/mrcalderon3d--everything-game-dev-code"><img src="/api/listings/mrcalderon3d--everything-game-dev-code/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

git clone https://github.com/MRCalderon3D/everything-game-dev-code.git
cd everything-game-dev-code
npm run setup:hooks

`npm run setup:hooks` wires the repo's pre-commit checks (structure sync + validation) so committed artifacts never drift; it needs Node.js 18+ and takes one second. Run `npm run doctor` at any time to diagnose your installation (environment, hooks, active engine profile, generated-artifact drift) with remediation hints.

Open the folder in your AI coding assistant (Claude Code, Cursor, Codex, OpenCode, Kiro, Grok Build, or Kilo). The scaffold is loaded from the assistant's adapter plus the shared `AGENTS.md`, `rules/`, `commands/`, `agents/`, and `skills/` layers.

Then type commands in the chat:

| Command | What it does | |---------|-------------| | `/plan` | Outline your project before coding | | `/gdd` | Generate a Game Design Document | | `/tdd` | Apply test-driven development to the current task | | `/scene-bootstrap` | Scaffold a new scene | | `/unity-setup` | Bootstrap a Unity project with conventions | | `/unity-build-fix` | Diagnose and fix Unity build errors | | `/godot-setup` | Bootstrap a Godot project | | `/unreal-setup` | Bootstrap an Unreal project | | `/web-setup` | Bootstrap a web (HTML5) project, 2D canvas or 3D WebGL | | `/generate-assets` | Generate real assets — images, skyboxes, 3D models, SFX, music, voice, video — from text prompts | | `/full-game` | Orchestrate an entire game from scratch (experimental) |

You don't have to follow a specific order. Pick whatever command fits your current need — start a new project, generate a GDD for an existing one, run a QA review, or fix a build error.

Step-by-step guide

The `guides/Dash & Collect/` folder contains a full tutorial that walks through building a game using the scaffold's commands, agents, skills, and contexts across all project phases.

Example projects

The `samples/` folder contains thirteen complete HTML games built with the `/full-game` command in a single pass each (PirateInvaders, Tetris2DMutation, LosRenacidos, pacmanAI, harness-comparison variants, PrismDefense3D — the first 3D sample, built on Three.js against the web 3D rules, plus its CC0-textured Visuals variant and its AssetsGen variant where every model, texture, skybox, sound, and the intro cinematic were generated through the `/generate-assets` layer, and NebulaLance — a 2.5D R-Type-style shoot-'em-up whose ship, enemies, boss, nebula, audio, and image-to-video menu cinematic are all AI-generated), plus a writeup comparing how different AI harnesses performed on the same brief. For real projects, we recommend going step by step.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 47 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "everything-game-dev-code",
  3. "slug": "everything-game-dev-code",
  4. "display_name": "Everything Game Dev Code",
  5. "summary": "A universal game development scaffold for Claude Code with layered rules, agents, skills, commands, hooks, contexts, and isolated engine packs for Unity, Unreal, and Godot.",
  6. "source": {
  7. "source": "github",
  8. "repo": "your-org/everything-game-dev-code",
  9. "branch": "main"
  10. },
  11. "categories": [
  12. "game-development",
  13. "ai-development-workflows",
  14. "unity",
  15. "unreal",
  16. "godot"
  17. ],
  18. "files": {
  19. "plugin": ".claude-plugin/plugin.json",
  20. "root_memory": "CLAUDE.md",
  21. "global_agents": "AGENTS.md"
  22. },
  23. "install": {
  24. "recommended_profile": "preproduction-only",
  25. "available_profiles": [
  26. "preproduction-only",
  27. "unity-mobile-f2p",
  28. "unreal-console-aaa",
  29. "godot-indie-2d",
  30. "unity-multiplayer"
  31. ]
  32. },
  33. "engines": [
  34. "unity",
  35. "unreal",
  36. "godot"
  37. ],
  38. "capabilities": [
  39. "planning",
  40. "game-design-documentation",
  41. "technical-design",
  42. "testing-and-qa",
  43. "performance-budgeting",
  44. "release-readiness",
  45. "liveops"
  46. ]
  47. }
README.md · README · 183 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <div align="center">
  2. # Everything Game Dev Code
  3. ### A universal scaffold for AI-assisted game development.
  4. ### Multi-engine. Multi-harness. One coordinated workflow.
  5. <br>
  6. ![license](https://img.shields.io/badge/license-MIT-blue)
  7. ![agents](https://img.shields.io/badge/agents-43-blueviolet)
  8. ![commands](https://img.shields.io/badge/commands-67-orange)
  9. ![skills](https://img.shields.io/badge/skills-109-brightgreen)
  10. ![rules](https://img.shields.io/badge/rules-115-yellow)
  11. ![contexts](https://img.shields.io/badge/contexts-9-cyan)
  12. ![harnesses](https://img.shields.io/badge/harnesses-5-red)
  13. ![engines](https://img.shields.io/badge/engines-Unity%20%7C%20Unreal%20%7C%20Godot%20%7C%20HTML-8A2BE2)
  14. **Unity** · **Unreal Engine** · **Godot** · **HTML/JS** — 2D and 3D, strict engine isolation, shared standards.
  15. </div>
  16. ---
  17. Not just a prompt collection — a structured operating system for game projects that combines:
  18. - **Rules** for policy and standards
  19. - **Agents** for role specialization
  20. - **Commands** for repeatable entry points
  21. - **Skills** for reusable execution patterns
  22. - **Contexts** for phase-specific behavior
  23. - **Hooks** for workflow automation
  24. - **Harness adapters** for Claude, Codex, Cursor, OpenCode, Kiro, Grok Build, and Kilo (see [docs/harness-support.md](docs/harness-support.md) for what each one supports)
  25. ## Quickstart
  26. ```bash
  27. git clone https://github.com/MRCalderon3D/everything-game-dev-code.git
  28. cd everything-game-dev-code
  29. npm run setup:hooks
  30. ```
  31. `npm run setup:hooks` wires the repo's pre-commit checks (structure sync + validation) so committed artifacts never drift; it needs Node.js 18+ and takes one second. Run `npm run doctor` at any time to diagnose your installation (environment, hooks, active engine profile, generated-artifact drift) with remediation hints.
  32. Open the folder in your AI coding assistant (Claude Code, Cursor, Codex, OpenCode, Kiro, Grok Build, or Kilo). The scaffold is loaded from the assistant's adapter plus the shared `AGENTS.md`, `rules/`, `commands/`, `agents/`, and `skills/` layers.
  33. Then type commands in the chat:
  34. | Command | What it does |
  35. |---------|-------------|
  36. | `/plan` | Outline your project before coding |
  37. | `/gdd` | Generate a Game Design Document |
  38. | `/tdd` | Apply test-driven development to the current task |
  39. | `/scene-bootstrap` | Scaffold a new scene |
  40. | `/unity-setup` | Bootstrap a Unity project with conventions |
  41. | `/unity-build-fix` | Diagnose and fix Unity build errors |
  42. | `/godot-setup` | Bootstrap a Godot project |
  43. | `/unreal-setup` | Bootstrap an Unreal project |
  44. | `/web-setup` | Bootstrap a web (HTML5) project, 2D canvas or 3D WebGL |
  45. | `/generate-assets` | Generate real assets — images, skyboxes, 3D models, SFX, music, voice, video — from text prompts |
  46. | `/full-game` | Orchestrate an entire game from scratch (experimental) |
  47. You don't have to follow a specific order. Pick whatever command fits your current need — start a new project, generate a GDD for an existing one, run a QA review, or fix a build error.
  48. ### Step-by-step guide
  49. The `guides/Dash & Collect/` folder contains a full tutorial that walks through building a game using the scaffold's commands, agents, skills, and contexts across all project phases.
  50. ### Example projects
  51. The `samples/` folder contains thirteen complete HTML games built with the `/full-game` command in a single pass each (PirateInvaders, Tetris2DMutation, LosRenacidos, pacmanAI, harness-comparison variants, PrismDefense3D — the first 3D sample, built on Three.js against the web 3D rules, plus its CC0-textured Visuals variant and its AssetsGen variant where every model, texture, skybox, sound, and the intro cinematic were generated through the `/generate-assets` layer, and NebulaLance — a 2.5D R-Type-style shoot-'em-up whose ship, enemies, boss, nebula, audio, and image-to-video menu cinematic are all AI-generated), plus a writeup comparing how different AI harnesses performed on the same brief. For real projects, we recommend going step by step.
  52. ## Goals
  53. - Keep shared game-development standards engine-neutral.
  54. - Let Unity, Unreal, Godot, and the web layer each extend the base cleanly without contaminating one another.
  55. - Support real production work across design, engineering, content, QA, release, and live ops.
  56. - Turn repeated solutions into reusable skills and structured workflows.
  57. - Make the repository portable across multiple coding assistants and harnesses.
  58. ## Repository Model
  59. This scaffold is organized in layers:
  60. - `rules/` — what good looks like
  61. - `agents/` — who does the work
  62. - `commands/` — how work starts
  63. - `skills/` — how work is executed well
  64. - `contexts/` — how priorities shift by phase
  65. - `hooks/` — how workflow safeguards are enforced
  66. - `manifests/` — how subsets are installed by profile, plus the engine layer registry (`engines.json`), the harness adapter registry (`harnesses.json`), and the generative asset provider registry (`asset-providers.json`)
  67. - `schemas/` — JSON validation for manifests, hooks, and plugins
  68. - `scripts/` — generators, validators, and diagnostics (`new:engine`, `doctor`, `sync:*`)
  69. - `docs/templates/` — structured templates for GDD, TDD, QA plans, and other deliverables
  70. - `docs/orchestration/` — agent routing, role handoffs, and workflow sequences
  71. - `tests/` — how the scaffold verifies itself
  72. - harness adapters — how different AI clients consume the same source of truth
  73. ## Engine Isolation Policy
  74. The repository is intentionally split into:
  75. - `rules/common/`
  76. - `rules/unity/`
  77. - `rules/unreal/`
  78. - `rules/godot/`
  79. - `rules/web/`
  80. And equivalent skill / command / review layers where needed.
  81. Shared documents should describe **intent**, **ownership**, and **quality bars**. Engine-specific files should describe **implementation conventions** inside that engine only.
  82. ## AI Asset Generation (optional)
  83. The scaffold ships an **optional** engine-neutral asset generation layer. It is an
  84. upgrade, not a dependency: the default asset workflow is unchanged, and AI generation
  85. only activates when a provider API key is present in the environment.
  86. **Without a key (default).** Use the scaffold's built-in tooling exactly as always:
  87. the engine placeholder commands (`/unity-placeholders`, `/godot-placeholders`,
  88. `/web-placeholders`) and the procedural / Canvas / WebAudio pipelines. A game built
  89. entirely on placeholders is a complete, valid result — nothing about the workflow
  90. requires an API.
  91. **With a key (`FAL_KEY` for the default fal.ai provider).** `/generate-assets` becomes
  92. available to upgrade placeholders to real content from text prompts:
  93. 1. Generate placeholders first so every asset has a stable name and path.
  94. 2. Run `/generate-assets` to produce images and textures, equirectangular skyboxes, 3D models (GLB/OBJ), sound effects, music, voice lines, and intro/cinematic video — dropped onto those same names and paths (zero code changes).
  95. 3. Import through the active engine layer and review with the matching pass command (`/art-2d-pass`, `/art-3d-pass`, `/audio-pass`).
  96. **Resolution order, quality, and cost.** For images and skyboxes the scaffold prefers a
  97. free harness-native generator (e.g. Codex `$imagegen`) when the running harness has one,
  98. then the paid API, then placeholders; 3D/audio/video only have the API or placeholder
  99. paths. Quality vs price is the user's dial: every capability has `budget` / `balanced` /
  100. `premium` tiers (`--quality`, default `balanced`) — a full asset pass runs roughly
  101. $2-3 / $5-7 / $10+ respectively. Because the API costs money, generation also asks before
  102. spending: every run prints a cost estimate, and `scripts/generate-assets.js` refuses runs
  103. at or above a configurable threshold (`confirmOverUsd`) without explicit confirmation.
  104. Autonomous flows like `/full-game` keep placeholders as the default and ask once — tier
  105. and spend — before generating.
  106. Capability-to-model routing lives in [manifests/asset-providers.json](manifests/asset-providers.json) (default provider: fal.ai — one pay-per-use key covers every modality). `scripts/generate-assets.js` performs the generation and writes a `.provenance.json` sidecar (provider, model, prompt, seed, request id) per run; assets without provenance are treated as unlicensed content. The key is read only from the `FAL_KEY` environment variable and is never committed (`.env` files are gitignored). Governance rules — the optional-capability, resolution-order, and cost-confirmation policy — live in [rules/common/asset-pipeline.md](rules/common/asset-pipeline.md). For a worked end-to-end example see the `samples/PrismDefense3DAssetsGen` variant.
  107. ## Intended Use Cases
  108. - New game project setup
  109. - Multi-engine studio workflows
  110. - Internal AI workflow standardization
  111. - GDD and technical design maintenance
  112. - QA and release readiness reviews
  113. - Plugin / content / tooling governance
  114. - Cross-discipline planning and orchestration
  115. ## Supported Harnesses
  116. - Claude Code
  117. - Codex
  118. - Cursor
  119. - OpenCode
  120. - Kiro
  121. - Grok Build
  122. - Kilo
  123. Each harness adapter points back to the same shared scaffold rather than becoming a second source of truth.
  124. ### MCP servers
  125. The scaffold curates a set of MCP servers (browser playtesting, AI asset generation, Blender/DCC control, and more) in [mcp-configs/mcp-servers.json](mcp-configs/mcp-servers.json), with ready-to-use, harness-native configs generated into [mcp-configs/generated/](mcp-configs/generated/). MCP is vendor-neutral, so they work with any MCP-capable client. See [docs/mcp-setup.md](docs/mcp-setup.md) for per-harness install and a Blender end-to-end walkthrough.
  126. ### Codex usage
  127. Codex should start from `AGENTS.md` and `.codex/README.md`. Slash-style commands such as `/plan`, `/gdd`, and `/unity-review` map to `commands/<name>.md`; if the Codex client does not execute slash commands natively, type the command name in chat and ask Codex to run the matching scaffold command.
  128. For raster-first asset work in Codex, use `$imagegen` alongside the shared art pipeline skills. Good fits include concept sheets, sprite source art, UI mockups, marketing key art, painted backgrounds, and bitmap edits; keep vector/code-native asset work in the normal repo workflows. If a generated image becomes a real project asset, move the selected file from `$CODEX_HOME/generated_images/...` into the workspace and keep the scaffold's naming and folder conventions.
  129. ## Current Status
  130. The scaffold is intentionally modular. Different blocks may be added or replaced over time, but the repository should always preserve:
  131. - flat agent and command structures
  132. - layered rules
  133. - grouped skills
  134. - engine isolation
  135. - harness portability
  136. ## Principles
  137. - Design before implementation
  138. - Explicit ownership over implicit assumptions
  139. - Testability over cleverness
  140. - Documentation that supports execution
  141. - Measured performance and release readiness
  142. - Accessibility, QA, and compliance as first-class requirements
  143. ## License
  144. This repository is provided under the MIT License unless you replace it with your studio’s internal licensing policy.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.