ux-research

UX research methodology including persona creation, journey mapping, competitive analysis, and research synthesis. Use when conducting user research, creating personas, mapping user journeys, or analyzing competitors.

Best use case

ux-research is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

UX research methodology including persona creation, journey mapping, competitive analysis, and research synthesis. Use when conducting user research, creating personas, mapping user journeys, or analyzing competitors.

Teams using ux-research should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/ux-research/SKILL.md --create-dirs "https://raw.githubusercontent.com/SufficientDaikon/archon/main/skills/ux-research/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/ux-research/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How ux-research Compares

Feature / Agentux-researchStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

UX research methodology including persona creation, journey mapping, competitive analysis, and research synthesis. Use when conducting user research, creating personas, mapping user journeys, or analyzing competitors.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# UX Research Skill

## Persona Creation Methodology

### Template Structure

```
PERSONA NAME: [Name]
ROLE: [Job title/position]
DEMOGRAPHICS: Age, Location, Education, Tech Comfort Level
BACKGROUND: Brief context about their professional/personal situation

GOALS (≥3):
• Primary Goal: [Most important objective]
• Secondary Goal: [Supporting objective] 
• Tertiary Goal: [Nice-to-have objective]

FRUSTRATIONS (≥3):
• Major Pain Point: [Biggest blocker or annoyance]
• Process Friction: [Workflow or usability issue]
• Resource Constraint: [Time, budget, or skill limitation]

BEHAVIORS:
• Digital Habits: [How they use technology/devices]
• Decision Making: [How they research and decide]
• Communication Style: [Preferred channels and tone]

QUOTE: "[A quote that captures their mindset and priorities]"
```

### Persona Anti-Patterns to Avoid

- **Too Generic**: "Sarah, 25-35, likes technology" - lacks specificity
- **Demographic-Only**: Focusing on age/gender without behavioral insights
- **Assumption-Based**: Creating personas without research data
- **One-Size-Fits-All**: Single persona for diverse user base
- **Stereotype-Driven**: Relying on biased assumptions

### Deriving Personas from Brief

1. **Identify User Segments**: Extract different user types from brief
2. **Map Goals to Segments**: Align business goals with user motivations
3. **Infer Behaviors**: Consider how each segment would interact with product
4. **Create Realistic Context**: Build believable scenarios and constraints
5. **Prioritize Primary Persona**: Focus on most important user segment first

## Journey Mapping Frameworks

### 6-Row Journey Map Structure

```
PERSONA: [Name] | SCENARIO: [Specific use case]

STAGES:        | Discover | Consider | Purchase | Onboard | Use | Support
TOUCHPOINTS:   | [Points of interaction with brand/product]
ACTIONS:       | [What user does at each stage]
THOUGHTS:      | [Internal monologue and considerations]
EMOTIONS:      | [Emotional state: frustrated, hopeful, confused, satisfied]
PAIN POINTS:   | [Specific friction, barriers, or negative moments]
```

### Identifying Stages from Product Brief

1. **Pre-Engagement**: How users become aware (ads, search, referral)
2. **Initial Contact**: First interaction (landing page, sign-up, trial)
3. **Onboarding**: Learning to use the product (tutorials, setup)
4. **Core Usage**: Regular interaction patterns (daily/weekly workflows)
5. **Advancement**: Growing usage (premium features, integrations)
6. **Support/Renewal**: Problem resolution and retention

### Emotion Curve Charting

Plot emotional trajectory across journey stages:
- **High Points**: Moments of delight, achievement, or relief
- **Low Points**: Frustration, confusion, or disappointment
- **Neutral Zones**: Routine or expected interactions
- **Recovery Points**: How negative emotions are addressed

## Competitive Analysis Patterns

### Feature Comparison Matrix Format

```
| Feature Category | Product A | Product B | Product C | Our Product |
|------------------|-----------|-----------|-----------|-------------|
| Core Feature 1   | ✅ Full   | ⚠️ Basic  | ❌ None   | ✅ Full     |
| Core Feature 2   | ⚠️ Basic  | ✅ Full   | ✅ Full   | ✅ Full     |
| Integration      | ❌ None   | ✅ Full   | ⚠️ Basic  | ✅ Full     |
| Mobile App       | ✅ Full   | ✅ Full   | ❌ None   | ⚠️ Basic    |
| Pricing Tier     | $X/month  | $Y/month  | $Z/month  | $A/month    |
```

### UX Audit Framework

**Navigation Clarity** (1-5 scale):
- Menu structure intuitive
- Labels clear and descriptive
- Search functionality accessible
- Breadcrumbs present where needed

**Information Density** (1-5 scale):
- Appropriate white space
- Content hierarchy clear
- No cognitive overload
- Scannable layout

**CTA Effectiveness** (1-5 scale):
- Primary CTAs prominent
- Action-oriented language
- Logical placement
- Visual priority clear

**Mobile Experience** (1-5 scale):
- Responsive design quality
- Touch target sizes
- Mobile-specific features
- Performance on mobile

**Loading Patterns** (1-5 scale):
- Page load speed
- Progressive loading
- Loading state feedback
- Error handling

### Identifying Competitors from Brief

1. **Direct Competitors**: Same solution, same audience
2. **Indirect Competitors**: Different solution, same problem
3. **Substitute Solutions**: Non-digital alternatives
4. **Adjacent Products**: Same audience, different problem
5. **Aspirational Brands**: Different industry, similar UX standards

## Research Synthesis Techniques

### Affinity Mapping Process

1. **Data Collection**: Gather research findings (interviews, surveys, analytics)
2. **Initial Grouping**: Cluster similar insights together
3. **Theme Identification**: Label groups with descriptive headers
4. **Pattern Recognition**: Look for connections between themes
5. **Hierarchy Creation**: Organize themes by importance/frequency

### Insight Prioritization Matrix (Impact × Frequency)

```
HIGH IMPACT + HIGH FREQUENCY = Critical Issues (Fix First)
HIGH IMPACT + LOW FREQUENCY = Important Opportunities 
LOW IMPACT + HIGH FREQUENCY = Quick Wins
LOW IMPACT + LOW FREQUENCY = Backlog Items
```

### Converting Insights to Recommendations

1. **State the Insight**: Clear description of what was learned
2. **Explain the Impact**: Why this matters for users/business
3. **Provide Evidence**: Supporting data or quotes
4. **Recommend Action**: Specific, actionable next step
5. **Success Criteria**: How to measure improvement

### Key Metrics/KPIs Selection

**Awareness Stage**:
- Website traffic sources
- Brand search volume
- Social media engagement

**Consideration Stage**:
- Time on site
- Page views per session
- Content downloads

**Conversion Stage**:
- Conversion rate
- Funnel drop-off points
- Cost per acquisition

**Retention Stage**:
- User activation rate
- Feature adoption
- Customer satisfaction scores

---

## Research Brief Output Template

### Executive Summary
- Project overview and objectives
- Key findings and insights
- Primary recommendations

### Research Objectives
- Business goals
- User questions to answer
- Success metrics

### Methodology
- Research methods used
- Participant criteria
- Timeline and scope

### User Personas
[Insert 2-3 detailed personas using template above]

### User Journey Maps
[Insert journey maps for key user flows]

### Competitive Analysis
[Insert feature comparison matrix and UX audit findings]

### Key Insights
1. **[Insight Category 1]**
   - Finding: [Specific discovery]
   - Evidence: [Supporting data/quotes]
   - Impact: [Effect on user experience]
   - Recommendation: [Specific action]

2. **[Insight Category 2]**
   - Finding: [Specific discovery]
   - Evidence: [Supporting data/quotes]
   - Impact: [Effect on user experience]
   - Recommendation: [Specific action]

3. **[Insight Category 3]**
   - Finding: [Specific discovery]
   - Evidence: [Supporting data/quotes]
   - Impact: [Effect on user experience]
   - Recommendation: [Specific action]

### Priority Matrix
| Insight | Impact | Frequency | Priority | Effort |
|---------|---------|-----------|----------|--------|
| [Item 1] | High | High | Critical | Medium |
| [Item 2] | High | Low | Important | High |
| [Item 3] | Low | High | Quick Win | Low |

### Next Steps
- Immediate actions (0-2 weeks)
- Short-term initiatives (1-3 months)
- Long-term opportunities (3-6 months)

### Appendix
- Raw research data
- Additional personas
- Detailed competitive analysis
- Survey/interview guides used

Related Skills

research-paper-to-course

7
from SufficientDaikon/archon

Transforms academic research papers into interactive single-page HTML courses

YAML Prompt Library

7
from SufficientDaikon/archon

> Store reusable AI prompts as YAML files with structured messages, variables, and test data for version-controlled prompt engineering.

writing-skills

7
from SufficientDaikon/archon

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Writing Plans — TDD-Sized Task Breakdown

7
from SufficientDaikon/archon

> **Type:** Rigid process (follow structure exactly)

wireframing

7
from SufficientDaikon/archon

Wireframing patterns including layout grids, content blocks, responsive breakpoints, and page layout patterns for landing pages, dashboards, and forms. Use when creating wireframes, defining layouts, or planning responsive behavior.

windows-registry-editor

7
from SufficientDaikon/archon

Expert Windows Registry editor and optimizer via PowerShell. Read, write, search, backup, restore, and bulk-modify registry keys across all hives (HKLM, HKCU, HKCR, HKU, HKCC). Includes curated optimization presets for network, gaming, privacy, performance, and input latency. Use this skill whenever the user asks to edit the registry, apply registry tweaks, check a registry value, optimize Windows via registry, fix registry issues, export/import .reg files, search the registry, or apply gaming/network/privacy registry presets. Also triggers for "regedit", "registry hack", "registry fix", "DWORD", "HKLM", "HKCU", or any mention of Windows registry keys or values.

windows-network-optimizer

7
from SufficientDaikon/archon

Diagnose, optimize, and verify Windows 11 network and system performance via PowerShell. Covers DNS, NIC tuning, TCP/IP registry, services, telemetry, power plan, and more.

windows-error-debugger

7
from SufficientDaikon/archon

Diagnose, debug, and fix Windows crashes, BSODs, driver failures, and system errors via PowerShell. Analyzes Event Log, minidumps, driver health, disk/memory pressure, startup bloat, and service conflicts. Builds a growing knowledge base of resolved issues per machine. Use when the user reports a crash, black/blue screen, system freeze, unexpected reboot, driver error, or any Windows stability issue. Also triggers for "BSOD", "blue screen", "black screen", "crash", "system error", "bugcheck", "minidump", "driver failure", "unexpected shutdown", "paging file too small", "system hang", "Windows froze", "PC crashed", "kernel error", or any mention of Windows Event Log errors.

White-Label Config

7
from SufficientDaikon/archon

> Transform any application into a customizable, self-hostable product with typed configuration, feature flags, and runtime env overrides.

webapp-testing

7
from SufficientDaikon/archon

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

web-design-guidelines

7
from SufficientDaikon/archon

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

Vitest Unit Patterns

7
from SufficientDaikon/archon

> Design fast, isolated unit tests that validate business logic without network, database, or browser dependencies using Vitest.