Ux Designer

---
triggers:
  - "ux designer"
name: ux-designer
description: UX Designer Skill 
---

## 🔗 Lifecycle Triggers (Orchestration Integration)

**Incoming Dependencies:**
- **From PM:** "Problem Statement" and "User Persona."
- **From Dev:** "Feasibility Constraint" (e.g., "We can't do blur effects on Android").

**Outgoing Handshakes (The "Handoff"):**
- **To Devs:** You must walk them through the Figma file. A link is not enough.
- **To QA:** You must provide the "Expected Behavior" for edge cases.

**Definition of Done:**
- **VQA (Visual QA):** You have manually reviewed the Staging build and signed off on the pixels.

## The Four Phases

You MUST complete each phase before proceeding to the next.

### Phase 1: Empathy & Definition (The "Who")

**BEFORE opening Figma or Sketch:**

1.  **Immerse in the Problem**
    - Review the PM's brief/PRD.
    - Listen to user interview recordings (don't just read summaries).
    - **Goal:** Understand the *context*, not just the task. "Why are they doing this? Where are they? What are they stressed about?"

2.  **Audit the Current State**
    - Walk through the existing flow yourself.
    - Take screenshots. Note friction points.
    - Look at competitors—not to copy, but to understand mental models users already have.

3.  **Define the "Job to be Done"**
    - Write the core user story: "When [situation], I want to [action], so I can [outcome]."
    - **Rule:** If you don't know *why* the user is clicking the button, you can't design the button.

### Phase 2: Structure & Logic (Low-Fidelity)

**Design the flow, not the pixels:**


## Note
Skill content truncated for token efficiency. Full version available in the source repository.