Gsp ux flow audit
Skill mike007jd/game-superpowers/publish/clawhub/gsp-ux-flow-audit
Use when auditing first-minute onboarding, menus, fail/retry flow, or player comprehension in a game.From its SKILL.md
npx -y skills add mike007jd/game-superpowers --skill gsp-ux-flow-auditAssembled 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.2 KB, 279 tokens by cl100k_base, as published. Nobody here has run it
Game UX Flow Audit
Goal
Audit the player journey and moment-to-moment experience flow, especially the first 30 seconds.
Outputs
Follow the gsp-orchestrator output strategy:
- inline (default): present findings in conversation.
- minimal or full: write to
docs/game-studio/audit/ux-findings.md,docs/game-studio/audit/audit-summary.md,docs/game-studio/audit/scorecard.json.
Use:
./shared/checklists/ux-flow-audit-checklist.md./shared/reference/first-30-seconds.md./shared/reference/audit-confidence-and-evidence.md
Evaluate
- first actionable screen clarity
- onboarding length and interruption cost
- main verb discoverability
- fail / retry / pause / resume flow
- menu-to-play transitions
- whether the UI or setup blocks the core loop
Evidence discipline
Tag each important finding with:
- confidence:
high,medium, orlow - evidence:
code,config,asset,screenshot, orinferred
Output style
Write findings in game-language, such as:
- what the player understands too late
- what the player is asked to do too early
- where friction kills momentum
What ships with it: 8 files
6.0 KB alongside SKILL.md
examples/
- usage.md605 B
shared/
tests/
- smoke.md445 B
- CHANGELOG.md206 B
- MANIFEST.yaml2.4 KB
- README.md981 B