ux-researcher-designerUX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis. Use for user research, persona creation, journey mapping, and design validation.
Install via ClawdBot CLI:
clawdbot install alirezarezvani/ux-researcher-designerGenerate user personas from research data, create journey maps, plan usability tests, and synthesize research findings into actionable design recommendations.
Use this skill when you need to:
Situation: You have user data (analytics, surveys, interviews) and need to create a research-backed persona.
Steps:
Required format (JSON):
[
{
"user_id": "user_1",
"age": 32,
"usage_frequency": "daily",
"features_used": ["dashboard", "reports", "export"],
"primary_device": "desktop",
"usage_context": "work",
"tech_proficiency": 7,
"pain_points": ["slow loading", "confusing UI"]
}
]
# Human-readable output
python scripts/persona_generator.py
# JSON output for integration
python scripts/persona_generator.py json
| Component | What to Check |
|-----------|---------------|
| Archetype | Does it match the data patterns? |
| Demographics | Are they derived from actual data? |
| Goals | Are they specific and actionable? |
| Frustrations | Do they include frequency counts? |
| Design implications | Can designers act on these? |
references/persona-methodology.md for validity criteriaSituation: You need to visualize the end-to-end user experience for a specific goal.
Steps:
| Element | Description |
|---------|-------------|
| Persona | Which user type |
| Goal | What they're trying to achieve |
| Start | Trigger that begins journey |
| End | Success criteria |
| Timeframe | Hours/days/weeks |
Sources:
Typical B2B SaaS stages:
Awareness ā Evaluation ā Onboarding ā Adoption ā Advocacy
Stage: [Name]
āāā Actions: What does user do?
āāā Touchpoints: Where do they interact?
āāā Emotions: How do they feel? (1-5)
āāā Pain Points: What frustrates them?
āāā Opportunities: Where can we improve?
Priority Score = Frequency Ć Severity Ć Solvability
references/journey-mapping-guide.md for templatesSituation: You need to validate a design with real users.
Steps:
Transform vague goals into testable questions:
| Vague | Testable |
|-------|----------|
| "Is it easy to use?" | "Can users complete checkout in <3 min?" |
| "Do users like it?" | "Will users choose Design A or B?" |
| "Does it make sense?" | "Can users find settings without hints?" |
| Method | Participants | Duration | Best For |
|--------|--------------|----------|----------|
| Moderated remote | 5-8 | 45-60 min | Deep insights |
| Unmoderated remote | 10-20 | 15-20 min | Quick validation |
| Guerrilla | 3-5 | 5-10 min | Rapid feedback |
Good task format:
SCENARIO: "Imagine you're planning a trip to Paris..."
GOAL: "Book a hotel for 3 nights in your budget."
SUCCESS: "You see the confirmation page."
Task progression: Warm-up ā Core ā Secondary ā Edge case ā Free exploration
| Metric | Target |
|--------|--------|
| Completion rate | >80% |
| Time on task | <2Ć expected |
| Error rate | <15% |
| Satisfaction | >4/5 |
references/usability-testing-frameworks.md for full guideSituation: You have raw research data (interviews, surveys, observations) and need actionable insights.
Steps:
Tag each data point:
[GOAL] - What they want to achieve[PAIN] - What frustrates them[BEHAVIOR] - What they actually do[CONTEXT] - When/where they use product[QUOTE] - Direct user words
User A: Uses daily, advanced features, shortcuts
User B: Uses daily, complex workflows, automation
User C: Uses weekly, basic needs, occasional
Cluster 1: A, B (Power Users)
Cluster 2: C (Casual User)
| Cluster | Users | % | Viability |
|---------|-------|---|-----------|
| Power Users | 18 | 36% | Primary persona |
| Business Users | 15 | 30% | Primary persona |
| Casual Users | 12 | 24% | Secondary persona |
For each theme:
| Factor | Score 1-5 |
|--------|-----------|
| Frequency | How often does this occur? |
| Severity | How much does it hurt? |
| Breadth | How many users affected? |
| Solvability | Can we fix this? |
references/persona-methodology.md for analysis frameworkGenerates data-driven personas from user research data.
| Argument | Values | Default | Description |
|----------|--------|---------|-------------|
| format | (none), json | (none) | Output format |
Sample Output:
============================================================
PERSONA: Alex the Power User
============================================================
š A daily user who primarily uses the product for work purposes
Archetype: Power User
Quote: "I need tools that can keep up with my workflow"
š¤ Demographics:
⢠Age Range: 25-34
⢠Location Type: Urban
⢠Tech Proficiency: Advanced
šÆ Goals & Needs:
⢠Complete tasks efficiently
⢠Automate workflows
⢠Access advanced features
š¤ Frustrations:
⢠Slow loading times (14/20 users)
⢠No keyboard shortcuts
⢠Limited API access
š” Design Implications:
ā Optimize for speed and efficiency
ā Provide keyboard shortcuts and power features
ā Expose API and automation capabilities
š Data: Based on 45 users
Confidence: High
Archetypes Generated:
| Archetype | Signals | Design Focus |
|-----------|---------|--------------|
| power_user | Daily use, 10+ features | Efficiency, customization |
| casual_user | Weekly use, 3-5 features | Simplicity, guidance |
| business_user | Work context, team use | Collaboration, reporting |
| mobile_first | Mobile primary | Touch, offline, speed |
Output Components:
| Component | Description |
|-----------|-------------|
| demographics | Age range, location, occupation, tech level |
| psychographics | Motivations, values, attitudes, lifestyle |
| behaviors | Usage patterns, feature preferences |
| needs_and_goals | Primary, secondary, functional, emotional |
| frustrations | Pain points with evidence |
| scenarios | Contextual usage stories |
| design_implications | Actionable recommendations |
| data_points | Sample size, confidence level |
| Question Type | Best Method | Sample Size |
|---------------|-------------|-------------|
| "What do users do?" | Analytics, observation | 100+ events |
| "Why do they do it?" | Interviews | 8-15 users |
| "How well can they do it?" | Usability test | 5-8 users |
| "What do they prefer?" | Survey, A/B test | 50+ users |
| "What do they feel?" | Diary study, interviews | 10-15 users |
| Sample Size | Confidence | Use Case |
|-------------|------------|----------|
| 5-10 users | Low | Exploratory |
| 11-30 users | Medium | Directional |
| 31+ users | High | Production |
| Severity | Definition | Action |
|----------|------------|--------|
| 4 - Critical | Prevents task completion | Fix immediately |
| 3 - Major | Significant difficulty | Fix before release |
| 2 - Minor | Causes hesitation | Fix when possible |
| 1 - Cosmetic | Noticed but not problematic | Low priority |
| Type | Example | Use For |
|------|---------|---------|
| Context | "Walk me through your typical day" | Understanding environment |
| Behavior | "Show me how you do X" | Observing actual actions |
| Goals | "What are you trying to achieve?" | Uncovering motivations |
| Pain | "What's the hardest part?" | Identifying frustrations |
| Reflection | "What would you change?" | Generating ideas |
Detailed reference guides in references/:
| File | Content |
|------|---------|
| persona-methodology.md | Validity criteria, data collection, analysis framework |
| journey-mapping-guide.md | Mapping process, templates, opportunity identification |
| example-personas.md | 3 complete persona examples with data |
| usability-testing-frameworks.md | Test planning, task design, analysis |
Generated Mar 1, 2026
An online retailer wants to create detailed user personas based on analytics and survey data to tailor marketing campaigns and improve website navigation. This involves analyzing customer demographics, purchase behaviors, and pain points to generate actionable personas for design teams.
A healthcare startup needs to map the patient journey for a new telemedicine app, from appointment scheduling to follow-up care. This includes gathering data from user interviews and session recordings to identify emotional highs and lows, touchpoints, and opportunities for enhancing user experience.
A B2B software company plans to validate a redesigned dashboard interface with real users through moderated remote tests. The goal is to assess task completion rates, time on task, and user satisfaction to ensure the design meets usability standards before launch.
A bank collects raw data from customer interviews and support tickets to synthesize insights for improving its mobile banking app. This involves coding data points, clustering patterns, and deriving actionable recommendations to address common pain points like navigation issues or transaction errors.
Companies offer this skill as part of a monthly or annual subscription for UX design tools, providing continuous access to persona generators, journey mapping templates, and usability testing frameworks. Revenue is generated through tiered pricing plans based on features and user seats.
UX agencies or freelancers use this skill to deliver custom research and design projects for clients, charging per project or hourly rates. It helps in creating tailored personas, journey maps, and test plans, with revenue coming from service fees and retainer agreements.
Large organizations license this skill for internal teams to conduct in-house UX research and design, often integrated with existing product development workflows. Revenue is generated through one-time or annual licensing fees, with support and updates included.
š¬ Integration Tip
Integrate this skill with analytics platforms and project management tools to streamline data input and output sharing, ensuring seamless workflow automation.
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Search and analyze your own session logs (older/parent conversations) using jq.
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linking related objects, enforcing constraints, planning multi-step actions as graph transformations, or when skills need to share state. Trigger on "remember", "what do I know about", "link X to Y", "show dependencies", entity CRUD, or cross-skill data access.
Ultimate AI agent memory system for Cursor, Claude, ChatGPT & Copilot. WAL protocol + vector search + git-notes + cloud backup. Never lose context again. Vibe-coding ready.
Headless browser automation CLI optimized for AI agents with accessibility tree snapshots and ref-based element selection