Refactor high-complexity React components in Dify frontend. Use when `pnpm analyze-component...
npx skills add majiayu000/claude-arsenal --skill "product-ux-expert"
Install specific skill from multi-skill repository
# 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.
# 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
| # | 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
## 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"
}
}
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
# 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 β Detailed heuristic examples
- reference/accessibility.md β Full WCAG 2.2 checklist
- reference/psychology.md β Cognitive psychology deep dive
- reference/journey-mapping.md β Journey mapping templates
# Supported AI Coding Agents
This skill is compatible with the SKILL.md standard and works with all major AI coding agents:
Learn more about the SKILL.md standard and how to use these skills with your preferred AI coding agent.