[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KBXG1AJREQ1SY33ZWEHM87":3,"skill-same:01M6KBXG1AJREQ1SY33ZWEHM87":109},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":6,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":6,"updatedAt":64,"install":65,"resources":78},"01M6KBXG1AJREQ1SY33ZWEHM87","ux-researcher-designer",null,"UX research and design toolkit for Senior UX Designer\u002FResearcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis. Use for user research, persona creation, journey mapping, and design validation.","afaizalam2003\u002FMaster-claude-skill","afaizalam2003","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222019359?v=4","01M6K8F2XNT0HKBPF00JQ78SV3","Faiz Alam","01M6K8F31EBXAPER0EG8R9HTR5",3,"MIT","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fux-researcher-designer\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"ux","ux researcher","ux researcher designer","designer","researcher","usability","data-driven","for","mapping","user research","creation","journey mapping","journey","frameworks","testing","use","persona","data","toolkit","design","2026-11-10 10:12:30",false,"---\nname: \"ux-researcher-designer\"\ndescription: UX research and design toolkit for Senior UX Designer\u002FResearcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis. Use for user research, persona creation, journey mapping, and design validation.\n---\n\n# UX Researcher & Designer\n\nGenerate user personas from research data, create journey maps, plan usability tests, and synthesize research findings into actionable design recommendations.\n\n---\n\n## Table of Contents\n\n- [Trigger Terms](#trigger-terms)\n- [Workflows](#workflows)\n  - [Workflow 1: Generate User Persona](#workflow-1-generate-user-persona)\n  - [Workflow 2: Create Journey Map](#workflow-2-create-journey-map)\n  - [Workflow 3: Plan Usability Test](#workflow-3-plan-usability-test)\n  - [Workflow 4: Synthesize Research](#workflow-4-synthesize-research)\n- [Tool Reference](#tool-reference)\n- [Quick Reference Tables](#quick-reference-tables)\n- [Knowledge Base](#knowledge-base)\n\n---\n\n## Trigger Terms\n\nUse this skill when you need to:\n\n- \"create user persona\"\n- \"generate persona from data\"\n- \"build customer journey map\"\n- \"map user journey\"\n- \"plan usability test\"\n- \"design usability study\"\n- \"analyze user research\"\n- \"synthesize interview findings\"\n- \"identify user pain points\"\n- \"define user archetypes\"\n- \"calculate research sample size\"\n- \"create empathy map\"\n- \"identify user needs\"\n\n---\n\n## Workflows\n\n### Workflow 1: Generate User Persona\n\n**Situation:** You have user data (analytics, surveys, interviews) and need to create a research-backed persona.\n\n**Steps:**\n\n1. **Prepare user data**\n\n   Required format (JSON):\n   ```json\n   [\n     {\n       \"user_id\": \"user_1\",\n       \"age\": 32,\n       \"usage_frequency\": \"daily\",\n       \"features_used\": [\"dashboard\", \"reports\", \"export\"],\n       \"primary_device\": \"desktop\",\n       \"usage_context\": \"work\",\n       \"tech_proficiency\": 7,\n       \"pain_points\": [\"slow loading\", \"confusing UI\"]\n     }\n   ]\n   ```\n\n2. **Run persona generator**\n   ```bash\n   # Human-readable output\n   python scripts\u002Fpersona_generator.py\n\n   # JSON output for integration\n   python scripts\u002Fpersona_generator.py json\n   ```\n\n3. **Review generated components**\n\n   | Component | What to Check |\n   |-----------|---------------|\n   | Archetype | Does it match the data patterns? |\n   | Demographics | Are they derived from actual data? |\n   | Goals | Are they specific and actionable? |\n   | Frustrations | Do they include frequency counts? |\n   | Design implications | Can designers act on these? |\n\n4. **Validate persona**\n\n   - Show to 3-5 real users: \"Does this sound like you?\"\n   - Cross-check with support tickets\n   - Verify against analytics data\n\n5. **Reference:** See `references\u002Fpersona-methodology.md` for validity criteria\n\n---\n\n### Workflow 2: Create Journey Map\n\n**Situation:** You need to visualize the end-to-end user experience for a specific goal.\n\n**Steps:**\n\n1. **Define scope**\n\n   | Element | Description |\n   |---------|-------------|\n   | Persona | Which user type |\n   | Goal | What they're trying to achieve |\n   | Start | Trigger that begins journey |\n   | End | Success criteria |\n   | Timeframe | Hours\u002Fdays\u002Fweeks |\n\n2. **Gather journey data**\n\n   Sources:\n   - User interviews (ask \"walk me through...\")\n   - Session recordings\n   - Analytics (funnel, drop-offs)\n   - Support tickets\n\n3. **Map the stages**\n\n   Typical B2B SaaS stages:\n   ```\n   Awareness → Evaluation → Onboarding → Adoption → Advocacy\n   ```\n\n4. **Fill in layers for each stage**\n\n   ```\n   Stage: [Name]\n   ├── Actions: What does user do?\n   ├── Touchpoints: Where do they interact?\n   ├── Emotions: How do they feel? (1-5)\n   ├── Pain Points: What frustrates them?\n   └── Opportunities: Where can we improve?\n   ```\n\n5. **Identify opportunities**\n\n   Priority Score = Frequency × Severity × Solvability\n\n6. **Reference:** See `references\u002Fjourney-mapping-guide.md` for templates\n\n---\n\n### Workflow 3: Plan Usability Test\n\n**Situation:** You need to validate a design with real users.\n\n**Steps:**\n\n1. **Define research questions**\n\n   Transform vague goals into testable questions:\n\n   | Vague | Testable |\n   |-------|----------|\n   | \"Is it easy to use?\" | \"Can users complete checkout in \u003C3 min?\" |\n   | \"Do users like it?\" | \"Will users choose Design A or B?\" |\n   | \"Does it make sense?\" | \"Can users find settings without hints?\" |\n\n2. **Select method**\n\n   | Method | Participants | Duration | Best For |\n   |--------|--------------|----------|----------|\n   | Moderated remote | 5-8 | 45-60 min | Deep insights |\n   | Unmoderated remote | 10-20 | 15-20 min | Quick validation |\n   | Guerrilla | 3-5 | 5-10 min | Rapid feedback |\n\n3. **Design tasks**\n\n   Good task format:\n   ```\n   SCENARIO: \"Imagine you're planning a trip to Paris...\"\n   GOAL: \"Book a hotel for 3 nights in your budget.\"\n   SUCCESS: \"You see the confirmation page.\"\n   ```\n\n   Task progression: Warm-up → Core → Secondary → Edge case → Free exploration\n\n4. **Define success metrics**\n\n   | Metric | Target |\n   |--------|--------|\n   | Completion rate | >80% |\n   | Time on task | \u003C2× expected |\n   | Error rate | \u003C15% |\n   | Satisfaction | >4\u002F5 |\n\n5. **Prepare moderator guide**\n\n   - Think-aloud instructions\n   - Non-leading prompts\n   - Post-task questions\n\n6. **Reference:** See `references\u002Fusability-testing-frameworks.md` for full guide\n\n---\n\n### Workflow 4: Synthesize Research\n\n**Situation:** You have raw research data (interviews, surveys, observations) and need actionable insights.\n\n**Steps:**\n\n1. **Code the data**\n\n   Tag each data point:\n   - `[GOAL]` - What they want to achieve\n   - `[PAIN]` - What frustrates them\n   - `[BEHAVIOR]` - What they actually do\n   - `[CONTEXT]` - When\u002Fwhere they use product\n   - `[QUOTE]` - Direct user words\n\n2. **Cluster similar patterns**\n\n   ```\n   User A: Uses daily, advanced features, shortcuts\n   User B: Uses daily, complex workflows, automation\n   User C: Uses weekly, basic needs, occasional\n\n   Cluster 1: A, B (Power Users)\n   Cluster 2: C (Casual User)\n   ```\n\n3. **Calculate segment sizes**\n\n   | Cluster | Users | % | Viability |\n   |---------|-------|---|-----------|\n   | Power Users | 18 | 36% | Primary persona |\n   | Business Users | 15 | 30% | Primary persona |\n   | Casual Users | 12 | 24% | Secondary persona |\n\n4. **Extract key findings**\n\n   For each theme:\n   - Finding statement\n   - Supporting evidence (quotes, data)\n   - Frequency (X\u002FY participants)\n   - Business impact\n   - Recommendation\n\n5. **Prioritize opportunities**\n\n   | Factor | Score 1-5 |\n   |--------|-----------|\n   | Frequency | How often does this occur? |\n   | Severity | How much does it hurt? |\n   | Breadth | How many users affected? |\n   | Solvability | Can we fix this? |\n\n6. **Reference:** See `references\u002Fpersona-methodology.md` for analysis framework\n\n---\n\n## Tool Reference\n\n### persona_generator.py\n\nGenerates data-driven personas from user research data.\n\n| Argument | Values | Default | Description |\n|----------|--------|---------|-------------|\n| format | (none), json | (none) | Output format |\n\n**Sample Output:**\n\n```\n============================================================\nPERSONA: Alex the Power User\n============================================================\n\n? A daily user who primarily uses the product for work purposes\n\nArchetype: Power User\nQuote: \"I need tools that can keep up with my workflow\"\n\n? Demographics:\n  • Age Range: 25-34\n  • Location Type: Urban\n  • Tech Proficiency: Advanced\n\n? Goals & Needs:\n  • Complete tasks efficiently\n  • Automate workflows\n  • Access advanced features\n\n? Frustrations:\n  • Slow loading times (14\u002F20 users)\n  • No keyboard shortcuts\n  • Limited API access\n\n? Design Implications:\n  → Optimize for speed and efficiency\n  → Provide keyboard shortcuts and power features\n  → Expose API and automation capabilities\n\n? Data: Based on 45 users\n    Confidence: High\n```\n\n**Archetypes Generated:**\n\n| Archetype | Signals | Design Focus |\n|-----------|---------|--------------|\n| power_user | Daily use, 10+ features | Efficiency, customization |\n| casual_user | Weekly use, 3-5 features | Simplicity, guidance |\n| business_user | Work context, team use | Collaboration, reporting |\n| mobile_first | Mobile primary | Touch, offline, speed |\n\n**Output Components:**\n\n| Component | Description |\n|-----------|-------------|\n| demographics | Age range, location, occupation, tech level |\n| psychographics | Motivations, values, attitudes, lifestyle |\n| behaviors | Usage patterns, feature preferences |\n| needs_and_goals | Primary, secondary, functional, emotional |\n| frustrations | Pain points with evidence |\n| scenarios | Contextual usage stories |\n| design_implications | Actionable recommendations |\n| data_points | Sample size, confidence level |\n\n---\n\n## Quick Reference Tables\n\n### Research Method Selection\n\n| Question Type | Best Method | Sample Size |\n|---------------|-------------|-------------|\n| \"What do users do?\" | Analytics, observation | 100+ events |\n| \"Why do they do it?\" | Interviews | 8-15 users |\n| \"How well can they do it?\" | Usability test | 5-8 users |\n| \"What do they prefer?\" | Survey, A\u002FB test | 50+ users |\n| \"What do they feel?\" | Diary study, interviews | 10-15 users |\n\n### Persona Confidence Levels\n\n| Sample Size | Confidence | Use Case |\n|-------------|------------|----------|\n| 5-10 users | Low | Exploratory |\n| 11-30 users | Medium | Directional |\n| 31+ users | High | Production |\n\n### Usability Issue Severity\n\n| Severity | Definition | Action |\n|----------|------------|--------|\n| 4 - Critical | Prevents task completion | Fix immediately |\n| 3 - Major | Significant difficulty | Fix before release |\n| 2 - Minor | Causes hesitation | Fix when possible |\n| 1 - Cosmetic | Noticed but not problematic | Low priority |\n\n### Interview Question Types\n\n| Type | Example | Use For |\n|------|---------|---------|\n| Context | \"Walk me through your typical day\" | Understanding environment |\n| Behavior | \"Show me how you do X\" | Observing actual actions |\n| Goals | \"What are you trying to achieve?\" | Uncovering motivations |\n| Pain | \"What's the hardest part?\" | Identifying frustrations |\n| Reflection | \"What would you change?\" | Generating ideas |\n\n---\n\n## Knowledge Base\n\nDetailed reference guides in `references\u002F`:\n\n| File | Content |\n|------|---------|\n| `persona-methodology.md` | Validity criteria, data collection, analysis framework |\n| `journey-mapping-guide.md` | Mapping process, templates, opportunity identification |\n| `example-personas.md` | 3 complete persona examples with data |\n| `usability-testing-frameworks.md` | Test planning, task design, analysis |\n\n---\n\n## Validation Checklist\n\n### Persona Quality\n- [ ] Based on 20+ users (minimum)\n- [ ] At least 2 data sources (quant + qual)\n- [ ] Specific, actionable goals\n- [ ] Frustrations include frequency counts\n- [ ] Design implications are specific\n- [ ] Confidence level stated\n\n### Journey Map Quality\n- [ ] Scope clearly defined (persona, goal, timeframe)\n- [ ] Based on real user data, not assumptions\n- [ ] All layers filled (actions, touchpoints, emotions)\n- [ ] Pain points identified per stage\n- [ ] Opportunities prioritized\n\n### Usability Test Quality\n- [ ] Research questions are testable\n- [ ] Tasks are realistic scenarios, not instructions\n- [ ] 5+ participants per design\n- [ ] Success metrics defined\n- [ ] Findings include severity ratings\n\n### Research Synthesis Quality\n- [ ] Data coded consistently\n- [ ] Patterns based on 3+ data points\n- [ ] Findings include evidence\n- [ ] Recommendations are actionable\n- [ ] Priorities justified\n\n## Related Skills\n\n- **UI Design System** (`product-team\u002Fui-design-system\u002F`) — Research findings inform design system decisions\n- **Product Manager Toolkit** (`product-team\u002Fproduct-manager-toolkit\u002F`) — Customer interview analysis complements persona research\n","# UX Researcher & Designer\n\nGenerate user personas from research data, create journey maps, plan usability tests, and synthesize research findings into actionable design recommendations.\n\n---\n\n## Table of Contents\n\n- [Trigger Terms](#trigger-terms)\n- [Workflows](#workflows)\n  - [Workflow 1: Generate User Persona](#workflow-1-generate-user-persona)\n  - [Workflow 2: Create Journey Map](#workflow-2-create-journey-map)\n  - [Workflow 3: Plan Usability Test](#workflow-3-plan-usability-test)\n  - [Workflow 4: Synthesize Research](#workflow-4-synthesize-research)\n- [Tool Reference](#tool-reference)\n- [Quick Reference Tables](#quick-reference-tables)\n- [Knowledge Base](#knowledge-base)\n\n---\n\n## Trigger Terms\n\nUse this skill when you need to:\n\n- \"create user persona\"\n- \"generate persona from data\"\n- \"build customer journey map\"\n- \"map user journey\"\n- \"plan usability test\"\n- \"design usability study\"\n- \"analyze user research\"\n- \"synthesize interview findings\"\n- \"identify user pain points\"\n- \"define user archetypes\"\n- \"calculate research sample size\"\n- \"create empathy map\"\n- \"identify user needs\"\n\n---\n\n## Workflows\n\n### Workflow 1: Generate User Persona\n\n**Situation:** You have user data (analytics, surveys, interviews) and need to create a research-backed persona.\n\n**Steps:**\n\n1. **Prepare user data**\n\n   Required format (JSON):\n   ```json\n   [\n     {\n       \"user_id\": \"user_1\",\n       \"age\": 32,\n       \"usage_frequency\": \"daily\",\n       \"features_used\": [\"dashboard\", \"reports\", \"export\"],\n       \"primary_device\": \"desktop\",\n       \"usage_context\": \"work\",\n       \"tech_proficiency\": 7,\n       \"pain_points\": [\"slow loading\", \"confusing UI\"]\n     }\n   ]\n   ```\n\n2. **Run persona generator**\n   ```bash\n   # Human-readable output\n   python scripts\u002Fpersona_generator.py\n\n   # JSON output for integration\n   python scripts\u002Fpersona_generator.py json\n   ```\n\n3. **Review generated components**\n\n   | Component | What to Check |\n   |-----------|---------------|\n   | Archetype | Does it match the data patterns? |\n   | Demographics | Are they derived from actual data? |\n   | Goals | Are they specific and actionable? |\n   | Frustrations | Do they include frequency counts? |\n   | Design implications | Can designers act on these? |\n\n4. **Validate persona**\n\n   - Show to 3-5 real users: \"Does this sound like you?\"\n   - Cross-check with support tickets\n   - Verify against analytics data\n\n5. **Reference:** See `references\u002Fpersona-methodology.md` for validity criteria\n\n---\n\n### Workflow 2: Create Journey Map\n\n**Situation:** You need to visualize the end-to-end user experience for a specific goal.\n\n**Steps:**\n\n1. **Define scope**\n\n   | Element | Description |\n   |---------|-------------|\n   | Persona | Which user type |\n   | Goal | What they're trying to achieve |\n   | Start | Trigger that begins journey |\n   | End | Success criteria |\n   | Timeframe | Hours\u002Fdays\u002Fweeks |\n\n2. **Gather journey data**\n\n   Sources:\n   - User interviews (ask \"walk me through...\")\n   - Session recordings\n   - Analytics (funnel, drop-offs)\n   - Support tickets\n\n3. **Map the stages**\n\n   Typical B2B SaaS stages:\n   ```\n   Awareness → Evaluation → Onboarding → Adoption → Advocacy\n   ```\n\n4. **Fill in layers for each stage**\n\n   ```\n   Stage: [Name]\n   ├── Actions: What does user do?\n   ├── Touchpoints: Where do they interact?\n   ├── Emotions: How do they feel? (1-5)\n   ├── Pain Points: What frustrates them?\n   └── Opportunities: Where can we improve?\n   ```\n\n5. **Identify opportunities**\n\n   Priority Score = Frequency × Severity × Solvability\n\n6. **Reference:** See `references\u002Fjourney-mapping-guide.md` for templates\n\n---\n\n### Workflow 3: Plan Usability Test\n\n**Situation:** You need to validate a design with real users.\n\n**Steps:**\n\n1. **Define research questions**\n\n   Transform vague goals into testable questions:\n\n   | Vague | Testable |\n   |-------|----------|\n   | \"Is it easy to use?\" | \"Can users complete checkout in \u003C3 min?\" |\n   | \"Do users like it?\" | \"Will users choose Design A or B?\" |\n   | \"Does it make sense?\" | \"Can users find settings without hints?\" |\n\n2. **Select method**\n\n   | Method | Participants | Duration | Best For |\n   |--------|--------------|----------|----------|\n   | Moderated remote | 5-8 | 45-60 min | Deep insights |\n   | Unmoderated remote | 10-20 | 15-20 min | Quick validation |\n   | Guerrilla | 3-5 | 5-10 min | Rapid feedback |\n\n3. **Design tasks**\n\n   Good task format:\n   ```\n   SCENARIO: \"Imagine you're planning a trip to Paris...\"\n   GOAL: \"Book a hotel for 3 nights in your budget.\"\n   SUCCESS: \"You see the confirmation page.\"\n   ```\n\n   Task progression: Warm-up → Core → Secondary → Edge case → Free exploration\n\n4. **Define success metrics**\n\n   | Metric | Target |\n   |--------|--------|\n   | Completion rate | >80% |\n   | Time on task | \u003C2× expected |\n   | Error rate | \u003C15% |\n   | Satisfaction | >4\u002F5 |\n\n5. **Prepare moderator guide**\n\n   - Think-aloud instructions\n   - Non-leading prompts\n   - Post-task questions\n\n6. **Reference:** See `references\u002Fusability-testing-frameworks.md` for full guide\n\n---\n\n### Workflow 4: Synthesize Research\n\n**Situation:** You have raw research data (interviews, surveys, observations) and need actionable insights.\n\n**Steps:**\n\n1. **Code the data**\n\n   Tag each data point:\n   - `[GOAL]` - What they want to achieve\n   - `[PAIN]` - What frustrates them\n   - `[BEHAVIOR]` - What they actually do\n   - `[CONTEXT]` - When\u002Fwhere they use product\n   - `[QUOTE]` - Direct user words\n\n2. **Cluster similar patterns**\n\n   ```\n   User A: Uses daily, advanced features, shortcuts\n   User B: Uses daily, complex workflows, automation\n   User C: Uses weekly, basic needs, occasional\n\n   Cluster 1: A, B (Power Users)\n   Cluster 2: C (Casual User)\n   ```\n\n3. **Calculate segment sizes**\n\n   | Cluster | Users | % | Viability |\n   |---------|-------|---|-----------|\n   | Power Users | 18 | 36% | Primary persona |\n   | Business Users | 15 | 30% | Primary persona |\n   | Casual Users | 12 | 24% | Secondary persona |\n\n4. **Extract key findings**\n\n   For each theme:\n   - Finding statement\n   - Supporting evidence (quotes, data)\n   - Frequency (X\u002FY participants)\n   - Business impact\n   - Recommendation\n\n5. **Prioritize opportunities**\n\n   | Factor | Score 1-5 |\n   |--------|-----------|\n   | Frequency | How often does this occur? |\n   | Severity | How much does it hurt? |\n   | Breadth | How many users affected? |\n   | Solvability | Can we fix this? |\n\n6. **Reference:** See `references\u002Fpersona-methodology.md` for analysis framework\n\n---\n\n## Tool Reference\n\n### persona_generator.py\n\nGenerates data-driven personas from user research data.\n\n| Argument | Values | Default | Description |\n|----------|--------|---------|-------------|\n| format | (none), json | (none) | Output format |\n\n**Sample Output:**\n\n```\n============================================================\nPERSONA: Alex the Power User\n============================================================\n\n? A daily user who primarily uses the product for work purposes\n\nArchetype: Power User\nQuote: \"I need tools that can keep up with my workflow\"\n\n? Demographics:\n  • Age Range: 25-34\n  • Location Type: Urban\n  • Tech Proficiency: Advanced\n\n? Goals & Needs:\n  • Complete tasks efficiently\n  • Automate workflows\n  • Access advanced features\n\n? Frustrations:\n  • Slow loading times (14\u002F20 users)\n  • No keyboard shortcuts\n  • Limited API access\n\n? Design Implications:\n  → Optimize for speed and efficiency\n  → Provide keyboard shortcuts and power features\n  → Expose API and automation capabilities\n\n? Data: Based on 45 users\n    Confidence: High\n```\n\n**Archetypes Generated:**\n\n| Archetype | Signals | Design Focus |\n|-----------|---------|--------------|\n| power_user | Daily use, 10+ features | Efficiency, customization |\n| casual_user | Weekly use, 3-5 features | Simplicity, guidance |\n| business_user | Work context, team use | Collaboration, reporting |\n| mobile_first | Mobile primary | Touch, offline, speed |\n\n**Output Components:**\n\n| Component | Description |\n|-----------|-------------|\n| demographics | Age range, location, occupation, tech level |\n| psychographics | Motivations, values, attitudes, lifestyle |\n| behaviors | Usage patterns, feature preferences |\n| needs_and_goals | Primary, secondary, functional, emotional |\n| frustrations | Pain points with evidence |\n| scenarios | Contextual usage stories |\n| design_implications | Actionable recommendations |\n| data_points | Sample size, confidence level |\n\n---\n\n## Quick Reference Tables\n\n### Research Method Selection\n\n| Question Type | Best Method | Sample Size |\n|---------------|-------------|-------------|\n| \"What do users do?\" | Analytics, observation | 100+ events |\n| \"Why do they do it?\" | Interviews | 8-15 users |\n| \"How well can they do it?\" | Usability test | 5-8 users |\n| \"What do they prefer?\" | Survey, A\u002FB test | 50+ users |\n| \"What do they feel?\" | Diary study, interviews | 10-15 users |\n\n### Persona Confidence Levels\n\n| Sample Size | Confidence | Use Case |\n|-------------|------------|----------|\n| 5-10 users | Low | Exploratory |\n| 11-30 users | Medium | Directional |\n| 31+ users | High | Production |\n\n### Usability Issue Severity\n\n| Severity | Definition | Action |\n|----------|------------|--------|\n| 4 - Critical | Prevents task completion | Fix immediately |\n| 3 - Major | Significant difficulty | Fix before release |\n| 2 - Minor | Causes hesitation | Fix when possible |\n| 1 - Cosmetic | Noticed but not problematic | Low priority |\n\n### Interview Question Types\n\n| Type | Example | Use For |\n|------|---------|---------|\n| Context | \"Walk me through your typical day\" | Understanding environment |\n| Behavior | \"Show me how you do X\" | Observing actual actions |\n| Goals | \"What are you trying to achieve?\" | Uncovering motivations |\n| Pain | \"What's the hardest part?\" | Identifying frustrations |\n| Reflection | \"What would you change?\" | Generating ideas |\n\n---\n\n## Knowledge Base\n\nDetailed reference guides in `references\u002F`:\n\n| File | Content |\n|------|---------|\n| `persona-methodology.md` | Validity criteria, data collection, analysis framework |\n| `journey-mapping-guide.md` | Mapping process, templates, opportunity identification |\n| `example-personas.md` | 3 complete persona examples with data |\n| `usability-testing-frameworks.md` | Test planning, task design, analysis |\n\n---\n\n## Validation Checklist\n\n### Persona Quality\n- [ ] Based on 20+ users (minimum)\n- [ ] At least 2 data sources (quant + qual)\n- [ ] Specific, actionable goals\n- [ ] Frustrations include frequency counts\n- [ ] Design implications are specific\n- [ ] Confidence level stated\n\n### Journey Map Quality\n- [ ] Scope clearly defined (persona, goal, timeframe)\n- [ ] Based on real user data, not assumptions\n- [ ] All layers filled (actions, touchpoints, emotions)\n- [ ] Pain points identified per stage\n- [ ] Opportunities prioritized\n\n### Usability Test Quality\n- [ ] Research questions are testable\n- [ ] Tasks are realistic scenarios, not instructions\n- [ ] 5+ participants per design\n- [ ] Success metrics defined\n- [ ] Findings include severity ratings\n\n### Research Synthesis Quality\n- [ ] Data coded consistently\n- [ ] Patterns based on 3+ data points\n- [ ] Findings include evidence\n- [ ] Recommendations are actionable\n- [ ] Priorities justified\n\n## Related Skills\n\n- **UI Design System** (`product-team\u002Fui-design-system\u002F`) — Research findings inform design system decisions\n- **Product Manager Toolkit** (`product-team\u002Fproduct-manager-toolkit\u002F`) — Customer interview analysis complements persona research\n",{"name":5,"description":7},"main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","product-team\u002Fux-researcher-designer",2,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill","https:\u002F\u002Fgithub.com\u002Fafaizalam2003","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmdfaizalam2003\u002F","2026-04-01 04:35:43",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill ux-researcher-designer",{"tool":71,"command":72},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill ux-researcher-designer",{"tool":74,"command":75},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill ux-researcher-designer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fux-researcher-designer\u002FSKILL.md",true,[79,85,91,95,99,103],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"assets\u002Fresearch_plan_template.md","ASSET","资产文件",4802,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fux-researcher-designer\u002Fassets\u002Fresearch_plan_template.md",{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fexample-personas.md","REFERENCE","参考文档",11990,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fux-researcher-designer\u002Freferences\u002Fexample-personas.md",{"path":92,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fjourney-mapping-guide.md",18102,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fux-researcher-designer\u002Freferences\u002Fjourney-mapping-guide.md",{"path":96,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fpersona-methodology.md",11644,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fux-researcher-designer\u002Freferences\u002Fpersona-methodology.md",{"path":100,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fusability-testing-frameworks.md",11932,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fux-researcher-designer\u002Freferences\u002Fusability-testing-frameworks.md",{"path":104,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":107,"sourceHtmlUrl":108},"scripts\u002Fpersona_generator.py","SCRIPT","脚本",23675,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fux-researcher-designer\u002Fscripts\u002Fpersona_generator.py",[110,138,163,188,215,235],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":119,"publishedAt":52},"01M6KC4E8MYR9DBAZTAXHKYMMH","soc2-compliance","Use when the user asks to prepare for SOC 2 audits, map Trust Service Criteria, build control matrices, collect audit evidence, perform gap analysis, or assess SOC 2 Type I vs Type II readiness.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fsoc2-compliance\u002FSKILL.md",[116],{"categoryNo":117,"categoryName":118,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000037","律师与法务",[120,121,122,123,124,125,126,127,47,128,129,130,131,132,133,134,135,136,137,39],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":52},"01M6KC461R3GKGZ1TAYHVR1MW9","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[145,146,147,148,149,150,151,152,127,47,153,154,155,156,157,158,159,160,161,162],"risk","risk management specialist","management","risk management","risk evaluation","product","Evaluation","lifecycle","risk matrix","iso","medical","iso 14971","identification","information","post-production","tree","matrix","implementing",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":52},"01M6KC3HF5ZFSSP2NZF68PEPFB","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[170,171,172,173,174,175,176,177,178,47,179,180,181,182,183,184,185,186,187,39],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":198,"publishedAt":52},"01M6KC34Z8M1559EY1CXYBJB1A","quality-manager-qms-iso13485","ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[194,197],{"categoryNo":195,"categoryName":196,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[199,200,187,51,201,202,203,204,205,47,206,207,208,209,210,211,212,213,39,214],"quality manager qms iso13485","quality","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":222,"publishedAt":52},"01M6KC2FXHBHXYX2ZZ17Y3GDB4","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[221],{"categoryNo":117,"categoryName":118,"taxonomyType":29,"taxonomyTypeDesc":30},[223,200,187,224,225,226,227,228,120,229,205,230,171,231,232,233,154,210,39,234],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":236,"name":237,"nameZh":6,"description":238,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":239,"categories":240,"keywords":248,"publishedAt":52},"01M6KC1VRR5JTDBNZANHPS6VR6","quality-documentation-manager","Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[241,244,247],{"categoryNo":242,"categoryName":243,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":245,"categoryName":246,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":117,"categoryName":118,"taxonomyType":29,"taxonomyTypeDesc":30},[249,250,200,187,224,251,252,124,205,253,254,255,256,257,155,258,259,260,261,39],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]