design-ui-states

Designs empty, loading, error, partial, and ideal states plus forms and confirmation dialogs per NN/g guidelines.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill design-ui-states-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-ui-states
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/design-ui-states
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill design-ui-states-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Most mockups and shipped screens only show the happy path, leaving empty, loading, error, and partial states undesigned — which reads as broken to users. This Skill provides a systematic five-state pass so every screen is fully specified before it ships. ## Core Features & Use Cases - Five-State Pass: Produces a state spec covering ideal, empty (first-use, user-cleared, no-results), loading, error, and partial states for any screen. - Feedback Channel Selection: Decision trees for choosing between validation, indicators, and notifications, plus rules for when confirmation dialogs are earned versus when undo is better. - Form & Validation Law: NN/g-grounded lint rules covering labels, placeholder prohibition, validation timing, error message anatomy (what happened, why, next step), and input preservation. - Use Case: A designer is about to hand off an appointments screen that only shows a full list. Run the five-state pass to deliver a complete spec: skeleton loading for 1–3s waits, a first-use empty state with a booking CTA, an offline error state with cached data and retry, and a single-item partial layout. ## Quick Start Ask the AI to run the five-state pass on your screen design and produce the full state spec including empty, loading, error, and partial states.

Frequently Asked Questions about design-ui-states

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

FAQPage Schema
How do I design empty states for a new screen?

Design three distinct empty states: first-use (teach what the screen is for plus one CTA), user-cleared (acknowledge completion without repeating the onboarding pitch), and no-results (show the query and offer recovery). Never ship a blank screen or reuse one generic empty state for all three.

How do I choose between a spinner, skeleton screen, and progress bar?

Choose the loading indicator by expected wait time using Nielsen's response-time limits. Under 1 second needs nothing, 1–10 seconds gets a skeleton screen when layout is known or a spinner for small regions, and over 10 seconds needs determinate progress with percent or steps.

When should I use a confirmation dialog versus undo?

Use undo for any action that is reversible, even destructive ones like deletion. Reserve confirmation dialogs only for actions that are rare, destructive, and irreversible — frequent confirmations cause habituation and protect nothing. The dialog must name the object and state consequences.

Why is placeholder text as a form label considered bad practice?

Placeholder-as-label disappears when the user types, creating memory load and preventing review before submit. It also fails contrast requirements and has inconsistent screen-reader support. Use a persistent label above the field with help text outside the field instead.

What are the limits of this UI states approach?

This Skill covers deterministic UI states only — AI and generative output failures like hallucination or low confidence belong to a separate trust-and-failure-states skill. It also defines what messages must contain but not their final wording, which belongs to UX microcopy work.