ux-sequence-diagram
[UI/UX] Visualizes interaction sequences and system communications as ASCII diagrams. Represents user-system interactions, API call sequences, and event flows. Use when requesting 'sequence diagram', 'interaction flow', or 'API sequence'.
When & Why to Use This Skill
The UX Sequence Diagram skill is a specialized tool designed to generate professional ASCII-based visualizations of system interactions and communication flows. It enables developers and designers to transform complex logic into readable diagrams, covering user-system touchpoints, API call sequences, and event-driven architectures. By utilizing standardized ASCII symbols for synchronous and asynchronous messaging, it provides a portable and efficient way to document software architecture directly within text-based environments.
Use Cases
- User-System Interaction Mapping: Visualizing the step-by-step journey of a user through a UI and the corresponding system responses to ensure a seamless user experience.
- API Sequence Documentation: Illustrating the flow of requests and responses between frontend clients, backend services, and third-party APIs for better technical alignment.
- Event-Driven Architecture Design: Representing complex asynchronous event flows and message-based communications between microservices or system components.
- Technical Documentation & PRs: Generating lightweight, text-friendly diagrams that can be easily embedded in Markdown files, GitHub Pull Requests, or code comments for improved team collaboration.
| name | ux-sequence-diagram |
|---|---|
| description | "[UI/UX] Visualizes interaction sequences and system communications as ASCII diagrams. Represents user-system interactions, API call sequences, and event flows. Use when requesting 'sequence diagram', 'interaction flow', or 'API sequence'." |
UX Sequence Diagram
A skill that visualizes interaction sequences and system communications as ASCII diagrams.
When to Use
- Defining user-system interaction sequences
- Documenting API call sequences
- Representing event flows between components
- Designing asynchronous operation sequences
Sequence Diagram Symbols
Participants
┌───────┐ ┌───────┐ ┌───────┐
│ User │ │ UI │ │Server │
└───┬───┘ └───┬───┘ └───┬───┘
│ │ │
Message Types
────────→ Sync Request
← ─ ─ ─ ─ Sync Response
- - - - → Async Request
═══════→ Critical Message
──────X Failed/Cancelled
Sequence Patterns
Basic Request-Response
┌───────┐ ┌───────┐ ┌───────┐
│ User │ │ UI │ │Server │
└───┬───┘ └───┬───┘ └───┬───┘
│ │ │
│ Click Button │ │
│─────────────────→│ │
│ │ API Request │
│ │─────────────────→│
│ │ Response Data │
│ │← ─ ─ ─ ─ ─ ─ ─ ─ │
│ Update View │ │
│← ─ ─ ─ ─ ─ ─ ─ ─ │ │
↓ ↓ ↓
Constraints
- Participants arranged left-to-right, closest to user first
- Time flows top-to-bottom
- Clearly distinguish sync/async messages