Skip to main content
skill CX Codex

product-ux-expert — Claude Code skill: what it does, how to install

product-ux-expert — a skill for reviewing interfaces against Nielsen's heuristics, building user journey maps, and auditing accessibility against WCAG 2.2 AA.

MIT 212 installs ★ 300 updated 2026-10-23

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add majiayu000/spellbook --skill product-ux-expert -a claude-code
Open on GitHub

What product-ux-expert does

Includes a reference for Nielsen's 10 heuristics, cognitive psychology laws (Hick, Miller, Fitts), Gestalt principles, and an evaluation template with severity ratings from 0 to 4. The skill provides a journey map structure (stages, touchpoints, emotions, pain points), a POUR accessibility checklist, and WCAG 2.2 updates: minimum tap target size of 24×24 pixels, visible focus indicator at least 2 pixels wide, alternatives to drag-and-drop.

The agent applies heuristics to screens, rates issue severity, builds journey maps from awareness to advocacy, and checks contrast, keyboard navigation, and ARIA markup. Full accessibility validation still requires manual testing with screen readers.

What it helps with

  • evaluate an interface against Nielsen's heuristics and prioritize fixes
  • build a user journey map with emotions and drop-off points
  • audit an interface for WCAG 2.2 AA compliance and identify violations
  • apply Hick's and Miller's laws to reduce cognitive load
  • design a user journey with touchpoints and pain points

Example prompts for the agent

  • Review the dashboard against Nielsen's heuristics and rate the severity of issues found
  • Build a user journey map for signup and checkout with stages and emotions
  • Check the order form for WCAG 2.2 AA compliance: contrast, tap target sizes, and keyboard navigation

How to install product-ux-expert

1Skills CLI (Vercel)

npx skills add majiayu000/spellbook --skill product-ux-expert -a claude-code

2Manually: put the files in place

~/.claude/skills/product-ux-expert/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/product-ux-expert/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about product-ux-expert

How to install product-ux-expert in Claude Code?

Run npx skills add majiayu000/spellbook --skill product-ux-expert -a claude-code. The skill will be written to ~/.claude/skills/product-ux-expert/SKILL.md.

What does product-ux-expert do?

Gives the agent a reference for usability heuristics, cognitive psychology laws, Gestalt principles, and WCAG 2.2 requirements. The skill applies this knowledge to interface reviews, user journey mapping, and accessibility audits.

Which WCAG 2.2 requirements does the skill check?

Minimum tap target size of 24×24 pixels, visible focus outline at least 2 pixels wide, alternatives to drag-and-drop, 4.5:1 contrast, keyboard navigation, and ARIA markup. Full validation requires manual testing with screen readers.

Source text

SKILL.md · MIT
---
name: product-ux-expert
description: Product interaction and UX expert. Use when reviewing UI/UX, conducting heuristic evaluations, designing user journeys, applying cognitive psychology principles, or ensuring WCAG 2.2 accessibility compliance.
---
# Product UX Expert

## Core Principles

- **Reduce Cognitive Load** — Minimize mental effort required for every interaction
- **Accessibility First** — WCAG 2.2 AA is the baseline, not an afterthought
- **Evidence-Based** — Decisions backed by user research, not assumptions
- **Anticipatory Design** — Predict user needs before they ask
- **Ethical Design** — No dark patterns, transparent data practices
- **Mobile First** — Design for smallest screens, enhance for larger

---

## Quick Reference

### Nielsen's 10 Heuristics

| # | Heuristic | Key Question |
|---|-----------|--------------|
| 1 | Visibility of System Status | Does the user always know what's happening? |
| 2 | Match System & Real World | Does it use familiar language and concepts? |
| 3 | User Control & Freedom | Can users easily undo or exit? |
| 4 | Consistency & Standards | Does it follow platform conventions? |
| 5 | Error Prevention | Does it prevent errors before they occur? |
| 6 | Recognition over Recall | Is information visible, not memorized? |
| 7 | Flexibility & Efficiency | Are there shortcuts for experts? |
| 8 | Aesthetic & Minimalist Design | Is every element necessary? |
| 9 | Help Users with Errors | Are error messages helpful and actionable? |
| 10 | Help & Documentation | Is help available when needed? |

---

## Cognitive Psychology

### Cognitive Load Types

```
Intrinsic Load     — Complexity inherent to the task itself
Extraneous Load    — Unnecessary complexity from poor design (eliminate this!)
Germane Load       — Mental effort for learning/understanding (support this)
```

### Key Laws

```
Hick's Law         — More choices = longer decision time
                   → Limit options to 5-7, use progressive disclosure

Miller's Law       — Working memory holds 7±2 items
                   → Chunk information, use visual grouping

Fitts's Law        — Larger, closer targets are easier to click
                   → Make primary actions big and accessible

Jakob's Law        — Users expect your site to work like others
                   → Follow established patterns

Von Restorff       — Different items are more memorable
                   → Highlight CTAs with contrast

Serial Position    — First and last items remembered best
                   → Put key info at start/end of lists
```

### Gestalt Principles

```
Proximity          — Close elements are perceived as groups
Similarity         — Similar elements are perceived as related
Continuity         — Eyes follow smooth lines and curves
Closure            — Mind completes incomplete shapes
Figure-Ground      — Elements seen as foreground or background
Common Region      — Elements in same area are grouped
```

---

## Heuristic Evaluation

### Process

```
1. Define scope         — What screens/flows to evaluate
2. Select evaluators    — 3-5 UX experts (80%+ issues found)
3. Independent review   — Each expert reviews alone
4. Apply heuristics     — Rate severity for each issue
5. Consolidate          — Merge findings, remove duplicates
6. Prioritize           — Rank by severity × frequency
7. Report               — Actionable recommendations
```

### Severity Rating

| Level | Severity | Description |
|-------|----------|-------------|
| 0 | Not a problem | Evaluator disagrees it's an issue |
| 1 | Cosmetic | Fix only if extra time available |
| 2 | Minor | Low priority, causes friction |
| 3 | Major | High priority, significant impact |
| 4 | Catastrophic | Must fix before release |

### Issue Template

```markdown
## Issue: [Brief Description]

**Heuristic:** #N - Name
**Severity:** 0-4
**Location:** Screen / Component / Flow

**Problem:**
What's wrong and why it matters to users.

**Evidence:**
Screenshot or recording link.

**Recommendation:**
Specific fix with before/after comparison.
```

---

## User Journey Mapping

### Journey Map Structure

```
┌─────────────────────────────────────────────────────────────────┐
│  PERSONA: [Name, Goals, Context]                                │
├─────────┬─────────┬─────────┬─────────┬─────────┬──────────────┤
│ Stage   │ Aware   │ Consider│ Purchase│ Use     │ Advocate     │
├─────────┼─────────┼─────────┼─────────┼─────────┼──────────────┤
│ Actions │ Search  │ Compare │ Signup  │ Onboard │ Share/Review │
├─────────┼─────────┼─────────┼─────────┼─────────┼──────────────┤
│ Touch-  │ Search  │ Website │ Checkout│ App     │ Social       │
│ points  │ Ads     │ Reviews │ Email   │ Support │ Email        │
├─────────┼─────────┼─────────┼─────────┼─────────┼──────────────┤
│ Emotions│   😐    │   🤔    │   😟    │   😊    │    😍        │
│         │ curious │ hopeful │ anxious │ relieved│  delighted   │
├─────────┼─────────┼─────────┼─────────┼─────────┼──────────────┤
│ Pain    │ Too many│ Info    │ Complex │ Unclear │ No referral  │
│ Points  │ options │ overload│ forms   │ next    │ program      │
├─────────┼─────────┼─────────┼─────────┼─────────┼──────────────┤
│ Opportu-│ Clear   │ Compare │ 1-click │ Progress│ Share        │
│ nities  │ tagline │ table   │ signup  │ tracker │ incentive    │
└─────────┴─────────┴─────────┴─────────┴─────────┴──────────────┘
```

### Touchpoint Analysis

```
For each touchpoint, evaluate:

1. Entry Point      — How do users arrive?
2. User Goal        — What are they trying to accomplish?
3. Friction         — What slows them down?
4. Emotion          — How do they feel?
5. Drop-off Risk    — Where might they abandon?
6. Opportunity      — How can we improve?
```

---

## Accessibility (WCAG 2.2 AA)

### POUR Principles

```
Perceivable     — Can users perceive the content?
                  ✓ Text alternatives for images
                  ✓ Captions for video
                  ✓ 4.5:1 color contrast
                  ✓ Resizable text (up to 200%)

Operable        — Can users operate the interface?
                  ✓ Keyboard accessible
                  ✓ No keyboard traps
                  ✓ Skip navigation links
                  ✓ Sufficient time limits
                  ✓ Focus visible (new in 2.2!)

Understandable  — Can users understand the content?
                  ✓ Language declared
                  ✓ Consistent navigation
                  ✓ Error identification
                  ✓ Labels and instructions

Robust          — Works with assistive technology?
                  ✓ Valid HTML
                  ✓ ARIA landmarks
                  ✓ Status messages announced
```

### New in WCAG 2.2 (2023-2025)

```
Focus Not Obscured (AA)      — Focused element not fully hidden
Focus Appearance (AA)        — Visible focus indicator (2px outline)
Dragging Movements (AA)      — Alternatives to drag-and-drop
Target Size (AA)             — Minimum 24×24 CSS pixels
Consistent Help (A)          — Help mechanisms in consistent locations
Redundant Entry (A)          — Don't ask for same info twice
Accessible Authentication (A) — No cognitive function tests for login
```

### Quick Checklist

```markdown
## Accessibility Check

### Perceivable
- [ ] All images have meaningful alt text
- [ ] Videos have captions and transcripts
- [ ] Color contrast ratio ≥ 4.5:1 (text), ≥ 3:1 (large text)
- [ ] Information not conveyed by color alone
- [ ] Text can be resized to 200% without loss

### Operable
- [ ] All functionality available via keyboard
- [ ] Focus order is logical
- [ ] Focus indicator is visible (2px outline minimum)
- [ ] No keyboard traps
- [ ] Skip links provided
- [ ] Touch targets ≥ 24×24px

### Understandable
- [ ] Page language declared
- [ ] Consistent navigation across pages
- [ ] Form errors clearly identified
- [ ] Labels associated with inputs

### Robust
- [ ] Valid HTML (no duplicate IDs)
- [ ] ARIA roles used correctly
- [ ] Works with screen readers (NVDA/VoiceOver)
```

---

## Interaction Patterns

### Micro-interactions

```
Purpose of micro-interactions:
1. Feedback      — Confirm user action (button click, form submit)
2. Status        — Show current state (loading, progress)
3. Guidance      — Direct attention (onboarding tooltips)
4. Delight       — Create emotional connection (subtle animations)

Best Practices:
✓ Keep animations under 300ms
✓ Use easing (ease-out for exits, ease-in for entries)
✓ Respect prefers-reduced-motion
✓ Animate properties that don't trigger layout (transform, opacity)
```

### Motion Design Principles

```
Duration Scale:
- Micro (fade, state change)     →  100-200ms
- Small (dropdown, tooltip)      →  200-300ms
- Medium (modal, sidebar)        →  300-400ms
- Large (page transition)        →  400-500ms

Easing:
- ease-out    → Elements entering (decelerate into view)
- ease-in     → Elements exiting (accelerate out of view)
- ease-in-out → Elements moving (natural feel)
```

### Form Design

```
✓ One column layout (no side-by-side inputs)
✓ Labels above inputs (not placeholder-only)
✓ Group related fields visually
✓ Inline validation (after field blur)
✓ Clear error messages with solutions
✓ Show password option
✓ Autofill support (autocomplete attributes)
✓ Smart defaults based on context
```

---

## Design System Integration

### Component States

```
Every interactive component needs:

Default         — Normal resting state
Hover           — Mouse over (desktop)
Focus           — Keyboard focus (visible ring)
Active          — Being pressed/clicked
Disabled        — Not currently available
Loading         — Processing action
Error           — Validation failed
Success         — Action completed
```

### Design Tokens

```json
{
  "color": {
    "text": {
      "primary": "#1a1a1a",
      "secondary": "#6b6b6b",
      "disabled": "#a3a3a3",
      "inverse": "#ffffff"
    },
    "interactive": {
      "default": "#0066cc",
      "hover": "#0052a3",
      "active": "#003d7a",
      "focus": "#0066cc"
    },
    "feedback": {
      "error": "#d32f2f",
      "warning": "#f57c00",
      "success": "#388e3c",
      "info": "#1976d2"
    }
  },
  "spacing": {
    "xs": "4px",
    "sm": "8px",
    "md": "16px",
    "lg": "24px",
    "xl": "32px"
  },
  "radius": {
    "sm": "4px",
    "md": "8px",
    "lg": "16px",
    "full": "9999px"
  }
}
```

---

## 2025 UX Trends

### AI-Driven Personalization

```
✓ Adaptive interfaces based on user behavior
✓ Predictive content suggestions
✓ Context-aware personalization
✓ Real-time UI adjustments

⚠️ Always provide transparency and user control
⚠️ Respect privacy, use on-device processing when possible
```

### Anticipatory Design

```
Design that:
- Predicts user needs before they ask
- Reduces decision fatigue with smart defaults
- Automates repetitive tasks
- Surfaces relevant information proactively

Example: Pre-filling shipping address based on previous orders
```

### Ethical Design Practices

```
DO:
✓ Clear consent for data collection
✓ Easy-to-find privacy settings
✓ Honest product representations
✓ Sustainable design (reduce digital carbon)

DON'T (Dark Patterns):
✗ Confirmshaming ("No, I don't want to save money")
✗ Hidden costs
✗ Trick questions
✗ Forced continuity (hard-to-cancel subscriptions)
✗ Misdirection
✗ Roach motels (easy in, hard out)
```

---

## Evaluation Template

```markdown
# UX Evaluation Report

## Overview
- **Product:** [Name]
- **Scope:** [Screens/Flows evaluated]
- **Date:** [Date]
- **Evaluators:** [Names]

## Executive Summary
[2-3 sentences on overall UX health and critical findings]

## Methodology
- Nielsen's 10 Heuristics
- WCAG 2.2 AA Compliance Check
- Cognitive Load Analysis

## Findings by Severity

### Catastrophic (Severity 4)
[Issues that must be fixed immediately]

### Major (Severity 3)
[High priority issues]

### Minor (Severity 2)
[Low priority improvements]

## Accessibility Status
- [ ] WCAG 2.2 A Compliance
- [ ] WCAG 2.2 AA Compliance
- [ ] Screen Reader Compatible
- [ ] Keyboard Navigation Complete

## Recommendations
[Prioritized action items with effort estimates]

## Appendix
- Screenshot evidence
- User testing video clips
- Competitive analysis
```

---

## See Also

- [reference/heuristics.md](reference/heuristics.md) — Detailed heuristic examples
- [reference/accessibility.md](reference/accessibility.md) — Full WCAG 2.2 checklist
- [reference/psychology.md](reference/psychology.md) — Cognitive psychology deep dive
- [reference/journey-mapping.md](reference/journey-mapping.md) — Journey mapping templates

© majiayu000 · MIT · majiayu000/spellbook

Similar skills

All skills for Design →

From the same set13

The whole set →
app-ui-design app-ui-design — a skill for designing iOS and Android interfaces: design systems, accessibility, platform guidelines. Useful when the agent lays out screens or checks contrast. CX Codex +1 652installs harmonyos-app harmonyos-app provides rules and patterns for building HarmonyOS NEXT apps with ArkTS and ArkUI. Guides agents on strict typing and immutable state updates under Stage model. CX Codex +1 502installs product-discovery A product discovery skill that keeps your agent honest: problem first, evidence over opinion, and frameworks like JTBD, Kano and Value Proposition Canvas. CX Codex +1 383installs technical-spec technical-spec enforces strict structures for technical design docs, RFCs, and ADRs with mandatory alternatives, diagrams, and risk matrices. CX Codex +1 245installs prd-master prd-master is a skill for writing product specifications, user stories, and acceptance criteria. It structures requirements with RICE and MoSCoW and sets measurable goals. CX Codex +1 166installs observability-sre The observability-sre skill guides monitoring, SLO design, tracing, logging, and incident response. Use it when a project needs Prometheus, Grafana, or OpenTelemetry practices. CX Codex +1 165installs database-patterns database-patterns guides AI agents on pairing PostgreSQL with Redis: schema types, indexing, JSONB usage, caching strategies, and stampede prevention. CX Codex +1 162installs clash-doctor clash-doctor diagnoses Clash Verge and mihomo connectivity, routes AI traffic, and manages TUN bypass rules directly from your agent. CX Codex +1 142installs

Project sponsors

Companies that keep this analytics open