## Reference UX

Point at the best, then build better

### UX Researcher

Capture a live product experience as a design reference. Say "make our form flow like Airbnb's host onboarding" and the agent captures, analyzes, and documents the reference so your team can build from it.

## How it works

1. **Point at a reference**  
   Share a URL and describe what you admire about the experience. "I love how Stripe handles their pricing page layout."

2. **Capture the experience**  
   The agent walks through the reference product, capturing the flow, interactions, copy, and design patterns that make it work.

3. **Get a reference document**  
   Receive a structured breakdown of what makes the reference effective and how those patterns could apply to your product.

## Why use Reference UX

### Beyond screenshots

Captures the full experience — flow, micro-interactions, copy, and context — not just static images.

### Shareable references

Turn "make it like X" into a structured document the whole team can work from.

### Pattern extraction

Identifies the specific design decisions that make a reference work, not just what it looks like.

### Feeds into prototyping

Reference documents flow directly into the design and prototyping phase as concrete inspiration.

## When to use Reference UX

### Multi-step form redesign

Your long form has high abandonment. You want to reference a product that does multi-step forms well.

Capture the Airbnb host onboarding flow. I want to understand how they break a complex form into friendly steps.

### Onboarding inspiration

You are redesigning your onboarding and want to learn from products known for great first-run experiences.

Document how Figma onboards new users. Focus on progressive disclosure and the first "aha moment."

### Dashboard layout reference

You need to design a data-heavy dashboard and want to see how best-in-class products handle information density.

Capture how Linear presents project status. I want to understand their information hierarchy and density choices.