ux-design

Design UX specifications for screens, flows, HUDs, CLI interactions, and API journeys.

18|5|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill ux-design-wsman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-design
Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/ux-design
Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill ux-design-wsman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn a screen, flow, HUD, CLI interaction, or API journey into a clear UX specification without missing the important product, journey, accessibility, or interaction details.

Core Features & Use Cases

  • Guided spec writing: Works section by section so you can define purpose, context, layout, states, interactions, data needs, and acceptance criteria in a structured way.
  • Context-aware design support: Reads concept docs, CDDs, existing UX specs, style references, accessibility requirements, and platform input preferences before drafting.
  • Retrofit-friendly workflow: Can update an existing UX spec by identifying what is already complete and filling only the missing or placeholder sections.
  • Use case: Use this when you need to design a new product screen, document a CLI or API interaction, or build a HUD spec that aligns with established architecture and design constraints.

Quick Start

Tell me the screen, flow, HUD, CLI command, or API journey you want to design, and I will guide you through the UX spec step by step.

Frequently Asked Questions about ux-design

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

FAQPage Schema
How do I write a UX spec for an API consumer journey without missing interaction details?

UX specs for an API consumer journey are written section by section, defining purpose, context, states, interactions, data needs, and acceptance criteria with guided approval checkpoints. This ensures all interaction details are captured systematically.

Can I update an existing UX spec to fill in missing layout and state handling sections?

Yes, existing UX specs can be retrofitted by identifying which sections are already complete and generating content only for the missing or placeholder sections. This preserves your current layout and state handling while filling gaps.

What's the best way to document CLI interactions and HUD layouts for game design?

Documenting CLI interactions and HUD layouts works best through context-aware structure, journey mapping, and state handling. The process reads existing concept docs and platform input preferences before drafting the interaction design.

Does this UX design workflow support accessibility-aware deliverables for product screens?

Yes, UX design workflows support accessibility-aware deliverables by reading accessibility requirements and style references before drafting product screen specifications. This ensures compliance throughout the spec authoring process.

How do I structure a UX specification for a complex product flow with multiple states?

Structure a UX specification by working section by section through purpose, context, layout, states, interactions, data needs, and acceptance criteria. Guided approval checkpoints validate each state before proceeding to the next.

Do I need concept docs or CDDs before starting UX spec authoring for a new screen?

While concept docs, CDDs, and existing UX specs are read for context before drafting, you can start by simply describing the screen, flow, or CLI interaction you want to design to begin the guided specification process.