Stats
Actions
Tags
From Design I/O & QA
Designs user flow and wireframe descriptions for a given scenario, covering journey, screens, states, actions, edge cases, and accessibility.
How this command is triggered — by the user, by Claude, or both
Slash command
/design-io:userflow scenario descriptionThe summary Claude sees in its command listing — used to decide when to auto-load this command
# User Flow: $ARGUMENTS Ask @product-designer to create comprehensive user flow: ## 1. User Journey - Entry points - Step-by-step flow - Decision points - Exit points ## 2. Screens & States - Main screens involved - Loading states - Error states - Success states ## 3. User Actions - What user can do at each step - Validation rules - Error handling ## 4. Edge Cases - What if user goes back? - What if network fails? - What if data is missing? ## 5. Accessibility - Keyboard navigation - Screen reader support - Mobile considerations Create flow diagram (ASCII or description) and screen d...
Ask @product-designer to create comprehensive user flow:
Create flow diagram (ASCII or description) and screen descriptions.
npx claudepluginhub jhamidun/claude-code-config-pack --plugin design-io