game-superpowers

Installation
SKILL.md

Game Superpowers

Start from the current game and the requested change. If the project already has a direction and engine, keep them. When starting fresh, pick the engine and style that best serve the core interaction. For an open brief, decide what the player does, why it matters and how it should feel. Ask only about missing decisions that would materially change the game.

Build around action → feedback → consequence → next decision. For a new game, make that loop playable first, then expand to the requested scope. For a targeted change, work directly on the affected experience. A concept, prototype, full game and critique have different deliverables; follow the user's request.

Read the references that match the work. For a new game, read all four.

  • Gameplay: mechanics, choices, pacing, progression and difficulty.
  • Presentation: game feel, camera, art, animation, VFX and sound.
  • Player experience: teaching, HUD, controls and transitions.
  • Runtime: timing, input, audio, screens, performance and saves; the bugs that make a game break or feel wrong.

To improve a game, find the largest gap in the ordinary player's experience, fix its cause, then check the result. Keep assets, scene bindings and player triggers connected: an asset that is never loaded or a feature reachable only through a debug route is not done.

Run what you build. Whenever the environment can launch the game (dev server, headless browser, engine CLI), start it after meaningful changes and confirm that it loads without errors, the first screen renders and the core action responds. Use screenshots or scripted input when available. Heavy test suites, release builds and formal reports wait for the user's request. If you could not run something, say so.

For critique, describe the observed problem, its effect on the player and a concrete improvement. Keep observation separate from inference: source reveals rules, screenshots reveal composition, motion reveals timing, listening reveals the mix, and player feedback reveals understanding and enjoyment.

Installs
10
GitHub Stars
25
First Seen
Oct 19, 2026