Gsp feel 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-feel-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 control feel, responsiveness, timing, camera reaction, or animation feedback in a game.
SKILL.md
1.1 KB, as published. Nobody here has run it
Game Feel Audit
Goal
Audit whether the game seems responsive, readable, and satisfying rather than merely functional.
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/scorecard.json,docs/game-studio/audit/ux-findings.md.
Use:
../../shared/checklists/gsp-feel-audit-checklist.md../../shared/checklists/game-feel-pillars.md../../shared/reference/audit-confidence-and-evidence.md
Evaluate
- apparent input-to-response latency in the implementation
- camera behavior around motion and impact
- timing support for attacks, movement, traversal, or collection
- feel debt caused by missing polish hooks
- emotionally dead interactions that need stronger juice or pacing
Important
Without runtime evidence, do not overstate certainty. Identify whether findings are confirmed or probable.