Loading...
Loading...
Found 3 Skills
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".
Production-readiness pass — audits and implements the full non-happy-path matrix: loading skeletons, empty states, error messages, partial data, i18n, offline, permissions, and first-run guidance. Use when preparing a surface for production or when the user says "it crashes on empty data" / "there's no loading state" / "harden this". Invoke when the user asks for harden on their UI, or mentions 'harden' alongside design / UI / frontend work.
Design every state a screen can be in, not just the happy one. Loading with skeletons that match the layout, spinner timing, empty states that teach one action, partial and stale data, errors that say what to do, optimistic updates and rollback, streaming, offline, unsaved changes, and success that does not interrupt. Use when building any screen that fetches, submits or can be empty, or when a screen "flashes", "jumps", or shows a spinner over everything.