ux-design

Automate gathering game design assets for UX and HUD documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Game UX and HUD design often suffers from inconsistency and misalignment with existing project assets like game design documents, player journey maps, and accessibility requirements, as designers must manually cross-reference scattered resources to create compliant, context-aware designs.

Core Features & Use Cases

  • Multi-mode authoring: Create per-screen/flow UX specifications, full HUD design documents, or a centralized interaction pattern library depending on your needs.
  • Automated context gathering: Automatically pulls relevant context from game concept docs, player journey maps, GDD UI requirements, existing UX specs, art bibles, and accessibility requirements to eliminate manual research.
  • Use Case: A game designer working on a new inventory screen can invoke this skill to automatically pull all relevant GDD requirements and player journey context, then walk through a structured, approval-based authoring process to produce a complete UX spec that aligns with the project's existing design standards.

Quick Start

Invoke the ux-design skill with a screen or flow name, "hud", or "patterns" to start a guided, context-aware design authoring session.

Frequently Asked Questions about ux-design

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

FAQPage Schema
How do I create game UX specs that align with my existing GDD and player journey maps?

Structured, section-by-section authoring builds game UX specs by automatically gathering context from your GDD, player journey maps, and accessibility requirements to ensure full alignment and eliminate manual cross-referencing.

What is the best way to document game HUD design without missing UI requirements?

Invoking a guided authoring session builds full HUD design documents while enforcing alignment with GDD UI requirements and existing project design patterns through built-in cross-reference checks and approval workflows.

How do I build a centralized interaction pattern library for my game development workflow?

Invoking the patterns mode builds a centralized interaction pattern library by gathering relevant project design assets and structuring your interaction patterns to maintain consistency across your game development workflow.

Can I automatically pull context from art bibles and accessibility requirements when authoring UX designs?

Automated context gathering pulls relevant data from game concept docs, art bibles, accessibility requirements, and existing UX specs to eliminate context gaps and manual research during your design authoring.

Do I need to manually cross-reference game design documents before writing a per-screen UX spec?

No manual cross-referencing is needed. The workflow automatically pulls relevant GDD UI requirements and player journey context to guide a structured, approval-based authoring process for your per-screen UX spec.