irwebtools ux-flow
When to use
Use when the task matches: ux-flow, user journey, screen flow.
Purpose
Agree experience behavior so POC implementation follows Product intent.
Inputs
- Feature brief
- User stories
- Acceptance criteria
Process
- Map the primary user journey end to end.
- List screens or steps in order.
- Define loading, empty, error, success, and permission states.
- Confirm journey with Product before architecture or POC.
Outputs
- User journey
- Screen flow
- States
- Interactions
Verification
- Confirm each output exists and is reviewable.
- Keep Product validation and engineering verification distinct.
- Do not claim completion without evidence.
Restrictions
- Do not start React coding in this skill.
- Do not invent a full design system without need.
- Do not skip Product confirmation on ambiguous flows.