ux-review

Validate UX specifications, HUD designs, and interaction pattern libraries for implementation readiness.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/johnatas-henrique/overdrive --skill ux-review-johnatas-henrique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-review
Source: https://github.com/johnatas-henrique/overdrive/tree/main/.opencode/skills/ux-review
Command: npx skills add https://github.com/johnatas-henrique/overdrive --skill ux-review-johnatas-henrique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UX specifications that are incomplete, misaligned with game design documents, or non-compliant with accessibility requirements cause costly rework and delays when handed off to implementation teams. This skill acts as an early quality gate to catch gaps before they reach the production pipeline.

Core Features & Use Cases

  • Multi-document validation: Reviews UX specs, HUD designs, and interaction pattern libraries against completeness, accessibility, GDD alignment, and implementation readiness standards.
  • Structured verdicts: Produces clear APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED outcomes with specific, actionable gap identification.
  • Use Case: For a 90s F1-style racing game, validate the inventory screen UX spec before passing it to the UI programmer to ensure all error states, input method coverage, and accessibility requirements are documented, avoiding downstream rework.

Quick Start

Use the ux-review skill to validate the UX spec at design/ux/inventory.md for implementation readiness.

Frequently Asked Questions about ux-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate UX specifications for implementation readiness before handing off to programmers?

Validating UX specifications for implementation readiness involves reviewing UX specs, HUD designs, and interaction pattern libraries for completeness, accessibility compliance, GDD alignment, and input method coverage. This produces structured verdicts identifying specific gaps for remediation before production handoff.

What is the best way to check if my HUD design aligns with the game design document?

Checking HUD design alignment with GDD involves reviewing the design against game design documents to ensure consistency. A structured GDD alignment review verifies that interface elements match documented game mechanics and requirements, preventing costly rework during implementation.

Can I use an automated UX review to catch accessibility compliance gaps in my game interface?

An automated UX review can catch accessibility compliance gaps in game interfaces by evaluating HUD designs and UX specs against accessibility standards. This early quality gate identifies specific compliance issues before the design reaches the production pipeline.

What limitations should I expect when running a pre-implementation UX validation for game development workflows?

Pre-implementation UX validation for game development workflows is limited to reviewing documented specifications, HUD designs, and pattern libraries. It cannot evaluate runtime behavior or performance, relying entirely on the completeness of the input UX documentation to produce accurate gap identification.

How do I get a structured approval verdict for my inventory screen UX spec?

Getting a structured approval verdict for an inventory screen UX spec requires submitting the design document for a completeness and implementation readiness review. The process outputs an APPROVED, NEEDS REVISION, or MAJOR REVISION NEEDED verdict with specific gap identification for remediation.