# UX Flow

> Define user journey, screens, states, and interactions before coding.

- Skill: `irwebtools/ux-flow` (Agent Skill, multi-file: 7 files)
- Install (CLI): `npx skillmds@latest add irwebtools/ux-flow`
- Raw SKILL.md: https://api.skillmd.com/api/skills/irwebtools/ux-flow/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: irwebtools (https://skillmd.com/u/irwebtools)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/irwebtools/ux-flow

---


# 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

1. Map the primary user journey end to end.
2. List screens or steps in order.
3. Define loading, empty, error, success, and permission states.
4. 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.