game-ui-review

Use when a user asks to review game UI/UX, screenshot readability, text overlap, first-player confusion, mobile layout, control reachability, HUD clarity, or player-facing wording. Requires concrete e

SKILL.md

GitHub

Game UI Review

Review UI like a player, not only like a developer.

Evidence Needed

  • screenshot or report path;
  • viewport size;
  • target player profile;
  • current objective;
  • primary action;
  • known complaint or uncertainty.

Review Axes

  • first action is visible;
  • text does not overlap;
  • labels fit their containers;
  • key controls are reachable;
  • optional systems do not compete with the next step;
  • wording uses player-facing verbs before domain jargon.

Output

For each finding:

  • severity;
  • screenshot or evidence;
  • observed issue;
  • player impact;
  • smallest safe fix;
  • verification target.

Stop Rules

Do not redesign the whole UI from one screenshot. Do not make runtime edits, mobile rewrites, or release-gate changes without explicit scope and verification.