AgentSkillsCN

ux-flow-creation

按照 UX-FLOW 模板生成用户体验流程文档。适用于设计 UI 流程、记录用户旅程,或当用户要求生成 UX 文档时使用。

SKILL.md
--- frontmatter
name: ux-flow-creation
description: "Generate user experience flow documentation following the UX-FLOW template. Use when designing UI flows, documenting user journeys, or when the user asks for UX documentation."
event: ux-design
auto_trigger: false
version: "1.0.0"
last_updated: "2026-01-26"

# Inputs/Outputs
inputs:
  - feature_name
  - user_personas
  - screen_list
  - interaction_flows
  - related_api_endpoints
output: ux_flow_document
output_format: "Markdown UX doc (06-UX-FLOW-TEMPLATE.md)"
output_path: "docs/technical/frontend/ux-flows/"

# Auto-Trigger Rules
auto_invoke:
  events:
    - "ux-design"
    - "feature-ui-request"
  conditions:
    - "user requests UX documentation"
    - "new feature needs user flows"

# Validation
validation_rules:
  - "must include user personas"
  - "must have screen mockups or wireframes"
  - "interactions must be documented"
  - "accessibility considerations included"

# Chaining
chain_after: []
chain_before: [doc-index-update, related-docs-sync]

# Agent Association
called_by: ["@Frontend"]
mcp_tools:
  - mcp_payment-syste_search_full_text
  - read_file

UX Flow Creation Skill

Purpose: Generate comprehensive user experience documentation following the project template. Creates consistent UX docs that link to related API and feature documentation.

Trigger

When: User requests UX documentation OR new feature needs UI design Context Needed: Feature requirements, user personas, screen designs MCP Tools: mcp_payment-syste_search_full_text, read_file

Required Sections

markdown
# [Feature] - UX Flow

## User Personas

- Primary: [persona]
- Secondary: [persona]

## Screens

1. [Screen Name]
   - Purpose: ...
   - Key elements: ...
   - Interactions: ...

## User Journeys

### Happy Path

1. User does X
2. System responds with Y
3. User sees Z

### Error Handling

- Scenario: ...
- Display: ...
- Recovery: ...

Screen Documentation Format

markdown
### Screen: [Name]

**Purpose:** [What this screen accomplishes]

**Entry Points:**

- From: [Previous screen]
- Trigger: [User action]

**Key Elements:**
| Element | Type | Behavior |
|:--------|:-----|:---------|
| [name] | button | [action] |

**Exit Points:**

- To: [Next screen]
- Condition: [What triggers navigation]

Accessibility Checklist

  • Keyboard navigation
  • Screen reader support
  • Color contrast (WCAG AA)
  • Touch targets (44x44px min)
  • Focus indicators

Reference