ux-researcher-designer by alirezarezvani/claude-skills
npx skills add https://github.com/alirezarezvani/claude-skills --skill ux-researcher-designer根据研究数据生成用户画像,创建旅程地图,规划可用性测试,并将研究发现综合为可操作的设计建议。
当您需要时使用此技能:
情境: 您拥有用户数据(分析、调查、访谈),需要创建一个基于研究的画像。
步骤:
所需格式 (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"]
}
]
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
2. 运行画像生成器
# 人类可读输出
python scripts/persona_generator.py
# 用于集成的 JSON 输出
python scripts/persona_generator.py json
3. 审查生成的组件
| 组件 | 检查内容 |
|---|---|
| 原型 | 是否与数据模式匹配? |
| 人口统计信息 | 是否源自实际数据? |
| 目标 | 是否具体且可操作? |
| 痛点 | 是否包含频率计数? |
| 设计启示 | 设计师能否据此采取行动? |
验证画像
参考: 查看 references/persona-methodology.md 了解有效性标准
情境: 您需要为特定目标可视化端到端的用户体验。
步骤:
| 元素 | 描述 |
|---|---|
| 画像 | 哪种用户类型 |
| 目标 | 他们试图实现什么 |
| 起点 | 触发旅程开始的事件 |
| 终点 | 成功标准 |
| 时间范围 | 小时/天/周 |
数据源:
* 用户访谈(询问“请带我走一遍...”)
* 会话录制
* 分析数据(漏斗、流失点)
* 支持工单
3. 映射各阶段
典型的 B2B SaaS 阶段:
Awareness → Evaluation → Onboarding → Adoption → Advocacy
4. 为每个阶段填充层级
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?
5. 识别机会
优先级分数 = 频率 × 严重性 × 可解决性
references/journey-mapping-guide.md 获取模板情境: 您需要使用真实用户验证一个设计。
步骤:
将模糊目标转化为可测试的问题:
| 模糊 | 可测试 |
|---|---|
| “它好用吗?” | “用户能否在 <3 分钟内完成结账?” |
| “用户喜欢它吗?” | “用户会选择设计 A 还是 B?” |
| “它合理吗?” | “用户能否在没有提示的情况下找到设置?” |
| 方法 | 参与者 | 时长 | 最适合 |
|---|---|---|---|
| 主持式远程测试 | 5-8 | 45-60 分钟 | 深度洞察 |
| 非主持式远程测试 | 10-20 | 15-20 分钟 | 快速验证 |
| 游击测试 | 3-5 | 5-10 分钟 | 快速反馈 |
良好的任务格式:
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."
任务进展:热身 → 核心 → 次要 → 边缘情况 → 自由探索
| 指标 | 目标 |
|---|---|
| 完成率 | >80% |
| 任务耗时 | <2× 预期 |
| 错误率 | <15% |
| 满意度 | >4/5 |
准备主持人指南
参考: 查看 references/usability-testing-frameworks.md 获取完整指南
情境: 您拥有原始研究数据(访谈、调查、观察),需要可操作的见解。
步骤:
标记每个数据点:
* `[GOAL]` \- 他们想要实现什么
* `[PAIN]` \- 什么让他们感到沮丧
* `[BEHAVIOR]` \- 他们实际做什么
* `[CONTEXT]` \- 他们在何时/何地使用产品
* `[QUOTE]` \- 用户的直接话语
2. 聚类相似模式
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)
3. 计算细分规模
| 聚类 | 用户数 | 百分比 | 可行性 |
|---|---|---|---|
| 高级用户 | 18 | 36% | 主要画像 |
| 商业用户 | 15 | 30% | 主要画像 |
| 普通用户 | 12 | 24% | 次要画像 |
针对每个主题:
* 发现陈述
* 支持证据(引述、数据)
* 频率(X/Y 参与者)
* 业务影响
* 建议
5. 确定机会优先级
| 因素 | 评分 1-5 |
|---|---|
| 频率 | 这种情况多久发生一次? |
| 严重性 | 它造成多大伤害? |
| 广度 | 影响多少用户? |
| 可解决性 | 我们能解决这个问题吗? |
references/persona-methodology.md 获取分析框架根据用户研究数据生成数据驱动的画像。
| 参数 | 值 | 默认值 | 描述 |
|---|---|---|---|
| format | (none), json | (none) | 输出格式 |
示例输出:
============================================================
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
生成的原型:
| 原型 | 信号 | 设计重点 |
|---|---|---|
| power_user | 每日使用,10+ 功能 | 效率,定制化 |
| casual_user | 每周使用,3-5 功能 | 简洁性,引导 |
| business_user | 工作场景,团队使用 | 协作,报告 |
| mobile_first | 移动设备为主 | 触摸,离线,速度 |
输出组件:
| 组件 | 描述 |
|---|---|
| demographics | 年龄范围,地点,职业,技术水平 |
| psychographics | 动机,价值观,态度,生活方式 |
| behaviors | 使用模式,功能偏好 |
| needs_and_goals | 主要,次要,功能性,情感性 |
| frustrations | 痛点及证据 |
| scenarios | 上下文使用场景 |
| design_implications | 可操作的建议 |
| data_points | 样本量,置信度 |
| 问题类型 | 最佳方法 | 样本量 |
|---|---|---|
| “用户做什么?” | 分析,观察 | 100+ 事件 |
| “他们为什么这样做?” | 访谈 | 8-15 用户 |
| “他们能做得怎么样?” | 可用性测试 | 5-8 用户 |
| “他们更喜欢什么?” | 调查,A/B 测试 | 50+ 用户 |
| “他们感觉如何?” | 日记研究,访谈 | 10-15 用户 |
| 样本量 | 置信度 | 使用场景 |
|---|---|---|
| 5-10 用户 | 低 | 探索性 |
| 11-30 用户 | 中 | 方向性 |
| 31+ 用户 | 高 | 生产环境 |
| 严重性 | 定义 | 行动 |
|---|---|---|
| 4 - 严重 | 阻止任务完成 | 立即修复 |
| 3 - 重大 | 显著困难 | 发布前修复 |
| 2 - 轻微 | 导致犹豫 | 可能时修复 |
| 1 - 外观 | 注意到但无问题 | 低优先级 |
| 类型 | 示例 | 用于 |
|---|---|---|
| Context | "Walk me through your typical day" | 了解环境 |
| Behavior | "Show me how you do X" | 观察实际行为 |
| Goals | "What are you trying to achieve?" | 揭示动机 |
| Pain | "What's the hardest part?" | 识别痛点 |
| Reflection | "What would you change?" | 产生想法 |
references/ 目录下的详细参考指南:
| 文件 | 内容 |
|---|---|
persona-methodology.md | 有效性标准,数据收集,分析框架 |
journey-mapping-guide.md | 映射过程,模板,机会识别 |
example-personas.md | 3 个完整的画像示例及数据 |
usability-testing-frameworks.md | 测试规划,任务设计,分析 |
每周安装数
203
仓库
GitHub 星标
2.8K
首次出现
Jan 20, 2026
安全审计
安装于
claude-code172
opencode153
gemini-cli151
codex143
cursor133
github-copilot129
Generate user personas from research data, create journey maps, plan usability tests, and synthesize research findings into actionable design recommendations.
Use this skill when you need to:
Situation: You have user data (analytics, surveys, interviews) and need to create a research-backed persona.
Steps:
Required format (JSON):
[
{
"user_id": "user_1",
"age": 32,
"usage_frequency": "daily",
"features_used": ["dashboard", "reports", "export"],
"primary_device": "desktop",
"usage_context": "work",
"tech_proficiency": 7,
"pain_points": ["slow loading", "confusing UI"]
}
]
2. Run persona generator
# Human-readable output
python scripts/persona_generator.py
# JSON output for integration
python scripts/persona_generator.py json
3. 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
Reference: See references/persona-methodology.md for validity criteria
Situation: You need to visualize the end-to-end user experience for a specific goal.
Steps:
| Element | Description |
|---|---|
| Persona | Which user type |
| Goal | What they're trying to achieve |
| Start | Trigger that begins journey |
| End | Success criteria |
| Timeframe | Hours/days/weeks |
Sources:
* User interviews (ask "walk me through...")
* Session recordings
* Analytics (funnel, drop-offs)
* Support tickets
3. Map the stages
Typical B2B SaaS stages:
Awareness → Evaluation → Onboarding → Adoption → Advocacy
4. 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?
5. Identify opportunities
Priority Score = Frequency × Severity × Solvability
references/journey-mapping-guide.md for templatesSituation: You need to validate a design with real users.
Steps:
Transform vague goals into testable questions:
| Vague | Testable |
|---|---|
| "Is it easy to use?" | "Can users complete checkout in <3 min?" |
| "Do users like it?" | "Will users choose Design A or B?" |
| "Does it make sense?" | "Can users find settings without hints?" |
| Method | Participants | Duration | Best For |
|---|---|---|---|
| Moderated remote | 5-8 | 45-60 min | Deep insights |
| Unmoderated remote | 10-20 | 15-20 min | Quick validation |
| Guerrilla | 3-5 | 5-10 min | Rapid feedback |
Good task format:
SCENARIO: "Imagine you're planning a trip to Paris..."
GOAL: "Book a hotel for 3 nights in your budget."
SUCCESS: "You see the confirmation page."
Task progression: Warm-up → Core → Secondary → Edge case → Free exploration
| Metric | Target |
|---|---|
| Completion rate | >80% |
| Time on task | <2× expected |
| Error rate | <15% |
| Satisfaction | >4/5 |
Prepare moderator guide
Reference: See references/usability-testing-frameworks.md for full guide
Situation: You have raw research data (interviews, surveys, observations) and need actionable insights.
Steps:
Tag each data point:
* `[GOAL]` \- What they want to achieve
* `[PAIN]` \- What frustrates them
* `[BEHAVIOR]` \- What they actually do
* `[CONTEXT]` \- When/where they use product
* `[QUOTE]` \- Direct user words
2. 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)
3. Calculate segment sizes
| Cluster | Users | % | Viability |
|---|---|---|---|
| Power Users | 18 | 36% | Primary persona |
| Business Users | 15 | 30% | Primary persona |
| Casual Users | 12 | 24% | Secondary persona |
For each theme:
* Finding statement
* Supporting evidence (quotes, data)
* Frequency (X/Y participants)
* Business impact
* Recommendation
5. 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? |
references/persona-methodology.md for analysis frameworkGenerates data-driven personas from user research data.
| Argument | Values | Default | Description |
|---|---|---|---|
| format | (none), json | (none) | Output format |
Sample Output:
============================================================
PERSONA: Alex the Power User
============================================================
📝 A daily user who primarily uses the product for work purposes
Archetype: Power User
Quote: "I need tools that can keep up with my workflow"
👤 Demographics:
• Age Range: 25-34
• Location Type: Urban
• Tech Proficiency: Advanced
🎯 Goals & Needs:
• Complete tasks efficiently
• Automate workflows
• Access advanced features
😤 Frustrations:
• Slow loading times (14/20 users)
• No keyboard shortcuts
• Limited API access
💡 Design Implications:
→ Optimize for speed and efficiency
→ Provide keyboard shortcuts and power features
→ Expose API and automation capabilities
📈 Data: Based on 45 users
Confidence: High
Archetypes Generated:
| Archetype | Signals | Design Focus |
|---|---|---|
| power_user | Daily use, 10+ features | Efficiency, customization |
| casual_user | Weekly use, 3-5 features | Simplicity, guidance |
| business_user | Work context, team use | Collaboration, reporting |
| mobile_first | Mobile primary | Touch, offline, speed |
Output Components:
| Component | Description |
|---|---|
| demographics | Age range, location, occupation, tech level |
| psychographics | Motivations, values, attitudes, lifestyle |
| behaviors | Usage patterns, feature preferences |
| needs_and_goals | Primary, secondary, functional, emotional |
| frustrations | Pain points with evidence |
| scenarios | Contextual usage stories |
| design_implications | Actionable recommendations |
| data_points | Sample size, confidence level |
| Question Type | Best Method | Sample Size |
|---|---|---|
| "What do users do?" | Analytics, observation | 100+ events |
| "Why do they do it?" | Interviews | 8-15 users |
| "How well can they do it?" | Usability test | 5-8 users |
| "What do they prefer?" | Survey, A/B test | 50+ users |
| "What do they feel?" | Diary study, interviews | 10-15 users |
| Sample Size | Confidence | Use Case |
|---|---|---|
| 5-10 users | Low | Exploratory |
| 11-30 users | Medium | Directional |
| 31+ users | High | Production |
| Severity | Definition | Action |
|---|---|---|
| 4 - Critical | Prevents task completion | Fix immediately |
| 3 - Major | Significant difficulty | Fix before release |
| 2 - Minor | Causes hesitation | Fix when possible |
| 1 - Cosmetic | Noticed but not problematic | Low priority |
| Type | Example | Use For |
|---|---|---|
| Context | "Walk me through your typical day" | Understanding environment |
| Behavior | "Show me how you do X" | Observing actual actions |
| Goals | "What are you trying to achieve?" | Uncovering motivations |
| Pain | "What's the hardest part?" | Identifying frustrations |
| Reflection | "What would you change?" | Generating ideas |
Detailed reference guides in references/:
| File | Content |
|---|---|
persona-methodology.md | Validity criteria, data collection, analysis framework |
journey-mapping-guide.md | Mapping process, templates, opportunity identification |
example-personas.md | 3 complete persona examples with data |
usability-testing-frameworks.md | Test planning, task design, analysis |
Weekly Installs
203
Repository
GitHub Stars
2.8K
First Seen
Jan 20, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
claude-code172
opencode153
gemini-cli151
codex143
cursor133
github-copilot129
推荐与联盟计划设计优化指南:病毒式增长营销策略、客户推荐计划、联盟营销
27,600 周安装
剪映AI视频生成自动化脚本 - 基于Playwright的Seedance 2.0模型文生图/图生视频工具
204 周安装
社交媒体内容策略指南:LinkedIn、Twitter、Instagram、TikTok、Facebook平台优化与模板
204 周安装
Python statsmodels 统计建模与计量经济学分析库 - 回归、时间序列、假设检验
204 周安装
Azure PostgreSQL 无密码身份验证配置指南:Entra ID 迁移与访问管理
34,800 周安装
阅读清单管理器:基于Zettelkasten和间隔重复的智能阅读追踪与知识管理工具
Proposal Designer 提案设计师:创建视觉提案,提升用户体验与设计系统