site-ux-states-patterns

Design loading, empty, error, success, and motion states for website interfaces.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill site-ux-states-patterns-tech-hy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: site-ux-states-patterns
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/site-ux-states-patterns
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill site-ux-states-patterns-tech-hy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Interfaces often break down outside the happy path: users face blank screens, cryptic errors, dead-end empty states, and distracting animations. This Skill turns loading, empty, error, success, disclosure, and motion behavior into explicit UX contracts so every screen stays understandable under real conditions. ## Core Features & Use Cases - State Modeling: Define explicit loading, empty, error, and success behavior for any component or page, with checklists for empty-state and error-state copy. - Form & Content Flow Design: Apply progressive disclosure, field-level error recovery, CTA hierarchy, and confirmation patterns to forms, checkout, and onboarding flows. - Motion & Disclosure Guardrails: Use transitions that clarify change, respect prefers-reduced-motion, and keep fallbacks when animation APIs are unavailable. - Use Case: When building a search results page, use this Skill to define the skeleton loading layout, the zero-results empty state with a reset action, the error retry path, and the transition behavior between filters. ## Quick Start Use the site-ux-states-patterns skill to design the loading, empty, error, and success states for my dashboard's filterable results table.

Frequently Asked Questions about site-ux-states-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design empty states for search and filter results?

Empty states should explain what happened, why the result is empty, and the best next action. Include a reset path, example content, or import option so the state acts as a navigational moment rather than a dead end.

What states should every UI component define?

Every non-trivial component should explicitly define loading, empty, error, and success states. Deliberately omitting a state is acceptable, but forgetting one creates accidental edge cases that confuse users.

When should I use skeleton screens instead of spinners?

Skeleton screens work best when they match the eventual layout, appear briefly while real content loads, and reduce uncertainty without visual noise. They should not be used to hide slow architecture or repeated unnecessary fetches.

How do I handle animations for users who prefer reduced motion?

Respect the prefers-reduced-motion media query, avoid parallax and large simulated camera movement, and never block interaction behind long entrance sequences. Keep a fallback path so the interface works when transition APIs like document.startViewTransition are unavailable.

What makes a good form error recovery flow?

Combine field-level error messages with a summary after failed submission, preserve the user's input, and provide a clear path back to the failed field. Error messages should shorten recovery time rather than merely announcing failure.