Gsp production code
Skill mike007jd/game-superpowers/publish/clawhub/gsp-production-code
Use when game implementation quality must be maintainable, understandable, and safe to extend.From its SKILL.md
npx -y skills add mike007jd/game-superpowers --skill gsp-production-codeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.1 KB, 208 tokens by cl100k_base, as published. Nobody here has run it
Game Production Code
Goal
Raise the code-quality floor. Unless the user explicitly asks for a throwaway spike, code should be written as though the project may continue and ship.
Reference
Use:
./shared/checklists/production-code-checklist.md./shared/reference/game-dev-abstractions.md
Apply these rules
- Prefer explicit ownership of state and side effects.
- Use game-native boundaries:
GameManager, controllers, state machines, systems, UI flow owners, sound layers. - Avoid fake implementations in the main path.
- Avoid copy-paste architecture in critical systems.
- Keep the code readable for the next developer or next session.
- If refactoring, document compatibility and rollback concerns.
Outputs
Follow the gsp-orchestrator output strategy:
- inline (default): present production code expectations in conversation.
- minimal or full: update
docs/game-studio/architecture.mdanddocs/game-studio/quality-target.md.
What ships with it: 7 files
5.8 KB alongside SKILL.md
examples/
- usage.md613 B
tests/
- smoke.md449 B
- CHANGELOG.md208 B
- MANIFEST.yaml2.2 KB
- README.md986 B