Skip to main content
skill CX Codex

state-ux-flow-builder — Claude Code skill

The state-ux-flow-builder skill structures loading, error, empty, and success states for data-driven screens. Use it when a UI flow has several views or state transitions.

MIT 264 installs ★ 64 updated 2026-01-12

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add patricio0312rev/skills --skill state-ux-flow-builder -a claude-code
Open on GitHub

What state-ux-flow-builder does

state-ux-flow-builder lays out a data-fetching sequence that covers loading first, then errors, empty results, and the successful data view. Its guidance favors loading skeletons over spinners, adds a retry action for failed requests, and gives empty screens a clear next action.

The skill also covers error boundaries, ARIA live regions, optimistic changes with rollback, and progressive content rendering. It suggests XState when a flow contains many states and transitions; simpler cases can use useState or server-side state handling. Without an error boundary, render failures will sit outside this shared UI flow.

What it helps with

  • design all data-fetching states for a screen
  • add a retry path after a failed request
  • replace a loading spinner with a skeleton view
  • model multi-step UI transitions with XState
  • give an empty result screen a useful action

Example prompts for the agent

  • Design the OrdersPage data flow with a loading skeleton, a retryable error state, and an empty result view.
  • Add an optimistic update with rollback on failure and an error boundary to this list component.
  • Model the form states in XState and describe every allowed transition.

How to install state-ux-flow-builder

1Skills CLI (Vercel)

npx skills add patricio0312rev/skills --skill state-ux-flow-builder -a claude-code

2Manually: put the files in place

~/.claude/skills/state-ux-flow-builder/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/state-ux-flow-builder/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about state-ux-flow-builder

How do I install state-ux-flow-builder in Claude Code?

Run npx skills add patricio0312rev/skills --skill state-ux-flow-builder -a claude-code, then check ~/.claude/skills/state-ux-flow-builder/SKILL.md.

What does state-ux-flow-builder do?

It helps define UI behavior for loading, failed requests, empty results, and successful data. It also covers retry actions, error boundaries, and state-management choices.

When does the skill recommend XState?

It points to XState for flows with several states and transitions. A simpler flow can use useState or server-managed state instead.

Source text

SKILL.md · MIT
---
name: state-ux-flow-builder
description: Standardizes UX states for data fetching flows (loading, error, empty, success) and complex multi-view UI patterns. Provides state machine approach recommendations, loading skeletons, error boundaries, and empty state components. Use when implementing "loading states", "error handling", "empty states", or "state machines".
---

# State & UX Flow Builder

Create consistent UX flows for all application states: loading, error, empty, and success.

## Output Components

Every implementation includes: (1) Loading skeletons, (2) Error state with retry, (3) Empty state with action, (4) Success view, (5) Error boundary, (6) State management pattern (useState/XState/server).

## Key Patterns

**Data Fetching Flow**: Check loading → Handle error → Show empty → Display data
**State Machine**: XState for complex flows with multiple states and transitions
**Optimistic Updates**: Instant UI feedback with rollback on error
**Progressive Loading**: Show content incrementally as it loads

## Best Practices

Always handle all states, prefer skeletons over spinners, provide retry mechanisms, use consistent error/empty UI, add ARIA live regions, implement error boundaries.

© patricio0312rev · MIT · patricio0312rev/skills

Similar skills

All skills for Frontend and UI →

From the same set148

The whole set →
postmortem-writer postmortem-writer turns an incident into a written postmortem: timeline, root cause, contributing factors, action items with owners. Runs as a skill inside your coding agent. CX Codex +1 265installs schema-consistency-checker schema-consistency-checker reads your tables and columns, flags names that break the agreed style, mismatched ID types, nullable critical fields and foreign keys without an index, then hands back a fix list. CX Codex +1 265installs deployment-checklist-generator deployment-checklist-generator generates deployment runbooks, pre-release checklists, smoke-test scripts, and post-launch verification plans. CX Codex +1 264installs api-versioning-deprecation-planner The api-versioning-deprecation-planner is a Claude Code skill for planning API version changes and client migrations. It covers releases of a new version while existing clients still rely on the old one. CX Codex +1 264installs zustand-state-builder zustand-state-builder — a skill for managing app state with Zustand: minimal API, full TypeScript support, persistence, and devtools. Runs on Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode. CX Codex +1 264installs monorepo-ci-optimizer monorepo-ci-optimizer — a CI skill for monorepos: it works out which packages a change touches and runs builds and tests only for those. Useful when every PR runs the whole workspace. CX Codex +1 264installs coverage-strategist The coverage-strategist skill helps set test priorities and coverage goals across a project. Use it when deciding which paths need tests and which code can be left out. CX Codex +1 263installs auth-module-builder auth-module-builder lays out a full authentication module: login and registration routes, JWT signing, bcrypt hashing, Redis sessions and a threat model. Useful when the login flow starts from an empty file. CX Codex +1 263installs

Project sponsors

Companies that keep this analytics open