Gsp feedback audit
Skills-first game development superpowers for Claude Code and Codex: build, audit, polish, and productionize game projects with reusable Agent Skills.
npx -y skills add mike007jd/game-superpowers --skill gsp-feedback-auditAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when auditing responsiveness, rewards, failures, danger telegraphing, or state-transition feedback in a game.
SKILL.md
1.1 KB, as published. Nobody here has run it
Game Feedback Audit
Goal
Audit whether the game clearly responds to the player and communicates consequences.
Outputs
Follow the gsp-orchestrator output strategy:
- inline (default): present findings in conversation.
- minimal or full: write to
docs/game-studio/audit/audit-summary.md,docs/game-studio/audit/ux-findings.md,docs/game-studio/audit/scorecard.json.
Use:
../../shared/checklists/feedback-audit-checklist.md../../shared/checklists/game-feel-pillars.md../../shared/reference/audit-confidence-and-evidence.md
Evaluate
- input acknowledgment
- hit / damage / collect / upgrade / deny signals
- reward and success feedback
- fail and error feedback
- danger telegraphing
- state transition clarity
- whether feedback supports understanding or is merely decorative
Important
A feature that technically works but gives weak or missing feedback should be marked as partially complete, not fully complete.