playableintelligence/game-creator

review-game

Review an existing game codebase for architecture, performance, and best practices.

Zobacz źródło

Jak używać

  1. Skopiuj polecenie instalacji i sprawdź źródła przed instalacją we własnym środowisku agenta.
  2. W oryginale sprawdź wymagane narzędzia, dane dostępowe i obsługiwane środowiska.
  3. Opisz dane wejściowe i oczekiwany rezultat; porównaj wynik ze źródłami.
npx skills add https://github.com/playableintelligence/game-creator --skill review-game

Przed rozpoczęciem

  • Instalacja nie obejmuje subskrypcji modelu, limitu API ani uprawnień do plików.
  • Gwiazdki i instalacje pokazują aktywność, a nie niezależny test jakości lub bezpieczeństwa.
Oryginalny dokument Skill

Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.

Performance Notes

  • Take your time to do this thoroughly
  • Quality is more important than speed
  • Do not skip validation steps

Review Game

Analyze an existing game codebase and provide a structured review. This is the final step in the pipeline — it checks everything is wired up correctly and gives you a quality score.

Instructions

Analyze the game at $ARGUMENTS (or the current directory if no path given).

Step 1: Identify the game

  • Detect the engine (Three.js, Phaser, or other)
  • Read package.json for dependencies and scripts
  • Read the main entry point and index.html
  • Identify the game concept/genre

Step 2: Architecture Review

Check for these required patterns and report compliance:

  • [ ] EventBus: Is there a centralized event system? Are modules decoupled?
  • [ ] GameState: Is there a centralized state singleton?
  • [ ] Constants: Are config values centralized or scattered as magic numbers?
  • [ ] Orchestrator: Is there a main Game class that initializes everything?
  • [ ] Directory Structure: Is code organized into core/systems/gameplay/ui/level layers?
  • [ ] Event Constants: Are events defined as named constants or raw strings?

Step 3: Performance Review

Check for common issues:

  • [ ] Delta time capping: Is getDelta() capped to prevent death spirals?
  • [ ] Object pooling: Are temp objects reused in hot loops?
  • [ ] Resource disposal: Are Three.js geometries/materials/textures disposed?
  • [ ] Event cleanup: Are event listeners cleaned up on scene transitions?
  • [ ] Asset loading: Are assets preloaded with progress feedback?

Step 4: Code Quality

  • [ ] No circular dependencies: Modules flow one direction
  • [ ] Single responsibility: Each module has one clear job
  • [ ] Error handling: Event handlers wrapped in try/catch
  • [ ] Consistent naming: Events use domain:action, files use PascalCase

Step 5: Monetization Readiness

  • [ ] Points system: Is there a scoring/points mechanism?
  • [ ] Session tracking: Can game sessions be identified?
  • [ ] Anti-cheat potential: Is score validation server-side or at least structured for it?
  • [ ] Play.fun integration: Any existing SDK integration?

Output Format

Provide a structured report with:

  1. Game Overview - What the game is, tech stack, game loop
  2. Architecture Score (out of 6 checks)
  3. Performance Score (out of 5 checks)
  4. Code Quality Score (out of 4 checks)
  5. Monetization Readiness (out of 4 checks)
  6. Top Recommendations - Prioritized list of improvements with plain-English explanations
  7. What's Working Well - Positive findings

Example Usage

/review-game examples/flappy-bird

Result: Architecture 6/6, Performance 4/5, Code Quality 4/4, Monetization 2/4 → Top recommendations: add Play.fun SDK, add object pooling for pipes, add delta time capping. Positive findings: clean EventBus usage, proper GameState reset, well-organized directory structure.

Next Step

Tell the user:

Your game has been through the full pipeline! Here's what you have: - Scaffolded architecture (/viral-game) - Visual polish (/design-game) - Music and sound effects (/add-audio) - Automated tests (/qa-game) - Architecture review (/review-game) (Reflects the `/viral-game` one-shot pipeline. If you're working through `/make-game`, the equivalent state is "post-scaffold-phase + first development milestone shipped".) What's next? - Add new gameplay features with /game-creator:add-feature [description] - Deploy to the web — run npm run build && ~/.agents/skills/here-now/scripts/publish.sh dist/ for instant hosting, or use GitHub Pages, Vercel, Netlify, itch.io - Keep iterating! Run /design-game, /add-audio, or /review-game again anytime after making changes.
z tego samego repozytorium

Więcej Skills

Wszystkie Skills
playableintelligence
Społeczność

game-assets

Game asset engineer that creates pixel art sprites, animated characters, and visual entities for browser games. Use when a game needs better character art, enemy sprites, item visuals, or any upgrade from basic geometric shapes to recognizable pixel art.

Instalacje / 1h
1
GitHub Stars
362
Aktualizacja
4 lis
playableintelligence
Społeczność

add-multiplayer

Add real-time or turn-based multiplayer to an existing browser game using PartyKit (Cloudflare Durable Objects). Scaffolds a room-based server, a NetworkManager client, EventBus events, GameState fields, Constants, and extends rendergametotext(). Use when the user says "add multiplayer", "make this multiplayer", "add real-time co-op", "add online play", "scaffold multiplayer", or "add netcode". Do NOT use for solo leaderboards (use monetize-game), single-player AI opponents (use add-feature), or

Instalacje / 1h
1
GitHub Stars
360
Aktualizacja
4 lis
playableintelligence
Społeczność

game-deploy

Deploy browser games to here.now (default), GitHub Pages, or other hosting. Use when deploying a game, setting up hosting, or publishing a game build. Do NOT use for local development servers (use npm run dev).

Instalacje / 1h
1
GitHub Stars
360
Aktualizacja
4 lis
playableintelligence
Społeczność

phaser

Build 2D browser games with Phaser 3 using scene-based architecture and centralized state. Use when creating a new 2D game, adding 2D game features, working with Phaser, or building sprite-based web games.

Instalacje / 1h
1
GitHub Stars
360
Aktualizacja
4 lis