ux-researcher-designer
UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis. Use when conducting user research, creating personas, mapping user journeys, planning usability tests, or validating designs.
- License 许可
- MIT
- 最近更新
- 2026-08-16
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- ux-researcher-designer
- description
- UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis. Use when conducting user research, creating personas, mapping user journeys, planning usability tests, or validating designs.
02 资源文件 6
- 资产文件assets/research_plan_template.md4.7 KB
- 参考文档references/example-personas.md11.7 KB
- 参考文档references/journey-mapping-guide.md17.7 KB
- 参考文档references/persona-methodology.md11.4 KB
- 参考文档references/usability-testing-frameworks.md11.7 KB
- 脚本scripts/persona_generator.py24.0 KB
03 SKILL.md 正文
UX Researcher & Designer
Generate user personas from research data, create journey maps, plan usability tests, and synthesize research findings into actionable design recommendations.
Table of Contents
Trigger Terms
Use this skill when you need to:
- "create user persona"
- "generate persona from data"
- "build customer journey map"
- "map user journey"
- "plan usability test"
- "design usability study"
- "analyze user research"
- "synthesize interview findings"
- "identify user pain points"
- "define user archetypes"
- "calculate research sample size"
- "create empathy map"
- "identify user needs"
Workflows
Workflow 1: Generate User Persona
Situation: You have user data (analytics, surveys, interviews) and need to create a research-backed persona.
Steps:
-
Prepare user data
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"] } ] -
Run persona generator
# Human-readable output python scripts/persona_generator.py # JSON output for integration python scripts/persona_generator.py json -
Review generated components
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? -
Validate persona
- Show to 3-5 real users: "Does this sound like you?"
- Cross-check with support tickets
- Verify against analytics data
-
Reference: See
references/persona-methodology.mdfor validity criteria
Workflow 2: Create Journey Map
Situation: You need to visualize the end-to-end user experience for a specific goal.
Steps:
-
Define scope
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 -
Gather journey data
Sources:
- User interviews (ask "walk me through...")
- Session recordings
- Analytics (funnel, drop-offs)
- Support tickets
-
Map the stages
Typical B2B SaaS stages:
Awareness → Evaluation → Onboarding → Adoption → Advocacy -
Fill in layers for each stage
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? -
Identify opportunities
Priority Score = Frequency × Severity × Solvability
-
Reference: See
references/journey-mapping-guide.mdfor templates
Workflow 3: Plan Usability Test
Situation: You need to validate a design with real users.
Steps:
-
Define research questions
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?" -
Select method
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 -
Design tasks
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
-
Define success metrics
Metric Target Completion rate >80% Time on task <2× expected Error rate <15% Satisfaction >4/5 -
Prepare moderator guide
- Think-aloud instructions
- Non-leading prompts
- Post-task questions
-
Reference: See
references/usability-testing-frameworks.mdfor full guide
Workflow 4: Synthesize Research
Situation: You have raw research data (interviews, surveys, observations) and need actionable insights.
Steps:
-
Code the data
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
-
Cluster similar patterns
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) -
Calculate segment sizes
Cluster Users % Viability Power Users 18 36% Primary persona Business Users 15 30% Primary persona Casual Users 12 24% Secondary persona -
Extract key findings
For each theme:
- Finding statement
- Supporting evidence (quotes, data)
- Frequency (X/Y participants)
- Business impact
- Recommendation
-
Prioritize opportunities
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? -
Reference: See
references/persona-methodology.mdfor analysis framework
Tool Reference
persona_generator.py
Generates 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 |
Quick Reference Tables
Research Method Selection
| 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 |
Persona Confidence Levels
| Sample Size | Confidence | Use Case |
|---|---|---|
| 5-10 users | Low | Exploratory |
| 11-30 users | Medium | Directional |
| 31+ users | High | Production |
Usability Issue Severity
| 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 |
Interview Question Types
| 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 |
Knowledge Base
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 |
Validation Checklist
Persona Quality
- [ ] Based on 20+ users (minimum)
- [ ] At least 2 data sources (quant + qual)
- [ ] Specific, actionable goals
- [ ] Frustrations include frequency counts
- [ ] Design implications are specific
- [ ] Confidence level stated
Journey Map Quality
- [ ] Scope clearly defined (persona, goal, timeframe)
- [ ] Based on real user data, not assumptions
- [ ] All layers filled (actions, touchpoints, emotions)
- [ ] Pain points identified per stage
- [ ] Opportunities prioritized
Usability Test Quality
- [ ] Research questions are testable
- [ ] Tasks are realistic scenarios, not instructions
- [ ] 5+ participants per design
- [ ] Success metrics defined
- [ ] Findings include severity ratings
Research Synthesis Quality
- [ ] Data coded consistently
- [ ] Patterns based on 3+ data points
- [ ] Findings include evidence
- [ ] Recommendations are actionable
- [ ] Priorities justified
Related Skills
- UI Design System (
product-team/ui-design-system/) — Research findings inform design system decisions - Product Manager Toolkit (
product-team/product-manager-toolkit/) — Customer interview analysis complements persona research
04 同仓库更多 Skills
syllabus
Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.
research
Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., "research [topic]", "look into [topic]", "what do we know about [topic]", "investigate [topic]", "find me information on [topic]", "do some research on [topic]", "I need to understand [topic]"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.
pulse
Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.
patent
Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.
notebooklm
Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio/Video Overviews, Mind Maps, Reports incl. Briefing Doc/Study Guide/FAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.
litreview
Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed/OpenAlex (or Consensus) query.