[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70GZCGECSW4TNHMS854DF79":3,"skill-same:01M70GZCGECSW4TNHMS854DF79":82},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M70GZCGECSW4TNHMS854DF79","user-insight-synthesis",null,"Interview techniques, persona creation, journey mapping, and usability testing patterns. Use when planning research, conducting user interviews, creating personas, mapping user journeys, or designing usability tests. Essential for user-research, requirements-analysis, and interaction-architecture agents.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fplugins\u002Fteam\u002Fskills\u002Fdesign\u002Fuser-insight-synthesis\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"insight synthesis","Synthesis","user","user insight synthesis","patterns","mapping","interviews","interaction","architecture","analysis","usability","when","journey mapping","persona","journey","testing","user interviews","creation","testing patterns","user journeys","2026-11-10 10:12:30",false,"---\nname: user-insight-synthesis\ndescription: Interview techniques, persona creation, journey mapping, and usability testing patterns. Use when planning research, conducting user interviews, creating personas, mapping user journeys, or designing usability tests. Essential for user-research, requirements-analysis, and interaction-architecture agents.\n---\n\n# User Research Methods\n\nA domain-specific skill providing structured methodologies for understanding users through research. This skill covers the complete research lifecycle from planning through synthesis and reporting.\n\n## When to Use\n\n- Planning user research studies for new or existing products\n- Conducting user interviews to understand needs and behaviors\n- Creating behavioral personas based on research data\n- Mapping user journeys to identify pain points and opportunities\n- Designing and running usability tests\n- Synthesizing research findings into actionable insights\n\n## Research Method Selection\n\nChoose research methods based on what you need to learn and where you are in the product lifecycle.\n\n### Method Selection Matrix\n\n| Question Type | Early Discovery | Design Validation | Post-Launch |\n|--------------|-----------------|-------------------|-------------|\n| What do users need? | Contextual inquiry, Diary studies | Concept testing | Support ticket analysis |\n| How do users behave? | Field observation, Shadowing | Prototype testing | Analytics, Session recordings |\n| What do users think? | Depth interviews | Preference testing | Surveys, NPS |\n| Can users complete tasks? | Card sorting | Usability testing | A\u002FB testing |\n\n### Generative vs Evaluative Research\n\n**Generative Research** - Use when exploring problem spaces:\n- Contextual inquiry (observe users in their environment)\n- Diary studies (longitudinal behavior patterns)\n- Participatory design workshops (co-create with users)\n- Jobs-to-be-done interviews (understand underlying motivations)\n\n**Evaluative Research** - Use when validating solutions:\n- Usability testing (can users complete tasks?)\n- A\u002FB testing (which variant performs better?)\n- Preference testing (which option do users prefer?)\n- Accessibility audits (does it work for everyone?)\n\n### Sample Size Guidelines\n\n| Method | Minimum Sample | Recommended | Diminishing Returns |\n|--------|---------------|-------------|---------------------|\n| Depth interviews | 5 | 8-12 | 15+ |\n| Usability testing | 5 | 5-8 | 10+ |\n| Card sorting | 15 | 30 | 50+ |\n| Surveys | 100 | 300-500 | Depends on segments |\n| A\u002FB tests | Statistical power calculation required | - | - |\n\n## User Interview Techniques\n\n### Interview Structure\n\n**1. Opening (5 minutes)**\n- Build rapport with neutral topics\n- Explain the purpose without biasing\n- Confirm recording consent\n- Set expectations for the session\n\n**2. Context Gathering (10 minutes)**\n- Understand their role and background\n- Map their typical day or workflow\n- Identify tools and touchpoints they use\n\n**3. Core Exploration (25-35 minutes)**\n- Use open-ended questions\n- Follow the participant's lead\n- Probe deeper on interesting topics\n- Ask for specific examples and stories\n\n**4. Closing (5 minutes)**\n- Ask if anything was missed\n- Request permission for follow-up\n- Thank them for their time\n\n### Question Types\n\n**Opening Questions** - Establish context:\n- \"Walk me through a typical day when you...\"\n- \"Tell me about the last time you...\"\n- \"How did you first start...?\"\n\n**Probing Questions** - Go deeper:\n- \"What do you mean by...?\"\n- \"Can you give me a specific example?\"\n- \"What happened next?\"\n- \"How did that make you feel?\"\n\n**Clarifying Questions** - Ensure understanding:\n- \"So if I understand correctly...\"\n- \"You mentioned X, can you tell me more?\"\n- \"When you say X, do you mean...?\"\n\n**Projective Questions** - Surface hidden needs:\n- \"If you had a magic wand, what would you change?\"\n- \"What would your ideal experience look like?\"\n- \"What would have to be true for you to switch?\"\n\n### Common Interview Pitfalls\n\n| Pitfall | Problem | Solution |\n|---------|---------|----------|\n| Leading questions | Biases responses | Ask neutral, open questions |\n| Asking about future behavior | People predict poorly | Ask about past behavior instead |\n| Accepting vague answers | Loses detail | Probe for specific examples |\n| Talking too much | Reduces user input | Embrace silence, let them think |\n| Solving during interview | Shifts to validation mode | Save solutions for later |\n\n### Observing Behavior vs Statements\n\nUsers often say one thing but do another. Watch for discrepancies:\n\n- **Workarounds**: Creative solutions reveal unmet needs\n- **Hesitation**: Confusion or friction points\n- **Skipped steps**: What they consider unnecessary\n- **Emotional reactions**: Frustration, delight, confusion\n- **Tool switching**: Integration pain points\n\n## Persona Creation Framework\n\n### Behavioral Personas vs Demographic Personas\n\n**Avoid demographic personas** that describe who users are (age, income, job title). These often become stereotypes that don't predict behavior.\n\n**Create behavioral personas** that describe what users do, why they do it, and what barriers they face. These drive design decisions.\n\n### Persona Components\n\n```\n[Persona Name]\n\nBEHAVIORAL ARCHETYPE\nOne sentence describing their core behavior pattern\n\nGOALS\n- Primary goal (what they're ultimately trying to achieve)\n- Secondary goals (supporting objectives)\n- Emotional goals (how they want to feel)\n\nBEHAVIORS\n- Key behavior 1 (observed pattern with frequency)\n- Key behavior 2 (observed pattern with context)\n- Key behavior 3 (observed pattern with trigger)\n\nPAIN POINTS\n- Frustration 1 (specific problem with impact)\n- Frustration 2 (specific problem with workaround)\n- Frustration 3 (specific problem with frequency)\n\nDECISION FACTORS\n- What influences their choices\n- What trade-offs they make\n- What they prioritize\n\nCONTEXT\n- When they engage with the product\n- Where they use it\n- What else competes for attention\n\nQUOTE\n\"Verbatim quote from research that captures their perspective\"\n```\n\n### Creating Personas from Research\n\n**Step 1: Identify Behavior Patterns**\n- Review all interview notes and observations\n- Tag recurring behaviors, goals, and pain points\n- Look for clusters of similar behavior\n\n**Step 2: Define Behavioral Variables**\n- List the key dimensions that differentiate users\n- Place participants along each dimension\n- Identify clusters that represent archetypes\n\n**Step 3: Build Persona Profiles**\n- Write narrative based on research data only\n- Include direct quotes from participants\n- Validate that persona represents multiple participants\n\n**Step 4: Prioritize Personas**\n- Identify primary persona (design for first)\n- Secondary personas (accommodate)\n- Edge cases (consider but don't optimize for)\n\n### Persona Anti-Patterns\n\n| Anti-Pattern | Why It Fails | Better Approach |\n|--------------|--------------|-----------------|\n| Fictional details | Creates false confidence | Use only observed data |\n| Photos of real people | Triggers stereotypes | Use illustrations or initials |\n| Too many personas | Dilutes focus | Limit to 3-5 maximum |\n| Demographic focus | Doesn't predict behavior | Focus on goals and behaviors |\n| No pain points | Misses design opportunities | Ground in observed frustrations |\n\n## Journey Mapping Methodology\n\n### Journey Map Components\n\n```\nJOURNEY MAP: [User Goal]\n\nPERSONA: [Which persona this represents]\nSCENARIO: [Specific context and trigger]\n\n| Stage | [Stage 1] | [Stage 2] | [Stage 3] | [Stage 4] |\n|-------|-----------|-----------|-----------|-----------|\n| Actions | What user does | ... | ... | ... |\n| Touchpoints | Channels\u002Finterfaces | ... | ... | ... |\n| Thoughts | What they're thinking | ... | ... | ... |\n| Emotions | How they feel (scale) | ... | ... | ... |\n| Pain Points | Frustrations | ... | ... | ... |\n| Opportunities | Design possibilities | ... | ... | ... |\n```\n\n### Journey Mapping Process\n\n**1. Define Scope**\n- Which persona is this for?\n- What goal or scenario are we mapping?\n- Where does the journey start and end?\n- What level of detail do we need?\n\n**2. Map the Current State**\n- List all stages from trigger to completion\n- Document what users do at each stage\n- Identify all touchpoints (channels, systems, people)\n- Note what users think and feel\n- Mark pain points and moments of delight\n\n**3. Validate with Data**\n- Cross-reference with analytics data\n- Validate with additional user interviews\n- Check assumptions against support data\n- Ensure map represents typical experience\n\n**4. Identify Opportunities**\n- Where are the highest-impact pain points?\n- Where do users drop off or get stuck?\n- What moments could be transformed?\n- Where can we exceed expectations?\n\n### Journey Map Types\n\n**Current State Maps** - Document how things work today\n- Based on research observations\n- Reveals improvement opportunities\n- Aligns stakeholders on reality\n\n**Future State Maps** - Envision improved experience\n- Based on current state insights\n- Shows target experience\n- Guides design decisions\n\n**Service Blueprints** - Include backend processes\n- Shows frontstage and backstage\n- Reveals operational dependencies\n- Identifies system requirements\n\n### Emotional Curve Mapping\n\nTrack emotional state across the journey using a simple scale:\n\n```\nVery Positive  +2  ----*----\nPositive       +1  ----*---------*----\nNeutral         0  *---------*----\nNegative       -1  ----*----\nVery Negative  -2  ----*----\n                   |Stage1|Stage2|Stage3|Stage4|\n```\n\nKey moments to identify:\n- **Peak moments**: Highest positive emotion (protect and amplify)\n- **Valley moments**: Lowest emotion (priority for improvement)\n- **Transition points**: Where emotion shifts (critical touchpoints)\n- **Ending moments**: Final impression (strong impact on memory)\n\n## Usability Testing Patterns\n\n### Test Types\n\n**Moderated Testing** - Facilitator guides participant\n- Best for: Complex tasks, early prototypes, need for probing\n- Pros: Rich qualitative data, can adapt on the fly\n- Cons: Time-intensive, facilitator can bias\n\n**Unmoderated Testing** - Participant works independently\n- Best for: Simple tasks, large samples, geographic spread\n- Pros: Scalable, no facilitator bias, natural behavior\n- Cons: No probing, participants may give up\n\n**Guerrilla Testing** - Quick tests with available people\n- Best for: Early validation, simple concepts, tight timelines\n- Pros: Fast, cheap, good for iteration\n- Cons: May not match target users, limited depth\n\n### Test Protocol Structure\n\n**1. Pre-Test Setup**\n- Confirm participant matches screener\n- Prepare test environment (prototype, recording)\n- Review tasks and questions\n- Test the test (pilot run)\n\n**2. Introduction (5 minutes)**\n- Explain the purpose (testing the design, not them)\n- Describe think-aloud protocol\n- Confirm recording consent\n- Encourage honest feedback\n\n**3. Background Questions (5 minutes)**\n- Relevant experience with similar products\n- Current tools and workflows\n- Expectations for this type of product\n\n**4. Task Scenarios (30-40 minutes)**\n- Present tasks one at a time\n- Use realistic scenarios, not instructions\n- Observe without helping\n- Probe after task completion\n\n**5. Post-Test Questions (10 minutes)**\n- Overall impressions\n- Comparison to expectations\n- Suggestions for improvement\n- Follow-up on observed issues\n\n### Writing Effective Task Scenarios\n\n**Bad task**: \"Click on Settings and change your notification preferences\"\n- Reveals the solution\n- Uses UI terminology\n- No realistic context\n\n**Good task**: \"You're getting too many email notifications. How would you reduce them?\"\n- Goal-oriented\n- User's language\n- Realistic motivation\n\n### Task Scenario Template\n\n```\nSCENARIO: [Context that makes the task realistic]\nGOAL: [What the user is trying to accomplish]\nSUCCESS CRITERIA: [How you'll know they succeeded]\n```\n\n### Metrics to Capture\n\n**Effectiveness Metrics**\n- Task success rate (completed \u002F attempted)\n- Error rate (errors \u002F task)\n- Recovery rate (recovered from errors \u002F total errors)\n\n**Efficiency Metrics**\n- Time on task (seconds to completion)\n- Number of steps (compared to optimal path)\n- Help requests (times asked for assistance)\n\n**Satisfaction Metrics**\n- Post-task rating (1-7 scale per task)\n- System Usability Scale (SUS) score\n- Net Promoter Score (NPS)\n- Qualitative feedback themes\n\n### Severity Rating Scale\n\n| Rating | Name | Definition | Action |\n|--------|------|------------|--------|\n| 1 | Cosmetic | Noticed but no impact | Fix if time permits |\n| 2 | Minor | Slight difficulty, recovered easily | Fix in next release |\n| 3 | Major | Significant difficulty, delayed success | Fix before release |\n| 4 | Critical | Prevented task completion | Must fix immediately |\n\n## Synthesis and Reporting\n\n### Affinity Mapping Process\n\n**1. Gather Raw Data**\n- Write each observation on a separate note\n- Include quotes, behaviors, and pain points\n- One insight per note\n\n**2. Cluster Related Notes**\n- Group similar observations together\n- Don't force categories, let them emerge\n- Move notes as patterns become clear\n\n**3. Name the Clusters**\n- Create descriptive labels for each group\n- Labels should capture the theme\n- Higher-level groups may emerge\n\n**4. Identify Patterns**\n- What themes appear across multiple participants?\n- What surprises challenge assumptions?\n- What opportunities become clear?\n\n### Research Report Structure\n\n```\nRESEARCH REPORT: [Study Name]\n\nEXECUTIVE SUMMARY\n- Research objective\n- Methods used\n- Key findings (3-5 bullets)\n- Recommended actions\n\nMETHODOLOGY\n- Research questions\n- Participant criteria and recruitment\n- Methods and sample size\n- Limitations\n\nKEY FINDINGS\nFinding 1: [Title]\n- Evidence: What we observed\n- Impact: Why it matters\n- Quote: \"Supporting verbatim\"\n\nFinding 2: [Title]\n...\n\nRECOMMENDATIONS\n- Priority 1: [Action] - Addresses [finding]\n- Priority 2: [Action] - Addresses [finding]\n- Priority 3: [Action] - Addresses [finding]\n\nNEXT STEPS\n- Immediate actions\n- Further research needed\n- Stakeholder follow-up\n\nAPPENDIX\n- Participant details (anonymized)\n- Full data sets\n- Methodology details\n```\n\n### Presenting Findings\n\n**Lead with insights, not methodology**\n- Start with what you learned, not how you learned it\n- Save methodology details for appendix\n\n**Use participant voices**\n- Include direct quotes that bring findings to life\n- Video clips are more powerful than text\n\n**Connect to business outcomes**\n- Tie findings to metrics stakeholders care about\n- Quantify impact where possible\n\n**Provide clear recommendations**\n- Don't just report problems, suggest solutions\n- Prioritize by impact and feasibility\n\n## Best Practices\n\n- Recruit participants who actually face the problem you're solving\n- Focus on understanding behavior, not validating your ideas\n- Look for patterns across participants, not individual opinions\n- Always observe what users do, not just what they say\n- Use multiple methods to triangulate findings\n- Create lightweight deliverables that teams will actually use\n- Involve stakeholders in research to build empathy\n- Measure research impact through design decisions influenced\n\n## References\n\n- `templates\u002Fresearch-plan-template.md` - Planning template for research studies\n","# User Research Methods\n\nA domain-specific skill providing structured methodologies for understanding users through research. This skill covers the complete research lifecycle from planning through synthesis and reporting.\n\n## When to Use\n\n- Planning user research studies for new or existing products\n- Conducting user interviews to understand needs and behaviors\n- Creating behavioral personas based on research data\n- Mapping user journeys to identify pain points and opportunities\n- Designing and running usability tests\n- Synthesizing research findings into actionable insights\n\n## Research Method Selection\n\nChoose research methods based on what you need to learn and where you are in the product lifecycle.\n\n### Method Selection Matrix\n\n| Question Type | Early Discovery | Design Validation | Post-Launch |\n|--------------|-----------------|-------------------|-------------|\n| What do users need? | Contextual inquiry, Diary studies | Concept testing | Support ticket analysis |\n| How do users behave? | Field observation, Shadowing | Prototype testing | Analytics, Session recordings |\n| What do users think? | Depth interviews | Preference testing | Surveys, NPS |\n| Can users complete tasks? | Card sorting | Usability testing | A\u002FB testing |\n\n### Generative vs Evaluative Research\n\n**Generative Research** - Use when exploring problem spaces:\n- Contextual inquiry (observe users in their environment)\n- Diary studies (longitudinal behavior patterns)\n- Participatory design workshops (co-create with users)\n- Jobs-to-be-done interviews (understand underlying motivations)\n\n**Evaluative Research** - Use when validating solutions:\n- Usability testing (can users complete tasks?)\n- A\u002FB testing (which variant performs better?)\n- Preference testing (which option do users prefer?)\n- Accessibility audits (does it work for everyone?)\n\n### Sample Size Guidelines\n\n| Method | Minimum Sample | Recommended | Diminishing Returns |\n|--------|---------------|-------------|---------------------|\n| Depth interviews | 5 | 8-12 | 15+ |\n| Usability testing | 5 | 5-8 | 10+ |\n| Card sorting | 15 | 30 | 50+ |\n| Surveys | 100 | 300-500 | Depends on segments |\n| A\u002FB tests | Statistical power calculation required | - | - |\n\n## User Interview Techniques\n\n### Interview Structure\n\n**1. Opening (5 minutes)**\n- Build rapport with neutral topics\n- Explain the purpose without biasing\n- Confirm recording consent\n- Set expectations for the session\n\n**2. Context Gathering (10 minutes)**\n- Understand their role and background\n- Map their typical day or workflow\n- Identify tools and touchpoints they use\n\n**3. Core Exploration (25-35 minutes)**\n- Use open-ended questions\n- Follow the participant's lead\n- Probe deeper on interesting topics\n- Ask for specific examples and stories\n\n**4. Closing (5 minutes)**\n- Ask if anything was missed\n- Request permission for follow-up\n- Thank them for their time\n\n### Question Types\n\n**Opening Questions** - Establish context:\n- \"Walk me through a typical day when you...\"\n- \"Tell me about the last time you...\"\n- \"How did you first start...?\"\n\n**Probing Questions** - Go deeper:\n- \"What do you mean by...?\"\n- \"Can you give me a specific example?\"\n- \"What happened next?\"\n- \"How did that make you feel?\"\n\n**Clarifying Questions** - Ensure understanding:\n- \"So if I understand correctly...\"\n- \"You mentioned X, can you tell me more?\"\n- \"When you say X, do you mean...?\"\n\n**Projective Questions** - Surface hidden needs:\n- \"If you had a magic wand, what would you change?\"\n- \"What would your ideal experience look like?\"\n- \"What would have to be true for you to switch?\"\n\n### Common Interview Pitfalls\n\n| Pitfall | Problem | Solution |\n|---------|---------|----------|\n| Leading questions | Biases responses | Ask neutral, open questions |\n| Asking about future behavior | People predict poorly | Ask about past behavior instead |\n| Accepting vague answers | Loses detail | Probe for specific examples |\n| Talking too much | Reduces user input | Embrace silence, let them think |\n| Solving during interview | Shifts to validation mode | Save solutions for later |\n\n### Observing Behavior vs Statements\n\nUsers often say one thing but do another. Watch for discrepancies:\n\n- **Workarounds**: Creative solutions reveal unmet needs\n- **Hesitation**: Confusion or friction points\n- **Skipped steps**: What they consider unnecessary\n- **Emotional reactions**: Frustration, delight, confusion\n- **Tool switching**: Integration pain points\n\n## Persona Creation Framework\n\n### Behavioral Personas vs Demographic Personas\n\n**Avoid demographic personas** that describe who users are (age, income, job title). These often become stereotypes that don't predict behavior.\n\n**Create behavioral personas** that describe what users do, why they do it, and what barriers they face. These drive design decisions.\n\n### Persona Components\n\n```\n[Persona Name]\n\nBEHAVIORAL ARCHETYPE\nOne sentence describing their core behavior pattern\n\nGOALS\n- Primary goal (what they're ultimately trying to achieve)\n- Secondary goals (supporting objectives)\n- Emotional goals (how they want to feel)\n\nBEHAVIORS\n- Key behavior 1 (observed pattern with frequency)\n- Key behavior 2 (observed pattern with context)\n- Key behavior 3 (observed pattern with trigger)\n\nPAIN POINTS\n- Frustration 1 (specific problem with impact)\n- Frustration 2 (specific problem with workaround)\n- Frustration 3 (specific problem with frequency)\n\nDECISION FACTORS\n- What influences their choices\n- What trade-offs they make\n- What they prioritize\n\nCONTEXT\n- When they engage with the product\n- Where they use it\n- What else competes for attention\n\nQUOTE\n\"Verbatim quote from research that captures their perspective\"\n```\n\n### Creating Personas from Research\n\n**Step 1: Identify Behavior Patterns**\n- Review all interview notes and observations\n- Tag recurring behaviors, goals, and pain points\n- Look for clusters of similar behavior\n\n**Step 2: Define Behavioral Variables**\n- List the key dimensions that differentiate users\n- Place participants along each dimension\n- Identify clusters that represent archetypes\n\n**Step 3: Build Persona Profiles**\n- Write narrative based on research data only\n- Include direct quotes from participants\n- Validate that persona represents multiple participants\n\n**Step 4: Prioritize Personas**\n- Identify primary persona (design for first)\n- Secondary personas (accommodate)\n- Edge cases (consider but don't optimize for)\n\n### Persona Anti-Patterns\n\n| Anti-Pattern | Why It Fails | Better Approach |\n|--------------|--------------|-----------------|\n| Fictional details | Creates false confidence | Use only observed data |\n| Photos of real people | Triggers stereotypes | Use illustrations or initials |\n| Too many personas | Dilutes focus | Limit to 3-5 maximum |\n| Demographic focus | Doesn't predict behavior | Focus on goals and behaviors |\n| No pain points | Misses design opportunities | Ground in observed frustrations |\n\n## Journey Mapping Methodology\n\n### Journey Map Components\n\n```\nJOURNEY MAP: [User Goal]\n\nPERSONA: [Which persona this represents]\nSCENARIO: [Specific context and trigger]\n\n| Stage | [Stage 1] | [Stage 2] | [Stage 3] | [Stage 4] |\n|-------|-----------|-----------|-----------|-----------|\n| Actions | What user does | ... | ... | ... |\n| Touchpoints | Channels\u002Finterfaces | ... | ... | ... |\n| Thoughts | What they're thinking | ... | ... | ... |\n| Emotions | How they feel (scale) | ... | ... | ... |\n| Pain Points | Frustrations | ... | ... | ... |\n| Opportunities | Design possibilities | ... | ... | ... |\n```\n\n### Journey Mapping Process\n\n**1. Define Scope**\n- Which persona is this for?\n- What goal or scenario are we mapping?\n- Where does the journey start and end?\n- What level of detail do we need?\n\n**2. Map the Current State**\n- List all stages from trigger to completion\n- Document what users do at each stage\n- Identify all touchpoints (channels, systems, people)\n- Note what users think and feel\n- Mark pain points and moments of delight\n\n**3. Validate with Data**\n- Cross-reference with analytics data\n- Validate with additional user interviews\n- Check assumptions against support data\n- Ensure map represents typical experience\n\n**4. Identify Opportunities**\n- Where are the highest-impact pain points?\n- Where do users drop off or get stuck?\n- What moments could be transformed?\n- Where can we exceed expectations?\n\n### Journey Map Types\n\n**Current State Maps** - Document how things work today\n- Based on research observations\n- Reveals improvement opportunities\n- Aligns stakeholders on reality\n\n**Future State Maps** - Envision improved experience\n- Based on current state insights\n- Shows target experience\n- Guides design decisions\n\n**Service Blueprints** - Include backend processes\n- Shows frontstage and backstage\n- Reveals operational dependencies\n- Identifies system requirements\n\n### Emotional Curve Mapping\n\nTrack emotional state across the journey using a simple scale:\n\n```\nVery Positive  +2  ----*----\nPositive       +1  ----*---------*----\nNeutral         0  *---------*----\nNegative       -1  ----*----\nVery Negative  -2  ----*----\n                   |Stage1|Stage2|Stage3|Stage4|\n```\n\nKey moments to identify:\n- **Peak moments**: Highest positive emotion (protect and amplify)\n- **Valley moments**: Lowest emotion (priority for improvement)\n- **Transition points**: Where emotion shifts (critical touchpoints)\n- **Ending moments**: Final impression (strong impact on memory)\n\n## Usability Testing Patterns\n\n### Test Types\n\n**Moderated Testing** - Facilitator guides participant\n- Best for: Complex tasks, early prototypes, need for probing\n- Pros: Rich qualitative data, can adapt on the fly\n- Cons: Time-intensive, facilitator can bias\n\n**Unmoderated Testing** - Participant works independently\n- Best for: Simple tasks, large samples, geographic spread\n- Pros: Scalable, no facilitator bias, natural behavior\n- Cons: No probing, participants may give up\n\n**Guerrilla Testing** - Quick tests with available people\n- Best for: Early validation, simple concepts, tight timelines\n- Pros: Fast, cheap, good for iteration\n- Cons: May not match target users, limited depth\n\n### Test Protocol Structure\n\n**1. Pre-Test Setup**\n- Confirm participant matches screener\n- Prepare test environment (prototype, recording)\n- Review tasks and questions\n- Test the test (pilot run)\n\n**2. Introduction (5 minutes)**\n- Explain the purpose (testing the design, not them)\n- Describe think-aloud protocol\n- Confirm recording consent\n- Encourage honest feedback\n\n**3. Background Questions (5 minutes)**\n- Relevant experience with similar products\n- Current tools and workflows\n- Expectations for this type of product\n\n**4. Task Scenarios (30-40 minutes)**\n- Present tasks one at a time\n- Use realistic scenarios, not instructions\n- Observe without helping\n- Probe after task completion\n\n**5. Post-Test Questions (10 minutes)**\n- Overall impressions\n- Comparison to expectations\n- Suggestions for improvement\n- Follow-up on observed issues\n\n### Writing Effective Task Scenarios\n\n**Bad task**: \"Click on Settings and change your notification preferences\"\n- Reveals the solution\n- Uses UI terminology\n- No realistic context\n\n**Good task**: \"You're getting too many email notifications. How would you reduce them?\"\n- Goal-oriented\n- User's language\n- Realistic motivation\n\n### Task Scenario Template\n\n```\nSCENARIO: [Context that makes the task realistic]\nGOAL: [What the user is trying to accomplish]\nSUCCESS CRITERIA: [How you'll know they succeeded]\n```\n\n### Metrics to Capture\n\n**Effectiveness Metrics**\n- Task success rate (completed \u002F attempted)\n- Error rate (errors \u002F task)\n- Recovery rate (recovered from errors \u002F total errors)\n\n**Efficiency Metrics**\n- Time on task (seconds to completion)\n- Number of steps (compared to optimal path)\n- Help requests (times asked for assistance)\n\n**Satisfaction Metrics**\n- Post-task rating (1-7 scale per task)\n- System Usability Scale (SUS) score\n- Net Promoter Score (NPS)\n- Qualitative feedback themes\n\n### Severity Rating Scale\n\n| Rating | Name | Definition | Action |\n|--------|------|------------|--------|\n| 1 | Cosmetic | Noticed but no impact | Fix if time permits |\n| 2 | Minor | Slight difficulty, recovered easily | Fix in next release |\n| 3 | Major | Significant difficulty, delayed success | Fix before release |\n| 4 | Critical | Prevented task completion | Must fix immediately |\n\n## Synthesis and Reporting\n\n### Affinity Mapping Process\n\n**1. Gather Raw Data**\n- Write each observation on a separate note\n- Include quotes, behaviors, and pain points\n- One insight per note\n\n**2. Cluster Related Notes**\n- Group similar observations together\n- Don't force categories, let them emerge\n- Move notes as patterns become clear\n\n**3. Name the Clusters**\n- Create descriptive labels for each group\n- Labels should capture the theme\n- Higher-level groups may emerge\n\n**4. Identify Patterns**\n- What themes appear across multiple participants?\n- What surprises challenge assumptions?\n- What opportunities become clear?\n\n### Research Report Structure\n\n```\nRESEARCH REPORT: [Study Name]\n\nEXECUTIVE SUMMARY\n- Research objective\n- Methods used\n- Key findings (3-5 bullets)\n- Recommended actions\n\nMETHODOLOGY\n- Research questions\n- Participant criteria and recruitment\n- Methods and sample size\n- Limitations\n\nKEY FINDINGS\nFinding 1: [Title]\n- Evidence: What we observed\n- Impact: Why it matters\n- Quote: \"Supporting verbatim\"\n\nFinding 2: [Title]\n...\n\nRECOMMENDATIONS\n- Priority 1: [Action] - Addresses [finding]\n- Priority 2: [Action] - Addresses [finding]\n- Priority 3: [Action] - Addresses [finding]\n\nNEXT STEPS\n- Immediate actions\n- Further research needed\n- Stakeholder follow-up\n\nAPPENDIX\n- Participant details (anonymized)\n- Full data sets\n- Methodology details\n```\n\n### Presenting Findings\n\n**Lead with insights, not methodology**\n- Start with what you learned, not how you learned it\n- Save methodology details for appendix\n\n**Use participant voices**\n- Include direct quotes that bring findings to life\n- Video clips are more powerful than text\n\n**Connect to business outcomes**\n- Tie findings to metrics stakeholders care about\n- Quantify impact where possible\n\n**Provide clear recommendations**\n- Don't just report problems, suggest solutions\n- Prioritize by impact and feasibility\n\n## Best Practices\n\n- Recruit participants who actually face the problem you're solving\n- Focus on understanding behavior, not validating your ideas\n- Look for patterns across participants, not individual opinions\n- Always observe what users do, not just what they say\n- Use multiple methods to triangulate findings\n- Create lightweight deliverables that teams will actually use\n- Involve stakeholders in research to build empathy\n- Measure research impact through design decisions influenced\n\n## References\n\n- `templates\u002Fresearch-plan-template.md` - Planning template for research studies\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002F_collections\u002Fplugins\u002Fteam\u002Fskills\u002Fdesign\u002Fuser-insight-synthesis",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill user-insight-synthesis",{"tool":68,"command":69},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill user-insight-synthesis",{"tool":71,"command":72},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill user-insight-synthesis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fplugins\u002Fteam\u002Fskills\u002Fdesign\u002Fuser-insight-synthesis\u002FSKILL.md",true,[76],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"templates\u002Fresearch-plan-template.md","REFERENCE","参考文档",5877,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fplugins\u002Fteam\u002Fskills\u002Fdesign\u002Fuser-insight-synthesis\u002Ftemplates\u002Fresearch-plan-template.md",[83,100,133,158,180,200],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":92,"publishedAt":47},"01M70P17DAD4C1C47NPH6A96EM","xiaolai-methodology","以李笑来(Li Xiaolai)的思考方式、方法论与表达风格,为用户做全方位 1-on-1 教练指导,覆盖创业、赚钱、投资、学习、自学、读书写作、用 AI、以及人生心态与自我管理。当用户提到 \"李笑来\"、\"笑来\"、\"笑来老师\"、\"扮演李笑来\"、\"找笑来聊聊\"、\"笑来怎么看\"、\"xiaolai\"、\"把时间当作朋友\"、\"通往财富自由之路\"、\"定投改变命运\"、\"韭菜的自我修养\"、\"自学是门手艺\"、\"让时间陪你慢慢变富\"、\"七年就是一辈子\"、\"元认知\"、\"活在未来\"、\"复利\u002F长期主义\"、\"践行\"、\"痴迷改进\"、\"个人商业模式\u002F出售时间\"、\"睡后收入\"、\"定投\"、\"财富自由\"、\"操作系统升级\"、\"最少必要知识\"、\"北极星提示词\"、\"用 AI 该怎么学\u002F思考\" 等任一触发词,或当用户带着关于创业\u002F赚钱\u002F投资\u002F学习\u002F职业\u002F重大人生决策的困惑、希望被人用笑来式的「逻辑 + 大白话 + 类比 + 重新定义 + 践行导向」来点醒和指导时,自动进入李笑来教练模式。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fxiaolai-methodology\u002FSKILL.md",[89],{"categoryNo":90,"categoryName":91,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",[93,94,95,96,97,98,99],"methodology","xiaolai","xiaolai methodology","朋友","投资","writing","收入",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":114,"publishedAt":47},"01M70P13NB9YP7ACJR1S861CDS","zread","Produce and consume a wiki-style knowledge base for a code repository via the `zread` CLI and its on-disk output under `.\u002F.zread\u002Fwiki\u002F`. Use this skill whenever the user wants to understand, onboard onto, explore, summarize, map, or get an overview of an unfamiliar codebase; asks for architecture docs, a project wiki, a repo walkthrough, module\u002Fpackage explanations, or \"what does this repo do\"; wants to generate, regenerate, resume, browse, or serve code documentation locally; or mentions zread \u002F zread.ai directly. Also use it proactively before diving into a large unknown repo — if `.\u002F.zread\u002Fwiki\u002Fcurrent` exists, read the generated pages instead of crawling source file-by-file; if it doesn't, consider offering to run `zread generate`. The trigger is the intent (understand a codebase through generated docs), not the literal word \"zread\".","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fzread\u002FSKILL.md",[106,109],{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[102,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,35,130,131,132],"knowledge","wiki","explore","walkthrough","project","get","knowledge base","run","generate","intent","cli","map","documentation","project wiki","disk","code","unknown","generated",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":143,"publishedAt":47},"01M70P10S4SWMZQ8BJAFBFDRW3","youtube","Launch the YouTube Creator Agent to auto-generate videos.\nUse when: user types \u002Fyoutube, wants to create YouTube videos,\ngenerate video content, or upload to YouTube.\nKeywords: youtube, video, 视频, 创作视频, 发布视频","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[139,140],{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":141,"categoryName":142,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000036","内容创作者",[135,29,144,145,146,147,148,149,123,150,151,152,38,153,154,155,156,157],"content","视频","creator","generate video","videos","launch","video content","create","upload","use","auto","types","Video","创作",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":165,"publishedAt":47},"01M70P0YE95D8BACZCGV8BK90K","youtube-script-sync","Sync, update, or optimize Tony's GetNote knowledge base `Youtube视频逐字稿` by turning each parent recording or first-person idea note into an idempotent child note containing a directly recordable YouTube long-video or Shorts script. Use when the user says “更新\u002F同步\u002F优化 Youtube视频逐字稿知识库”, or says “更新\u002F同步\u002F优化该知识库” while this knowledge base is the active context.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-script-sync\u002FSKILL.md",[164],{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},[166,167,135,168,169,156,170,171,172,173,174,175,176,177,121,178,38,153,115,179],"sync","script","youtube script sync","recording","shorts","first","base","person","update","active","child","optimize","idempotent","long",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":190,"publishedAt":47},"01M70P0WMV5XT0EEC0N445PW07","writing-skills","How to write SKILL.md files that trigger reliably and teach effectively. Use when creating, improving, or reviewing Claude Code skills.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-skills\u002FSKILL.md",[186,187,188,189],{"categoryNo":90,"categoryName":91,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},{"categoryNo":141,"categoryName":142,"taxonomyType":112,"taxonomyTypeDesc":113},[191,98,192,193,194,195,130,38,153,196,197,198,199],"writing skills","how","teach","write skill","write","claude code skills","files","how to","trigger",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":208,"publishedAt":47},"01M70P0SJFR4YVJQBGMHKGSKXT","writing-rules","How to write .claude\u002Frules\u002F files that Claude actually follows. Use when creating, improving, or reviewing project rules.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-rules\u002FSKILL.md",[206,207],{"categoryNo":90,"categoryName":91,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":141,"categoryName":142,"taxonomyType":112,"taxonomyTypeDesc":113},[209,98,210,119,211,197,38,192,195,153,198],"Rules","writing rules","project rules"]