Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Design & UI

game-superpowers

Design and build games, improve gameplay, game feel, visuals, sound and player-facing UI, or critique an existing game experience.

mike007jd · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add mike007jd/game-superpowers --skill game-superpowers

About this skill


name: game-superpowers description: Design and build games, improve gameplay, game feel, visuals, sound and player-facing UI, or critique an existing game experience.

Game Superpowers

Start from the current game and the requested change. Keep an established direction and engine; choose an approach that serves this game's interaction when starting fresh. For an open brief, connect 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 early and expand it to the requested scope. For a targeted change, work on the affected experience directly. A concept, prototype, full game and critique have different deliverables; follow the user's request.

Read only the reference relevant to the current work:

  • Gameplay: mechanics, meaningful choices, pacing and progression.
  • Presentation: game feel, camera, art, animation, VFX and sound.
  • Player experience: teaching, HUD, controls and transitions.

Use the ordinary player experience to guide improvements: identify the largest relevant gap, change its cause, then inspect the affected result when runtime work is authorized. Keep assets, scene bindings and player triggers connected; an unused asset or debug-only route does not complete a gameplay feature.

For critique, explain 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.

Use the user's scope and quality expectations. Tests and builds run on request; extra reports, scoring systems and release processes are not part of ordinary game work. Deliver the requested artifact and briefly state what changed and what remains unobserved.