create-ux-design

Create DESIGN.md and EXPERIENCE.md UX specification artifacts.

4|2|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/anderson-0/mighty-powers --skill create-ux-design-anderson-0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-ux-design
Source: https://github.com/anderson-0/mighty-powers/tree/main/skills/create-ux-design
Command: npx skills add https://github.com/anderson-0/mighty-powers --skill create-ux-design-anderson-0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps teams turn unclear product ideas into structured UX decisions by facilitating discovery, capturing user intent, and producing durable design documentation.

Core Features & Use Cases

  • UX Discovery Facilitation: Guides conversations to uncover product goals, journeys, platforms, accessibility needs, and interaction requirements without imposing design choices.
  • Design Documentation: Creates paired DESIGN.md and EXPERIENCE.md artifacts that separate visual identity decisions from behavioral and interaction specifications.
  • Use Case: A product team starting a new application can use this Skill to define information architecture, key user flows, component behaviors, and visual system requirements before implementation begins.

Quick Start

Ask the create-ux-design skill to help me create UX specifications for my new product experience.

Frequently Asked Questions about create-ux-design

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

FAQPage Schema
How do I create UX specifications from a product vision?

Creating UX specifications from a product vision involves facilitating discovery to capture user intent and goals, then generating paired DESIGN.md and EXPERIENCE.md artifacts that define information architecture, interaction patterns, and accessibility requirements.

What is the best way to document information architecture and user journeys?

The best way to document information architecture and user journeys is by generating structured design documentation that separates visual identity decisions from behavioral specifications, ensuring component behaviors and interaction requirements are clearly mapped.

How do I structure design documentation for interface planning?

To structure design documentation for interface planning, generate paired artifacts that separate visual system requirements from experience specifications, capturing token references, interaction patterns, and accessibility considerations for the implementation team.

Can I use this approach to define accessibility needs during product discovery?

Yes, you can use this approach to define accessibility needs during product discovery. It guides conversations to uncover accessibility requirements and integrates them directly into the generated UX design specifications and review processes.

What is included in UX validation workflows for new applications?

UX validation workflows for new applications include defining key user flows, component behaviors, and visual system requirements. The process produces durable design documentation with review processes to validate interface planning and user intent.