AgentStack
SKILL verified MIT Self-run

Gsp Hud Readability Audit

skill-mike007jd-game-superpowers-gsp-hud-readability-audit · by mike007jd

Use when auditing HUD hierarchy, readability, controls discoverability, or mobile thumb-zone pressure.

No reviews yet
0 installs
9 views
0.0% view→install

Install

$ agentstack add skill-mike007jd-game-superpowers-gsp-hud-readability-audit

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

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

Are you the author of Gsp Hud Readability Audit? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Game HUD Readability Audit

Goal

Audit the heads-up display and overlay layer for readability, hierarchy, and actionable clarity.

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/hud-readability-audit-checklist.md
  • ./shared/checklists/ui-ux-hard-rules.md
  • ./shared/reference/audit-confidence-and-evidence.md

Evaluate

  • information priority and hierarchy
  • readability of numbers, labels, and state cues
  • button affordance and control discoverability
  • text density and clutter
  • overlap between HUD and playfield
  • persistent HUD budget discipline
  • mobile thumb-zone or one-handed pressure
  • whether essential state is hidden, delayed, or over-explained
  • whether menu / pause / overlay states fight gameplay readability

Important

If screenshots are unavailable, state which claims are inferred from code or layout structure rather than observed directly. Call out explicit hard-rule violations when the playfield, focus, or safe-area behavior is likely wrong.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.