agentsclimarketplace

Gsp ux flow designer

Skill mike007jd/game-superpowers/publish/clawhub/gsp-ux-flow-designer

Use when designing onboarding, menus, CTA hierarchy, and first-minute interaction flow for a game.From its SKILL.md

Install
npx -y skills add mike007jd/game-superpowers --skill gsp-ux-flow-designer

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

SKILL.md

1.8 KB, 367 tokens by cl100k_base, as published. Nobody here has run it

Game UX Flow Designer

Goal

Define the player-facing flow clearly enough that implementation does not drift into unreadable or frustrating UX.

Outputs

Follow the gsp-orchestrator output strategy:

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

Must cover

  • entry flow
  • first 30 seconds
  • start / restart / fail / success states
  • pause or escape flow when relevant
  • HUD priorities
  • onboarding style
  • readability and accessibility constraints
  • critical feedback moments

Hard rules

Use:

  • ./shared/reference/first-30-seconds.md
  • ./shared/checklists/ui-feedback-checklist.md
  • ./shared/checklists/ui-ux-hard-rules.md

Explicitly decide:

  • how the playfield is protected from overlay clutter
  • what the persistent HUD budget is
  • whether the project needs a dedicated UI layer for text-heavy or responsive UI
  • how pause, menu focus, pointer lock, camera control, and gameplay input hand off control
  • what mobile safe-area and thumb-zone constraints exist when relevant

By quality target

  • first-playable: first 30 seconds and essential affordances only
  • polished-prototype: include title/start, retry, pause, success/failure flow, clearer UI rhythm, and explicit playfield/HUD rules
  • production-feature / live-patch: preserve consistency with the existing product while improving the target flow

Important

Do not stop at vague UX language. Lock concrete player-facing rules that implementation can actually follow. If critical UX flow details are still unknown, ask follow-up questions until the flow is explicit enough to implement with confidence.

What ships with it: 8 files

8.6 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.