Help us improve
Share bugs, ideas, or general feedback.
From game-creator
Audits visual design, polish, UI, particles, animations, and game feel of existing JavaScript games. Scores areas like background and typography, then implements improvements via Constants.js and EventBus without gameplay changes.
npx claudepluginhub playableintelligence/game-creator --plugin game-creatorHow this skill is triggered — by the user, by Claude, or both
Slash command
/game-creator:design-game [path-to-game][path-to-game]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Take your time to do this thoroughly
Analyzes and improves UI/UX of browser games with visual polish, atmospheres, backgrounds, particles, animations, transitions, and juice effects. Use for aesthetic and player experience upgrades.
Plans UX patterns and design specifications for game UI/HUD elements. Useful for developers planning game interfaces.
Audits app UIs for visual hierarchy, spacing, typography, color, alignment, and components; generates phased, implementation-ready refinement plans.
Share bugs, ideas, or general feedback.
Run a UI/UX design pass on an existing game to improve visuals, atmosphere, and game feel. No design experience needed — this command analyzes your game and applies proven visual patterns.
Analyze the game at $ARGUMENTS (or the current directory if no path given).
First, load the game-designer skill to get the full design vocabulary and patterns.
package.json to identify the enginesrc/core/Constants.js for the current color palette and configsrc/core/EventBus.js for existing eventsScore each area 1-5 and present as a table:
| Area | Score | Notes |
|---|---|---|
| Background & Atmosphere | ||
| Color Palette | ||
| Animations & Tweens | ||
| Particle Effects | ||
| Screen Transitions | ||
| Typography | ||
| Game Feel / Juice | ||
| Game Over | ||
| Expression Usage | If personality characters exist, score how reactively expressions change to game events. Score 1 if expressions never change. |
Then list the top improvements ranked by visual impact, with a plain-English description of what each one does (e.g., "Add a sky gradient so the background looks like a real sky instead of a flat color").
Ask the user which improvements they want, or implement all if they say so. Follow the game-designer skill patterns:
Constants.jsnpm run build to confirm no errors/design-game examples/asteroid-dodge
Result: Audits visuals → scores Background 2/5, Particles 1/5, Typography 3/5 → adds sky gradient background, star parallax, explosion particles on asteroid destroy, screen shake on hit, smooth scene transitions. All values in Constants.js.
Cause: Too many particle emitters or gradient fills per frame. Fix: Limit active particles (pool and reuse). Use cached gradient textures instead of recreating per-frame.
Cause: Hardcoded pixel positions instead of using PX scale factor. Fix: All positions and sizes should use Constants.js PX-relative values.
Tell the user:
Your game looks much better now! Next, run
/game-creator:add-audioto add chiptune background music and retro sound effects — all procedurally generated, no audio files needed.Pipeline progress:
/viral-game→/design-game→/add-audio→/qa-game→/review-game(This is the
/viral-gameone-shot pipeline — not the/make-gamemulti-session, milestone-driven workflow.)