Skip to content
Back to search

game-creator

SkillGitHubIncomplete

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/playableintelligence/game-creator 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/playableintelligence/game-creator'

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/playableintelligence--game-creator/badge.svg)](/listings/playableintelligence--game-creator)

HTML

<a href="/listings/playableintelligence--game-creator"><img src="/api/listings/playableintelligence--game-creator/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

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

npx skills add playableintelligence/game-creator

Target a specific agent:

npx skills add playableintelligence/game-creator -a claude-code
npx skills add playableintelligence/game-creator -a codex
npx skills add playableintelligence/game-creator -a cursor

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 · 46 lines

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

  1. {
  2. "name": "game-creator",
  3. "owner": {
  4. "name": "OpusGameLabs"
  5. },
  6. "metadata": {
  7. "description": "The game studio for the agent internet. Build, monetize, and ship browser games. Phaser 2D, Three.js 3D, Play.fun monetization. Works with 40+ AI coding agents.",
  8. "version": "1.3.0"
  9. },
  10. "plugins": [
  11. {
  12. "name": "game-creator",
  13. "source": "./",
  14. "description": "The game studio for the agent internet. Build, monetize, and ship 2D and 3D browser games with one command. Play.fun + Moltbook.",
  15. "version": "1.3.0",
  16. "author": {
  17. "name": "OpusGameLabs"
  18. },
  19. "homepage": "https://opusgamelabs.github.io/game-creator",
  20. "repository": "https://github.com/OpusGameLabs/game-creator",
  21. "license": "MIT",
  22. "keywords": [
  23. "games",
  24. "gamedev",
  25. "threejs",
  26. "phaser",
  27. "3d",
  28. "2d",
  29. "browser-games",
  30. "openclaw",
  31. "moltbook",
  32. "agent-internet",
  33. "playfun",
  34. "play-fun",
  35. "opengameprotocol",
  36. "monetization",
  37. "game-design",
  38. "game-audio",
  39. "strudel",
  40. "chrome-devtools-protocol",
  41. "qa"
  42. ],
  43. "category": "development"
  44. }
  45. ]
  46. }
README.md · README · 221 lines

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

  1. # game-creator
  2. **Go from game idea to deployed, monetized browser game in minutes — not hours.**
  3. Tell your AI coding agent "make a space invaders game" and get a fully playable 2D or 3D browser game with pixel art, procedural audio, and automated QA. Deploy instantly to the web. Monetize with [Play.fun](https://play.fun).
  4. Works with **40+ AI coding agents** — Claude Code, Codex, Cursor, and more via `npx skills add`.
  5. ## Install
  6. ```bash
  7. npx skills add playableintelligence/game-creator
  8. ```
  9. Target a specific agent:
  10. ```bash
  11. npx skills add playableintelligence/game-creator -a claude-code
  12. npx skills add playableintelligence/game-creator -a codex
  13. npx skills add playableintelligence/game-creator -a cursor
  14. ```
  15. ## Quick Start
  16. ```bash
  17. # Build a complete 2D game in one shot (scaffold → pixel art → design → audio → deploy → monetize)
  18. # QA subagent runs after every step (build, runtime, gameplay, architecture, visual)
  19. /game-creator:viral-game 2d my-game
  20. # Build from a tweet
  21. /game-creator:viral-game https://x.com/user/status/123456
  22. # Or design a real game project with milestones, ADRs, and multi-session iteration:
  23. /game-creator:make-game
  24. # Or run individual steps on an existing game:
  25. /game-creator:add-assets # Replace shapes with pixel art sprites
  26. /game-creator:design-game # Add visual polish (particles, juice, transitions)
  27. /game-creator:add-audio # Add chiptune music and sound effects
  28. /game-creator:add-feature jetpack # Add a gameplay feature
  29. /game-creator:improve-game # Audit + implement highest-impact improvements
  30. /game-creator:monetize-game # Register on Play.fun, add SDK, get monetized URL
  31. /game-creator:review-game # Code review for architecture + best practices
  32. /game-creator:qa-game # Add browser QA tests
  33. ```
  34. ## How It Works
  35. `/viral-game` is an orchestrator that delegates all code writing to subagents and runs a QA subagent after every code-modifying step. (For the deeper, multi-session `/make-game` workflow with phases, milestones, ADRs, and `docs/STATE.md`, see `skills/make-game/`.)
  36. ```
  37. Step 0 Parse args, create task list ← main thread
  38. Step 1 Scaffold game from template ← code subagent → QA subagent
  39. Step 1.5 Add pixel art sprites (2D only) ← code subagent → QA subagent
  40. Step 2 Visual polish (particles, juice, transitions) ← code subagent → QA subagent
  41. Step 3 Audio (Strudel.cc BGM + SFX) ← code subagent → QA subagent
  42. Step 4 Deploy to here.now ← main thread (instant publish)
  43. Step 5 Monetize with Play.fun ← main thread (interactive auth)
  44. ```
  45. The QA subagent runs 5 phases per step: build check, runtime check (headless Chromium), gameplay verification (iterate client with game-specific actions), architecture validation, and visual review (screenshots captured over the Chrome DevTools protocol). If any phase fails, an autofix subagent patches the code and QA re-runs (up to 3 attempts per step).
  46. ## Architecture
  47. Every game follows the same architecture, whether 2D or 3D:
  48. ```
  49. src/
  50. ├── core/
  51. │ ├── EventBus.js # Singleton pub/sub — all cross-module communication
  52. │ ├── GameState.js # Centralized state with reset() for clean restarts
  53. │ ├── Constants.js # Every magic number, color, timing, speed
  54. │ └── GameConfig.js # Engine config (Phaser or Three.js)
  55. ├── scenes/ # Scene lifecycle (Phaser) or states (Three.js)
  56. ├── entities/ # Game objects (player, enemies, obstacles)
  57. ├── systems/ # Background, particles, spawners
  58. ├── sprites/ # Pixel art data (palette, matrices, tiles)
  59. ├── audio/ # Strudel.cc procedural audio
  60. │ ├── AudioManager.js # Init, play, stop wrapper
  61. │ ├── AudioBridge.js # Wires EventBus → AudioManager
  62. │ ├── music.js # Background music patterns
  63. │ └── sfx.js # Sound effect patterns
  64. ├── playfun.js # Play.fun SDK integration
  65. └── main.js # Entry point + render_game_to_text() + advanceTime()
  66. ```
  67. **EventBus** — Modules never import each other. All communication via pub/sub with `domain:action` event names.
  68. **GameState** — Single source of truth. `reset()` gives a clean slate for restarts.
  69. **Constants** — Zero hardcoded values in game logic. Sizes are proportional (`GAME.WIDTH * ratio`), with DPR-aware scaling for retina displays.
  70. **`render_game_to_text()`** — Every game exposes `window.render_game_to_text()` returning a JSON string of current game state, so AI agents can read the game without interpreting pixels.
  71. ## Skills
  72. ### Reference Skills (loaded automatically by Claude when relevant)
  73. | Skill | Purpose |
  74. |-------|---------|
  75. | `phaser` | 2D game patterns — Phaser 3 scenes, arcade physics, high-DPI rendering |
  76. | `threejs-game` | 3D game patterns — Three.js event-driven architecture, modular systems |
  77. | `game-assets` | Pixel art sprites — `renderPixelArt()`, `renderSpriteSheet()`, palette system |
  78. | `game-designer` | Visual polish — gradients, particles, screen shake, transitions, juice |
  79. | `game-audio` | Procedural audio — Strudel.cc BGM patterns + Web Audio SFX |
  80. | `game-qa` | Browser testing (Chrome over CDP, no npm dependency) — gameplay, visual regression, performance |
  81. | `game-architecture` | Reference architecture patterns for event-driven games |
  82. | `game-deploy` | Deployment — here.now (default), GitHub Pages, Vercel, Netlify, itch.io |
  83. | `playdotfun` | Play.fun (OpenGameProtocol) — SDK, API, auth, leaderboards |
  84. | `unity-mcp` | Unity Editor automation via MCP (CoplayDev/unity-mcp, beta) |
  85. | `fetch-tweet` | Fetch tweet content for tweet-to-game conversion |
  86. ### Slash Commands (user-invocable)
  87. | Command | Description |
  88. |---------|-------------|
  89. | `/viral-game [2d\|3d] [name] OR [tweet-url]` | One-shot pipeline (~10 min): scaffold, pixel art, design, audio, promo video, deploy to here.now, monetize on Play.fun |
  90. | `/make-game` | Multi-session game-dev workflow: idea → scaffold → development phases with milestones, ADRs, and `docs/STATE.md` |
  91. | `/improve-game [focus]` | Deep audit + implement highest-impact improvements |
  92. | `/design-game [path]` | Audit and improve visual polish |
  93. | `/add-feature [description]` | Add a gameplay feature following architecture patterns |
  94. | `/add-assets [path]` | Replace geometric shapes with pixel art sprites |
  95. | `/retrodiffusion [prompt]` | Generate true pixel art sprites/tilesets/animations via Retro Diffusion API (paid) |
  96. | `/add-audio [path]` | Add Strudel.cc music and sound effects |
  97. | `/monetize-game [path]` | Register on Play.fun, add SDK, get monetized URL |
  98. | `/qa-game [path]` | Add browser QA tests |
  99. | `/review-game [path]` | Code review for architecture + best practices |
  100. All commands are prefixed with `game-creator:` when installed as a plugin (e.g., `/game-creator:viral-game`).
  101. ## Agents
  102. | Agent | Description | Preloaded Skills |
  103. |-------|-------------|------------------|
  104. | `game-creator` | Autonomous end-to-end pipeline with build/visual gates (no user confirmation between steps) | — (delegates to subagents) |
  105. | `game-reviewer` | Reviews codebases for architecture compliance, performance, and monetization readiness | `game-architecture` |
  106. | `game-qa-runner` | Runs browser test suites, diagnoses failures, fixes code, and re-runs until green | `game-qa`, `game-architecture` |
  107. | `game-deploy` | Deploys games to here.now (default), GitHub Pages, Vercel, or itch.io with pre/post validation | `game-deploy` |
  108. ## Examples
  109. 8 complete example games in `examples/`, demonstrating both engines:
  110. | Game | Engine | Description |
  111. |------|--------|-------------|
  112. | `flappy-bird` | Phaser 3 | Classic flappy clone — 5 scenes, 15 browser tests, full audio |
  113. | `barn-defense` | Phaser 3 | Tower defense game |
  114. | `vampire-survivors` | Phaser 3 | Survivors-like auto-attacking game |
  115. | `example-game` | Phaser 3 | Asteroid dodger (generated by `/viral-game` test run) |
  116. | `flappy-bird-3d` | Three.js | 3D flappy bird variant |
  117. | `flight-simulator` | Three.js | Flight sim with terrain |
  118. | `labyrinth` | Three.js | 3D maze game |
  119. | `singularity-run` | Three.js | Endless runner with matrix rain effects |
  120. ```bash
  121. cd examples/flappy-bird
  122. npm install
  123. npm run dev # http://localhost:3000
  124. npm run test # Browser tests (node --test)
  125. npm run build # Production build to dist/
  126. ```
  127. ## Templates
  128. `/viral-game` copies a runnable starter project from `templates/` — not generated from scratch. Both templates include all dependencies, the full EventBus/GameState/Constants architecture, QA scripts, and procedural graphics (no asset files).
  129. | Template | Engine | Includes |
  130. |----------|--------|----------|
  131. | `phaser-2d` | Phaser 3 | Boot/Game/GameOver scenes, Player entity, ScoreSystem, arcade physics, high-DPI support |
  132. | `threejs-3d` | Three.js | Game orchestrator, Player mesh, LevelBuilder, HTML overlays, InputSystem (touch + keyboard) |
  133. Both templates ship with `scripts/verify-runtime.mjs` (headless runtime check), `scripts/iterate-client.js` (action replay + screenshots), `scripts/validate-architecture.mjs` (pattern validator), and `scripts/example-actions.json` (default test actions).
  134. ## Tech Stack
  135. | Layer | Technology |
  136. |-------|-----------|
  137. | 2D Engine | Phaser 3 (`^3.90.0`) |
  138. | 3D Engine | Three.js (`^0.183.0`) |
  139. | Audio | Strudel.cc (`@strudel/web ^1.3.0`) — AGPL-3.0 |
  140. | Build | Vite (`^7.3.1`) |
  141. | Testing | `node --test` + `scripts/browser-test.mjs` / `scripts/cdp.mjs` (system Google Chrome over the DevTools protocol, no npm dependency) |
  142. | Monetization | [Play.fun](https://play.fun) (OpenGameProtocol) |
  143. | Language | JavaScript ES modules |
  144. ## Quality Assurance
  145. QA is built into every code-modifying step of the pipeline via a dedicated QA subagent:
  146. 1. **Build** — `npm run build` catches compilation errors
  147. 2. **Runtime** — Headless Chromium checks for WebGL errors, uncaught exceptions, console errors
  148. 3. **Gameplay** — Iterate client replays game-specific actions, verifies scoring works and death triggers
  149. 4. **Architecture** — Validates EventBus/GameState/Constants patterns, flags magic numbers
  150. 5. **Visual** — Screenshots (iterate client, read back by the agent) check entity visibility, safe zone compliance, button labels
  151. If any phase fails, an autofix subagent patches the code and QA re-runs (up to 3 attempts). Problems are caught when introduced, not at the end of the pipeline.
  152. ## Play.fun Integration
  153. The `/monetize-game` command (and Step 5 of `/viral-game`) registers games on [Play.fun](https://play.fun) and integrates the browser SDK:
  154. 1. Authenticate via web callback or manual paste
  155. 2. Register game with anti-cheat limits based on scoring system
  156. 3. Add CDN script + `src/playfun.js` (wires EventBus to `addPoints()`/`savePoints()`)
  157. 4. Rebuild and redeploy
  158. The SDK is non-blocking — if it fails to load, the game still works. Points buffer locally during gameplay and sync on game over.
  159. ## License
  160. MIT (games using `@strudel/web` for audio must use an AGPL-3.0-compatible license)
  161. ## Star History
  162. <a href="https://www.star-history.com/?repos=playableintelligence%2Fgame-creator&type=date&legend=top-left">
  163. <picture>
  164. <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/chart?repos=playableintelligence/game-creator&type=date&theme=dark&legend=top-left" />
  165. <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/chart?repos=playableintelligence/game-creator&type=date&legend=top-left" />
  166. <img alt="Star History Chart" src="https://api.star-history.com/chart?repos=playableintelligence/game-creator&type=date&legend=top-left" />
  167. </picture>
  168. </a>

Ratings and comments

Sign in to rate this skill.

Sign in

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