agentsclimarketplace

Gsp mechanics systems design

Skill mike007jd/game-superpowers/publish/clawhub/gsp-mechanics-systems-design

Use when translating a locked concept into concrete game systems, progression, state, and encounter rules.From its SKILL.md

Install
npx -y skills add mike007jd/game-superpowers --skill gsp-mechanics-systems-design

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.0 KB, 186 tokens by cl100k_base, as published. Nobody here has run it

Game Mechanics Systems Design

Goal

Turn the concept into a concrete systems design that game developers can reason about and extend.

Outputs

Follow the gsp-orchestrator output strategy:

  • inline (default): present systems design in conversation.
  • minimal or full: write docs/game-studio/system-design.md.

Use:

  • ./shared/templates/system-design.md
  • ./shared/reference/game-dev-abstractions.md

Cover

  • primary and secondary verbs
  • core loop and loop exits
  • state model
  • encounter / obstacle / challenge model
  • progression or meta progression
  • save / persistence boundaries
  • sound ownership and feedback ownership

Important

Prefer game-native concepts such as GameManager, StateMachine, EncounterDirector, HUDFlow, and SoundLayer. Do not let runtime-specific jargon replace actual game design clarity.

What ships with it: 7 files

5.1 KB alongside SKILL.md

examples/

tests/

Keep looking

Skills are one crate of 613,531. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.