agentsclimarketplace

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

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

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

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, or low
  • evidence: code, config, asset, screenshot, or inferred

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/

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.