关于 ux-design
ux-design 是用于设计和评估用户体验的方法技能,面向规划流程、界面和可用性的产品团队。它结合 UX 原则、分阶段设计流程、评审检查项和设计文档模板。
主要功能
- 01应用以用户为中心的 UX 原则
- 02组织从研究到验证的流程
- 03编写流程图和线框文档
- 04评估可用性与无障碍性
- 05撰写 UX 文案和错误提示
适用场景
- 01规划新功能的用户体验
- 02梳理用户流程
- 03评估界面的可用性
- 04撰写界面文案和错误提示
安装
复制下面的命令,在终端中运行。
$
npx skills add https:/ / github.com/ civitai/ civitai --skill ux-design安装后在 Claude Code 中输入/ux-design确认已加载。
详细介绍
UX 设计技能
一套全面的 UX 设计方法论,用于打造以用户为中心的产品。在设计用户体验、创建流程、评估可用性或获取外部 UX 反馈时,请使用此技能。
UX 核心原则
1. 待完成任务(JTBD)
关注用户想要完成的事情,而非功能。
Template:
When [situation], I want to [motivation], so I can [expected outcome].
Example:
When I have a character I love, I want to generate comic panels with them,
so I can tell stories without learning to draw.
2. 渐进式呈现
每一步只展示所需内容。随着用户的需求逐步呈现复杂功能。
Level 1: Core action (upload, generate)
Level 2: Basic options (style, description)
Level 3: Advanced controls (parameters, fine-tuning)
Level 4: Expert features (custom LoRAs, composition)
3. 优先识别,而非回忆
用户应该能识别选项,而不是记住命令。
Bad: "Enter LoRA weight (0.0-1.0)"
Good: [Slider with preview] "Style strength: Subtle ←→ Strong"
4. 防止错误 > 从错误中恢复
设计应防止错误,而不仅仅是妥善处理错误。
Example: Disable "Generate" until character is locked, not "Error: No character"
5. 即时反馈
每个操作都应在 100ms 内得到可见响应。
- Button press → visual state change
- Upload → progress indicator
- Generation → status updates ("Analyzing face...", "Applying style...")
UX 设计流程
阶段 1:研究与探索
1. User Interviews
- Who are the target users?
- What are they trying to accomplish?
- What do they currently use? What's frustrating?
- What would "magic" look like?
2. Competitive Analysis
- What do competitors do well?
- Where do they fail?
- What's the table stakes?
- What's the differentiation opportunity?
3. Jobs-to-be-Done Mapping
- List all user jobs
- Prioritize by frequency × importance
- Identify underserved jobs
4. User Personas
- 2-3 primary personas
- Goals, frustrations, context
- Technical proficiency level
阶段 2:信息架构
1. Content Inventory
- What content/features exist?
- How do they relate?
2. Site/App Map
- Hierarchy of screens/pages
- Navigation structure
3. User Flows
- Primary task flows (happy path)
- Error/edge case flows
- Entry and exit points
阶段 3:交互设计
1. Wireframes
- Low-fidelity layouts
- Component placement
- Information hierarchy
2. Interaction Patterns
- How does each element behave?
- State transitions
- Micro-interactions
3. Responsive Considerations
- Desktop, tablet, mobile breakpoints
- Touch vs mouse interactions
阶段 4:视觉设计
1. Design System
- Typography
- Color palette
- Spacing/grid
- Component library
2. High-Fidelity Mockups
- Pixel-perfect designs
- All states (empty, loading, error, success)
- Dark/light mode if applicable
3. Prototypes
- Interactive clickable prototypes
- Animation/transition specs
阶段 5:验证
1. Usability Testing
- Task completion rates
- Time on task
- Error rates
- User satisfaction
2. A/B Testing
- Hypothesis-driven experiments
- Statistical significance
3. Analytics
- Funnel analysis
- Drop-off points
- Feature usage
UX 交付物
用户流程图格式
[Entry Point] → (Decision) → [Screen/State] → [Exit/Success]
↓
[Alternative Path]
Legend:
[ ] = Screen or state
( ) = Decision point
→ = Flow direction
--- = Optional path
线框图注释格式
┌─────────────────────────────────────────┐
│ [Component Name] │
│ ┌─────────────────────────────────────┐│
│ │ ││
│ │ ① Element description ││
│ │ ② Interaction behavior ││
│ │ ││
│ └─────────────────────────────────────┘│
│ │
│ Notes: │
│ - Accessibility considerations │
│ - Edge cases │
│ - Mobile behavior │
└─────────────────────────────────────────┘
① Numbered annotations reference specific elements
② Describe behavior, not just appearance
状态图格式
State Machine: [Component Name]
States:
- idle: Default state
- loading: Async operation in progress
- success: Operation completed
- error: Operation failed
Transitions:
idle → loading: [trigger: user action]
loading → success: [trigger: operation complete]
loading → error: [trigger: operation failed]
error → idle: [trigger: dismiss/retry]
开展 UX 评审
使用 agent-review 技能,并提供聚焦 UX 的提示词:
# Get UX feedback on a flow
node .claude/skills/agent-review/query.mjs -m opus \
-s "You are a senior UX designer with 15 years of experience in consumer products. Focus on usability, accessibility, and emotional design." \
-f docs/ux-flow.md \
"Review this user flow for usability issues and opportunities"
# Evaluate information architecture
node .claude/skills/agent-review/query.mjs -m opus \
-s "You are an information architect specializing in complex creative tools. Prioritize discoverability and progressive complexity." \
-f docs/site-map.md \
"Evaluate this information architecture for a comic creation tool"
# Get feedback on wireframes
node .claude/skills/agent-review/query.mjs -m opus \
-s "You are a UX designer who specializes in creative tools like Figma, Canva, and Adobe products. Focus on efficiency for power users while maintaining approachability." \
-f docs/wireframes.md \
"Critique these wireframes for a comic panel generator"
UX 启发式检查清单
使用此清单评估设计:
Nielsen 的 10 项可用性启发式原则
- 系统状态的可见性:用户始终知道当前发生了什么
- 与现实世界相符:使用熟悉的语言和概念
- 用户控制与自由:易于撤销、退出和返回
- 一致性与标准:相同操作的行为方式一致
- 错误预防:在错误发生前就加以防止
- 识别而非回忆:选项清晰可见,无需记忆
- 灵活性与效率:为专家提供快捷操作,为新手保持简单
- 美观与简约:不包含无关信息
- 帮助用户识别和解决错误:提供清晰且包含解决方案的错误消息
- 帮助与文档:在需要时可供查阅
无障碍访问(WCAG)
- 可感知性:内容可通过所有感官获取
- 可操作性:所有功能均可通过键盘使用
- 可理解性:语言清晰,行为可预测
- 稳健性:兼容辅助技术
情感化设计
- 本能层面:第一印象积极
- 行为层面:使用体验良好且高效
- 反思层面:使用后用户感到自豪或满意
UX 文案指南
微文案原则
1. Be concise: "Upload" not "Click here to upload your files"
2. Be specific: "3 images required" not "Upload images"
3. Be helpful: "Try a front-facing photo" not "Invalid image"
4. Be human: "Almost there!" not "Processing: 80%"
按钮标签
Good: [Create Comic] [Save Draft] [Generate Panel]
Bad: [Submit] [OK] [Go]
Action verbs that describe what happens
错误消息
Format: What happened + Why + How to fix
Example:
"Character not recognized. We couldn't detect a face in your images.
Try uploading photos with a clear, front-facing view."
加载状态
Informative progress, not just spinners:
"Analyzing your character..." (0-30%)
"Learning facial features..." (30-50%)
"Creating style profile..." (50-70%)
"Almost ready..." (70-100%)
输出模板
创建 UX 文档时,请使用以下模板:
用户故事模板
## User Story: [Title]
**As a** [user type]
**I want to** [action]
**So that** [benefit]
### Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
### UX Notes
- Key interaction details
- Edge cases to handle
- Accessibility considerations
屏幕规格模板
## Screen: [Name]
**Purpose:** What this screen accomplishes
**Entry Points:** How users arrive here
**Exit Points:** Where users can go from here
### Layout
[ASCII wireframe or description]
### Components
| Component | Behavior | States |
|-----------|----------|--------|
| Component 1 | Description | idle, hover, active, disabled |
### Interactions
1. When user does X, Y happens
2. ...
### Edge Cases
- Empty state: What shows when no data?
- Error state: What shows on failure?
- Loading state: What shows during async?
### Accessibility
- Keyboard navigation
- Screen reader considerations
- Color contrast
用户流程模板
## Flow: [Name]
**Goal:** What the user accomplishes
**Trigger:** What initiates this flow
**Actors:** Who is involved
### Happy Path
1. Step 1 → [Screen/State]
2. Step 2 → [Screen/State]
3. Success!
### Alternative Paths
- If [condition], then [alternative flow]
### Error Paths
- If [error], show [error state], user can [recovery action]
### Flow Diagram
[ASCII or mermaid diagram]
何时使用此技能
- 新功能设计:编写代码前,先设计体验
- UX 评审:评估现有设计中的可用性问题
- 用户流程梳理:记录用户完成任务的方式
- 线框图设计:创建低保真布局
- 交互设计:定义元素的行为方式
- 可用性评估:对设计进行启发式分析
- UX 文案撰写:编写微文案、错误消息和引导文案
评论
支持 Markdown