ux-design

Transforms research findings into interface-ready specs and design-system-compatible documentation for engineers.

15|3|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/LazyIsEfficient/agentic-os --skill ux-design-lazyisefficient
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-design
Source: https://github.com/LazyIsEfficient/agentic-os/tree/main/.claude/skills/ux-design
Command: npx skills add https://github.com/LazyIsEfficient/agentic-os --skill ux-design-lazyisefficient

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

UX design often stalls when turning research into concrete interfaces and coherent handoff artifacts. This Skill provides a structured approach to translating insights into wireframes, flows, and design-system-compatible specs that engineers can implement reliably.

Core Features & Use Cases

  • Transform research findings into IA, interaction patterns, and microcopy for real products.
  • Create and critique flows, wireframes, and prototypes with accessibility and usability in mind.
  • Produce handoff-ready documentation, tokens, and templates to align design and engineering teams.

Quick Start

Use this skill to convert a research finding into a concrete UX design plan that covers discovery, definition, development, and delivery, including accessibility considerations.

Frequently Asked Questions about ux-design

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

FAQPage Schema
How do I turn UX research findings into handoff-ready specs?

To turn UX research findings into handoff-ready specs, translate insights into information architecture, wireframes, and design-system-compatible token specs that align engineering and product teams for reliable implementation.

What is the best way to structure information architecture for a new product?

Structuring information architecture involves translating research findings into interaction patterns and interface structures. This process ensures accessible, usable product flows from discovery through final engineering handoff.

Can I use this approach for accessibility audits and design-system governance?

Yes, this approach supports accessibility audits and design-system governance by applying structured critique, token-based design, and usability checks to interface patterns across product teams.

How do I align design and engineering teams during UX handoff?

Align design and engineering teams during UX handoff by producing handoff-ready documentation, design tokens, and structured templates that define interaction patterns and interface requirements clearly.

Does this UX design method work for both prototyping and microcopy generation?

Yes, this UX design method works for both prototyping and microcopy generation by transforming research findings into concrete interaction patterns, wireframes, and interface text for real products.

When should I use structured design critique over informal feedback?

Use structured design critique over informal feedback when evaluating flows, wireframes, and prototypes against accessibility and usability standards to ensure coherent, handoff-ready design specifications.