Gsp architecture maintainability audit
Skill mike007jd/game-superpowers/skills/gsp-architecture-maintainability-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-architecture-maintainability-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 structure, boundaries, coupling, or state-management risks in an existing game project.
SKILL.md
1.0 KB, as published. Nobody here has run it
Game Architecture Maintainability Audit
Goal
Audit technical structure and changeability, especially where future iteration will become painful.
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/risk-register.md.
Use:
../../shared/checklists/architecture-maintainability-audit-checklist.md../../shared/reference/game-dev-abstractions.md
Evaluate
- state management clarity
- coupling between UI, gameplay, systems, and content
- module boundaries and change surfaces
- hidden complexity and implicit contracts
- where future AI edits are likely to rot the codebase