smithery/patricio0312rev

state-ux-flow-builder

Standardizes UX states for data fetching flows (loading, error, empty, success) and complex multi-view UI patterns.

Installation

$ npx skills add smithery/patricio0312rev --skill state-ux-flow-builder

Summary

  • 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".

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/patricio0312rev · top by installs.

npx skills add smithery/patricio0312rev

Browse all from smithery/patricio0312rev

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,223 B
  • docs SUMMARY.md 353 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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.