# UX Flow Critic

> Use this skill when creating or changing pages, forms, modals, dashboards, tables, filters, navigation, or any user-facing flow that impacts clarity, friction, or usability.

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

---


# UX Flow Critic

## Goal
Improve real product usability by reducing friction, confusion, and cognitive load.

## When to use
Use this skill for:
- pages
- forms
- tables
- filters
- dashboards
- modals
- onboarding steps
- status and feedback flows
- error and success states

## Core mindset
UX is not decoration.
Prioritize clarity, confidence, and ease of use.

## Always verify
- the main action is obvious
- the user understands what to do next
- labels and copy are clear
- the flow has no unnecessary steps
- loading, empty, success, and error states exist
- the interface does not force the user to remember too much
- hierarchy guides attention properly
- the user can recover from mistakes
- forms and tables are not visually or cognitively overloaded

## Review questions
- What is the primary task of this screen?
- Is the main CTA obvious?
- Is anything competing with the main action?
- Does the user get clear feedback?
- Are there hidden assumptions?
- Can a non-technical user understand this quickly?

## Anti-patterns to avoid
- too many actions with similar weight
- unclear labels
- validation only after submission when early feedback would help
- tables without meaningful filters or empty states
- modals used for flows that need more space
- interface complexity added without real value

## Output format
Always provide:
1. Main UX risks
2. Specific flow or UI improvements
3. Expected usability impact
4. Any tradeoff introduced
5. Plain-language summary for non-technical readers