Game Feedback Design
Published by mike007jd in game-superpowers
No known issues1 installs
What this skill does
Design the game’s feedback grammar across visuals, audio, motion, danger signaling, reward signaling, and UI acknowledgment so the result feels alive rather than placeholder-level.
Add Game Feedback Design to your agent
Review the source and files first. When you are ready, copy the prompt instruction or use the CLI command supported by your environment.
Install with a prompt
Paste this into a compatible coding agent:
add this skill "game-feedback-design" from https://github.com/mike007jd/game-superpowersInstall with the CLI
Run this command in a controlled environment after reviewing the repository:
npx skills add https://github.com/mike007jd/game-superpowers --skill game-feedback-designSkill instructions
Game Feedback Design
Goal
Make feedback part of the design, not something bolted on at the end.
Outputs
Respect the output strategy set by using-game-superpowers:
- inline (default): present feedback design in conversation.
- minimal or full: write
docs/game-studio/feedback-design.md.
Use:
../../shared/templates/feedback-design.md../../shared/checklists/feedback-design-checklist.md../../shared/checklists/game-feel-pillars.md../../shared/checklists/ui-ux-hard-rules.md
Cover
- input acknowledgment
- success / reward signals
- fail / deny signals
- danger telegraphing
- state transition feedback
- audio priorities
- micro-motion and juice that support clarity rather than noise
- which feedback belongs in the world layer vs the HUD layer
Use when
- the build works but feels dead
- the target is
polished-prototypeor above - combat, traversal, collection, menuing, or puzzle interactions need stronger feel
Important
Feedback is part of the mechanic contract. If the game does not communicate clearly or feel responsive, it is not “done enough.”
Files included
- SKILL.md

