Gsp project audit
Use when running a top-level audit of an existing game project before repair or major changes.From its SKILL.md
npx -y skills add mike007jd/game-superpowers --skill gsp-project-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
- 4 stars4 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.
SKILL.md
2.8 KB, 680 tokens by cl100k_base, as published. Nobody here has run it
Game Project Audit
Goal
Audit an existing game project from multiple dimensions before making implementation changes. Default to read-only first.
Default modes
audit-only— produce findings onlyaudit-and-plan— produce findings and a repair roadmapaudit-and-patch— audit first, then patch only approved high-value issues
Outputs
Follow the gsp-orchestrator output strategy:
- inline (default): present all findings, scorecard, and repair directions in conversation. Do not create
docs/files. - minimal: write only
docs/game-studio/audit/audit-summary.mdfor cross-session reference. - full: create and maintain the audit summary, scorecard, UX findings, repair roadmap, and risk register files listed below.
Full output files (when strategy = full):
docs/game-studio/audit/audit-summary.mddocs/game-studio/audit/scorecard.jsondocs/game-studio/audit/ux-findings.mddocs/game-studio/audit/repair-roadmap.mddocs/game-studio/audit/risk-register.md
Use:
../../shared/templates/audit-summary.md../../shared/templates/audit-scorecard.md../../shared/templates/ux-findings.md../../shared/templates/repair-roadmap.md../../shared/templates/risk-register.md../../shared/checklists/project-audit-master-checklist.md../../shared/checklists/ui-ux-hard-rules.md../../shared/reference/audit-modes.md../../shared/reference/audit-confidence-and-evidence.md
Audit workflow
- Assess project state and release risk with
gsp-project-state-assessment. - Determine audit mode and focus dimensions.
- Run the relevant sub-audits:
gsp-ux-flow-auditgsp-hud-readability-auditgsp-feedback-auditgsp-audio-feedback-auditgsp-feel-auditgsp-mechanics-systems-auditgsp-scope-completeness-auditgsp-production-readiness-auditgsp-architecture-maintainability-auditgsp-live-risk-auditwhen the repo is shipped or high-risk
- Consolidate findings with
gsp-audit-scorecard. - If requested, create a prioritized fix plan with
gsp-repair-roadmap. - Patch only after the audit report exists and the requested mode allows edits.
Rules
- Never start by changing files when the request is clearly an audit.
- Distinguish between confirmed issues and high-confidence inferred issues.
- Always include evidence and confidence for important findings.
- Prefer game-native language over frontend jargon.
- Call out hard-rule violations when UI flow, HUD pressure, or input-focus conflicts are likely hurting the player experience.
Stop condition
You are done when the project has a clear audit summary, a dimensional scorecard, a risk register, and a repair roadmap if requested.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.