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
npx skills add patricio0312rev/skills --skill state-ux-flow-builder -a claude-codeWhat 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
OrdersPagedata 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-code2Manually: put the files in place
~/.claude/skills/state-ux-flow-builder/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/state-ux-flow-builder/
1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill state-ux-flow-builder -a codex2Manually: put the files in place
.agents/skills/state-ux-flow-builder/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill state-ux-flow-builder -a cursor2Manually: put the files in place
.cursor/skills/state-ux-flow-builder/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install patricio0312rev/skills frontend/state-ux-flow-builder/SKILL.md2Manually: put the files in place
.github/skills/state-ux-flow-builder/SKILL.md1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill state-ux-flow-builder -a gemini-cli2Platform CLI
gemini skills install https://github.com/patricio0312rev/skills --path frontend/state-ux-flow-builderManually: put the files in place
.devin/skills/state-ux-flow-builder/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill state-ux-flow-builder -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
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