Gsp loop bootstrap
Skill mike007jd/game-superpowers/publish/clawhub/gsp-loop-bootstrap
Use when establishing core game runtime structure such as state flow, control, camera, and UI ownership.From its SKILL.md
npx -y skills add mike007jd/game-superpowers --skill gsp-loop-bootstrapAssembled 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
1.0 KB, 191 tokens by cl100k_base, as published. Nobody here has run it
Game Loop Bootstrap
Goal
Create a maintainable gameplay architecture that matches the chosen target quality.
Outputs
Follow the gsp-orchestrator output strategy:
- inline (default): present architecture decisions in conversation.
- minimal or full: write or update
docs/game-studio/architecture.md.
Prefer abstractions like
GameManagerInputProfileStateMachinePlayerControllerCameraRigHUDFlowSoundLayerEncounterDirector
Rules
- Separate simulation state and UI state clearly enough to reason about them.
- Avoid hiding critical gameplay state inside presentation objects.
- Choose the simplest architecture that still supports the requested result.
- In aggressive greenfield modes, do not fear building a complete coherent shell if it prevents later churn.
- In live modes, preserve compatibility unless a deliberate migration plan exists.
What ships with it: 5 files
3.9 KB alongside SKILL.md
examples/
- usage.md609 B
tests/
- smoke.md447 B
- CHANGELOG.md207 B
- MANIFEST.yaml1.7 KB
- README.md990 B