โ† Back to list
majiayu000

product-ux-expert

by majiayu000

๐Ÿš€ 39+ battle-tested Claude Code skills & 9 specialized agents for professional software development. The most comprehensive skill library for Claude Code.

โญ 2๐Ÿด 1๐Ÿ“… Jan 25, 2026

SKILL.md


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

#HeuristicKey Question
1Visibility of System StatusDoes the user always know what's happening?
2Match System & Real WorldDoes it use familiar language and concepts?
3User Control & FreedomCan users easily undo or exit?
4Consistency & StandardsDoes it follow platform conventions?
5Error PreventionDoes it prevent errors before they occur?
6Recognition over RecallIs information visible, not memorized?
7Flexibility & EfficiencyAre there shortcuts for experts?
8Aesthetic & Minimalist DesignIs every element necessary?
9Help Users with ErrorsAre error messages helpful and actionable?
10Help & DocumentationIs 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

LevelSeverityDescription
0Not a problemEvaluator disagrees it's an issue
1CosmeticFix only if extra time available
2MinorLow priority, causes friction
3MajorHigh priority, significant impact
4CatastrophicMust fix before release

Issue Template

## 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

## 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

{
  "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"
  }
}

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

# 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

Score

Total Score

75/100

Based on repository quality metrics

โœ“SKILL.md

SKILL.mdใƒ•ใ‚กใ‚คใƒซใŒๅซใพใ‚Œใฆใ„ใ‚‹

+20
โœ“LICENSE

ใƒฉใ‚คใ‚ปใƒณใ‚นใŒ่จญๅฎšใ•ใ‚Œใฆใ„ใ‚‹

+10
โœ“่ชฌๆ˜Žๆ–‡

100ๆ–‡ๅญ—ไปฅไธŠใฎ่ชฌๆ˜ŽใŒใ‚ใ‚‹

+10
โ—‹ไบบๆฐ—

GitHub Stars 100ไปฅไธŠ

0/15
โœ“ๆœ€่ฟ‘ใฎๆดปๅ‹•

1ใƒถๆœˆไปฅๅ†…ใซๆ›ดๆ–ฐ

+10
โ—‹ใƒ•ใ‚ฉใƒผใ‚ฏ

10ๅ›žไปฅไธŠใƒ•ใ‚ฉใƒผใ‚ฏใ•ใ‚Œใฆใ„ใ‚‹

0/5
โœ“Issue็ฎก็†

ใ‚ชใƒผใƒ—ใƒณIssueใŒ50ๆœชๆบ€

+5
โœ“่จ€่ชž

ใƒ—ใƒญใ‚ฐใƒฉใƒŸใƒณใ‚ฐ่จ€่ชžใŒ่จญๅฎšใ•ใ‚Œใฆใ„ใ‚‹

+5
โœ“ใ‚ฟใ‚ฐ

1ใคไปฅไธŠใฎใ‚ฟใ‚ฐใŒ่จญๅฎšใ•ใ‚Œใฆใ„ใ‚‹

+5

Reviews

๐Ÿ’ฌ

Reviews coming soon