user-experience

What this skill does

<!-- NOTE: activation-keywords (19 entries) intentionally differ from mandatory-skill-usage.md trigger map.
     activation-keywords are SKILL.md-scoped terms for Claude Code agent discovery (H-26).
     The trigger map uses broader/narrower terms with negative keywords for routing disambiguation (H-36b).
     This asymmetry is by design per agent-routing-standards.md Enhanced Trigger Map specification:
     trigger map keywords are routing-optimized; activation-keywords are discovery-optimized. -->

# User-Experience Skill

> **Version:** 1.0.0
> **Framework:** Jerry User-Experience
> **Constitutional Compliance:** Jerry Constitution v1.0
> **SSOT References:** GitHub Issue #138 (Architecture Spec), PROJ-022 PLAN.md, ADR-agent-design-001 (Agent Definition Format)
> **Project:** PROJ-022 User Experience Skill | GitHub Issue [#138](https://github.com/geekatron/jerry/issues/138)

## Document Sections

| Section | Purpose |
|---------|---------|
| [Document Audience](#document-audience-triple-lens) | Triple-Lens audience guide |
| [Purpose](#purpose) | Skill overview and key capabilities |
| [When to Use This Skill](#when-to-use-this-skill) | Activation triggers and scope boundaries |
| [Available Agents](#available-agents) | 11-agent roster with roles, models, and output locations |
| [P-003 Compliance](#p-003-compliance) | Orchestrator-worker hierarchy diagram |
| [Invoking an Agent](#invoking-an-agent) | Three invocation methods with examples |
| [Wave Architecture](#wave-architecture) | 5-wave criteria-gated deployment model |
| [Lifecycle-Stage Routing](#lifecycle-stage-routing) | Orchestrator triage by product stage |
| [Synthesis Hypothesis Validation](#synthesis-hypothesis-validation) | 3-tier confidence gate protocol |
| [MCP Integration Architecture](#mcp-integration-architecture) | Dependency matrix, cost tiers, fallback paths |
| [Cross-Skill Integration](#cross-skill-integration) | Integration with eng-team, red-team, adversary, orchestration, and others |
| [Constitutional Compliance](#constitutional-compliance) | Governing principles |
| [Quick Reference](#quick-reference) | Common workflows and agent selection hints |
| [References](#references) | Full repo-relative paths to all referenced files |

## Document Audience (Triple-Lens)

This SKILL.md serves multiple audiences:

| Level | Audience | Sections to Focus On |
|-------|----------|---------------------|
| **L0 (Stakeholder)** | New users, product managers | [Purpose](#purpose), [When to Use This Skill](#when-to-use-this-skill), [Quick Reference](#quick-reference) |
| **L1 (Developer)** | Engineers invoking agents | [Invoking an Agent](#invoking-an-agent), [Available Agents](#available-agents), [Lifecycle-Stage Routing](#lifecycle-stage-routing) |
| **L2 (Architect)** | Workflow designers, skill maintainers | [Wave Architecture](#wave-architecture), [MCP Integration Architecture](#mcp-integration-architecture), [Synthesis Hypothesis Validation](#synthesis-hypothesis-validation) |

---

## Purpose

The User-Experience skill provides AI-augmented UX methodology for tiny teams (1-5 people) through 11 agents (1 orchestrator + 10 framework specialists). Each agent encapsulates a proven UX framework, produces **persistent artifacts** that survive context compaction, enforces methodological rigor via synthesis hypothesis confidence gates, and builds a cumulative product UX knowledge base.

The skill targets teams where UX is a part-time responsibility -- calibrated for 20-50% of one person's time in Waves 1-2, with Waves 3-5 as aspirational progression.

### Key Capabilities

- **Heuristic Evaluation** -- Nielsen's 10 Heuristics with severity-rated findings (Wave 1)
- **Jobs-to-Be-Done Analysis** -- User motivation research, switch interviews, job mapping (Wave 1)
- **Lean UX Facilitation** -- Hypothesis-driven build-measure-learn cycles (Wave 2)
- **HEART Metrics** -- Google's Goals-Signals-Metrics (GSM) framework for UX measurement (Wave 2)
- **Atomic Design** -- Brad Frost's 5-level component taxonomy (Wave 3)
- **Inclusive Design Evaluation** -- WCAG 2.2 compliance and Microsoft Inclusive Design (Wave 3)
- **Behavior Diagnosis** -- Fogg B=MAP bottleneck analysis (Wave 4)
- **Kano Feature Prioritization** -- Must-be / Performance / Attractive classification (Wave 4)
- **Design Sprint Facilitation** -- AJ&Smart Design Sprint 2.0 four-day process (Wave 5)
- **AI-First Interaction Design** -- AI interface patterns and trust calibration (Wave 5, CONDITIONAL)

> **Deployment Status (v1.0.0):** The skill architecture is fully specified but sub-skills deploy incrementally through the wave model. Currently deployed: `ux-orchestrator` (Wave 0 Foundation). Wave 1-5 sub-skill agents are **not yet deployed** — invoking the skill before their wave completes will route to only the currently-available sub-skills. The orchestrator discloses deployment state to users per P-022 and offers the wave bypass mechanism for urgent needs. See [Wave Architecture](#wave-architecture) for the full deployment timeline.

---

## When to Use This Skill

Activate when:

- Evaluating an existing interface against usability heuristics
- Conducting user research to understand motivations (JTBD, switch interviews)
- Designing or validating a Lean UX hypothesis and experiment cycle
- Defining or measuring UX metrics using the HEART framework
- Building or auditing a component library using atomic design principles
- Auditing for accessibility compliance (WCAG 2.2, inclusive design)
- Diagnosing why users fail to take a desired action (Fogg B=MAP)
- Prioritizing features by user satisfaction impact (Kano analysis)
- Running a structured design sprint for rapid prototyping
- Designing AI-powered interfaces or conversational interactions
- Performing a comprehensive multi-framework UX audit (orchestrator routes to 2+ agents)
- Urgent UX triage via crisis mode (3-skill emergency sequence)

Do NOT use for:

- Security-focused code review or threat modeling (use `/eng-team`)
- Systems engineering requirements or V&V (use `/nasa-se`)
- General research without UX focus (use `/problem-solving`)
- Adversarial quality review of deliverables (use `/adversary`)
- Offensive security testing (use `/red-team`)
- Architecture design without user-facing concerns (use `/architecture`)
- Documentation writing (use `/diataxis`)

---

## Available Agents

| Agent | Role | Tier | Mode | Model | Wave | Output Location |
|-------|------|------|------|-------|------|-----------------|
| `ux-orchestrator` | Parent orchestrator: routing, wave gating, cross-framework synthesis | T5 | Integrative | Opus | 0 | `projects/${JERRY_PROJECT}/engagements/{engagement-id}/ux-orchestrator-{topic-slug}.md` |
| `ux-heuristic-evaluator` | Nielsen heuristic evaluation specialist | T4 | Systematic | Haiku* | 1 | `projects/${JERRY_PROJECT}/engagements/{engagement-id}/ux-heuristic-evaluator-{topic-slug}.md` |
| `ux-jtbd-analyst` | Jobs-to-Be-Done research and analysis | T4 | Divergent | Sonnet | 1 | `projects/${JERRY_PROJECT}/engagements/{engagement-id}/ux-jtbd-analyst-{topic-slug}.md` |
| `ux-lean-ux-facilitator` | Lean UX hypothesis and experiment facilitation | T4 | Systematic | Sonnet | 2 | `projects/${JERRY_PROJECT}/engagements/{engagement-id}/ux-lean-ux-facilitator-{topic-slug}.md` |
| `ux-heart-analyst` | HEART metrics framework specialist | T2 | Systematic | Sonnet | 2 | `projects/${JERRY_PROJECT}/engagements/{engagement-id}/ux-heart-analyst-{topic-slug}.md` |
| `ux-atomic-architect` | Atomic design component taxonomy architect | T4 | Systematic | Sonnet | 3 | `projects/${JERRY_PROJECT}/engagements/{engagement-id}/ux-atomic-architect-{topic-slug}.md` |
| `ux-inclusive-evaluator` | Inclusive design and accessibility auditor | T4 | Systematic | Sonnet | 3 | `projects/${JERRY_PROJECT}/engagements/{engagement-id}/ux-inclusive-evaluator-{topic-slug}.md` |
| `ux-behavior-diagnostician` | Fogg B=MAP behavior bottleneck diagnosis | T2 | Convergent | Sonnet | 4 | `