bmad-agent-ux-designer

Translate user needs into UX design specifications and interaction guidance.

Updated May 23, 2026
One-click install
npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-agent-ux-designer-diegosanchespereira1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-agent-ux-designer
Source: https://github.com/diegosanchespereira1/lavarapido/tree/main/lava-rapido/.agents/skills/bmad-agent-ux-designer
Command: npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-agent-ux-designer-diegosanchespereira1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sally helps teams turn vague product ideas into clear UX direction, reducing ambiguity before design and implementation begin.

Core Features & Use Cases

  • Persona-driven guidance: Clarifies who the user is, what they need, and how the interface should behave.
  • Interaction and flow planning: Defines screens, states, edge cases, and transitions for web or app experiences.
  • Implementation-ready handoff: Produces practical UX specifications that support product, architecture, and engineering decisions.
  • Use Case: A team has a feature idea for a dashboard but no clear flow; Sally turns it into a structured interaction plan and design rationale.

Quick Start

Ask Sally to turn your product idea into a UX specification with key user flows, edge cases, and handoff notes.

Frequently Asked Questions about bmad-agent-ux-designer

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

FAQPage Schema
How do I turn a product idea into UX specifications with user flows and edge cases?

To turn a product idea into UX specifications, you define user goals, apply persona-driven analysis, and map screen structures, states, and transitions. This produces interaction guidance and handoff-ready recommendations for web and app delivery.

What is persona-driven interaction design and when do I need it for app planning?

Persona-driven interaction design clarifies who the user is, what they need, and how the interface should behave. You need it during the planning phase to reduce ambiguity and define structured screen flows before implementation begins.

Can I use UX specifications for both web and app experiences?

Yes, UX specifications apply to both web and app experiences. The interaction and flow planning defines screens, states, edge cases, and transitions across platforms to support architecture and engineering delivery.

What's the best way to structure handoff-ready UX specs for engineering teams?

The best way to structure handoff-ready UX specs is to define implementation-aware decisions that support product architecture. This includes mapping key user flows, documenting edge cases, and providing clear design rationale.

Why does my dashboard feature lack clear interaction flows before design begins?

Your dashboard lacks clear interaction flows because vague product ideas require persona-driven analysis and empathy-led mapping. Defining user goals and screen structures translates ambiguous concepts into structured plans and design rationale.

Do I need clear user goals to generate wireframes and interaction guidance?

Yes, you need clear user goals to generate interaction guidance. Empathy-led analysis and defined user needs are required to produce practical UX specifications that support architecture and delivery decisions.