Gsp Ux Flow Designer
Use when designing onboarding, menus, CTA hierarchy, and first-minute interaction flow for a game.
Install
$ agentstack add skill-mike007jd-game-superpowers-gsp-ux-flow-designer ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-mike007jd-game-superpowers-gsp-ux-flow-designer) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: mike007jd
- Source: mike007jd/game-superpowers
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.