| name | draft |
| description | Draft a user experience specification for a requested CoC feature. Use when planning new features, designing user flows, or creating UX specs for the CoC dashboard, CLI, server, or Node packages. |
Draft UX Specification
Draft a user experience specification for the requested feature or ask. Include:
-
User Story: Who is the user and what problem are they solving?
-
Entry Points: How does the user discover and access this feature?
- Dashboard tabs, routes, or panels
- CLI commands
- Context menus (right-click)
- Keyboard shortcuts
- Lists, tables, sidebars, or detail views
- Settings
-
User Flow: Step-by-step walkthrough of the primary workflow
- Initial state
- User actions
- System responses
- Success state
-
Edge Cases & Error Handling:
- What happens when things go wrong?
- How are errors communicated to the user?
- Recovery paths
-
Visual Design Considerations:
- Icons needed
- List, table, sidebar, or detail-view representation
- Notifications/status indicators
- Any dashboard or editor requirements
-
Settings & Configuration:
- What should be configurable?
- Sensible defaults
-
Discoverability: How will users learn about this feature?
Focus on clarity and simplicity. Prefer conventions already established in CoC. No code details.