home / skills / sanky369 / vibe-building-skills / loading-states

This skill helps you design effective loading and empty states that maintain user confidence during delays and empty data scenarios.

npx playbooks add skill sanky369/vibe-building-skills --skill loading-states

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
6.9 KB
---
name: loading-states
description: Design effective loading states, skeleton screens, and empty states that maintain user confidence. Use when content takes time to load, when showing progress, or handling empty data scenarios. Triggers on "loading state", "skeleton screen", "empty state", "spinner", "progress bar", "loading animation", "zero state".
---

# Loading & Empty States

Maintain user confidence when content isn't immediately available.

## Loading State Types

### Choose by Duration

| Duration | Recommendation |
|----------|---------------|
| < 100ms | No indicator needed |
| 100ms - 1s | Subtle indicator (opacity change) |
| 1s - 10s | Skeleton screen or spinner |
| > 10s | Progress bar with estimate |

## Skeleton Screens

### When to Use
- Page or section content loading
- Lists, cards, tables
- Better than spinners for known layouts

### Basic Skeleton
```css
.skeleton {
  background: #e5e7eb;
  border-radius: 4px;
}

/* Animated shimmer */
.skeleton-animated {
  background: linear-gradient(
    90deg,
    #f3f4f6 25%,
    #e5e7eb 50%,
    #f3f4f6 75%
  );
  background-size: 200% 100%;
  animation: shimmer 1.5s infinite;
}

@keyframes shimmer {
  0% { background-position: 200% 0; }
  100% { background-position: -200% 0; }
}
```

### Skeleton Components
```html
<!-- Text skeleton -->
<div class="skeleton skeleton-text" style="width: 80%"></div>
<div class="skeleton skeleton-text" style="width: 60%"></div>

<!-- Avatar skeleton -->
<div class="skeleton skeleton-avatar"></div>

<!-- Image skeleton -->
<div class="skeleton skeleton-image"></div>
```

```css
.skeleton-text {
  height: 16px;
  margin-bottom: 8px;
}

.skeleton-avatar {
  width: 40px;
  height: 40px;
  border-radius: 50%;
}

.skeleton-image {
  width: 100%;
  aspect-ratio: 16/9;
}
```

### Card Skeleton Example
```html
<article class="card card-skeleton">
  <div class="skeleton skeleton-image"></div>
  <div class="card-content">
    <div class="skeleton skeleton-text" style="width: 70%"></div>
    <div class="skeleton skeleton-text" style="width: 90%"></div>
    <div class="skeleton skeleton-text" style="width: 50%"></div>
  </div>
</article>
```

### What NOT to Skeleton
- Modals (should be instant or loading indicator inside)
- Toasts/notifications
- Dropdown menus
- The skeleton itself shouldn't have a skeleton

## Spinners

### When to Use
- Unknown content structure
- Short operations (1-3 seconds)
- Small areas (buttons, inputs)

### Simple Spinner
```css
.spinner {
  width: 24px;
  height: 24px;
  border: 3px solid #e5e7eb;
  border-top-color: var(--primary);
  border-radius: 50%;
  animation: spin 0.8s linear infinite;
}

@keyframes spin {
  to { transform: rotate(360deg); }
}
```

### Button Loading State
```css
.button-loading {
  position: relative;
  color: transparent; /* Hide text */
  pointer-events: none;
}

.button-loading::after {
  content: '';
  position: absolute;
  top: 50%;
  left: 50%;
  transform: translate(-50%, -50%);
  width: 20px;
  height: 20px;
  border: 2px solid currentColor;
  border-top-color: transparent;
  border-radius: 50%;
  animation: spin 0.6s linear infinite;
}
```

### Inline Loading Text
```html
<span class="loading-text">
  Loading
  <span class="loading-dots">
    <span>.</span><span>.</span><span>.</span>
  </span>
</span>
```

## Progress Bars

### When to Use
- Operations > 10 seconds
- File uploads/downloads
- Multi-step processes

### Basic Progress Bar
```html
<div class="progress">
  <div
    class="progress-bar"
    role="progressbar"
    style="width: 65%"
    aria-valuenow="65"
    aria-valuemin="0"
    aria-valuemax="100"
  >
    65%
  </div>
</div>
```

```css
.progress {
  height: 8px;
  background: #e5e7eb;
  border-radius: 4px;
  overflow: hidden;
}

.progress-bar {
  height: 100%;
  background: var(--primary);
  transition: width 0.3s ease-out;
}
```

### Indeterminate Progress
```css
.progress-indeterminate .progress-bar {
  width: 30%;
  animation: indeterminate 1.5s infinite ease-in-out;
}

@keyframes indeterminate {
  0% { transform: translateX(-100%); }
  100% { transform: translateX(400%); }
}
```

## Empty States

### Types of Empty States

1. **First Use**: User hasn't added data yet
2. **No Results**: Search/filter returned nothing
3. **Error State**: Something went wrong
4. **Success Empty**: Completed all tasks (inbox zero)

### First Use Empty State
```html
<div class="empty-state">
  <img src="illustration.svg" alt="" class="empty-illustration">
  <h3 class="empty-title">No projects yet</h3>
  <p class="empty-description">
    Create your first project to get started
  </p>
  <button class="button-primary">
    Create Project
  </button>
</div>
```

### No Results Empty State
```html
<div class="empty-state">
  <span class="empty-icon">🔍</span>
  <h3 class="empty-title">No results found</h3>
  <p class="empty-description">
    Try adjusting your search or filters
  </p>
  <button class="button-secondary">
    Clear Filters
  </button>
</div>
```

### Empty State Styles
```css
.empty-state {
  display: flex;
  flex-direction: column;
  align-items: center;
  justify-content: center;
  padding: 48px 24px;
  text-align: center;
}

.empty-illustration {
  width: 200px;
  max-width: 100%;
  margin-bottom: 24px;
}

.empty-icon {
  font-size: 48px;
  margin-bottom: 16px;
}

.empty-title {
  font-size: 20px;
  font-weight: 600;
  margin-bottom: 8px;
  color: var(--text-primary);
}

.empty-description {
  font-size: 14px;
  color: var(--text-secondary);
  max-width: 300px;
  margin-bottom: 24px;
}
```

### Error States
```html
<div class="empty-state error-state">
  <span class="empty-icon">⚠️</span>
  <h3 class="empty-title">Something went wrong</h3>
  <p class="empty-description">
    We couldn't load your data. Please try again.
  </p>
  <button class="button-primary">
    Retry
  </button>
</div>
```

## Best Practices

### Do
- Match skeleton layout to actual content
- Show loading state immediately (don't wait)
- Use animations to indicate activity
- Provide progress info when possible
- Include helpful actions in empty states
- Keep messaging friendly and helpful

### Don't
- Show spinners for everything
- Use loading states for instant operations
- Leave users without feedback
- Make empty states feel like dead ends
- Animate aggressively (respect motion preferences)

### Accessibility
```css
/* Announce loading to screen readers */
.loading-region[aria-busy="true"]::before {
  content: "Loading...";
  position: absolute;
  clip: rect(0, 0, 0, 0);
}

/* Respect reduced motion */
@media (prefers-reduced-motion: reduce) {
  .skeleton-animated {
    animation: none;
  }

  .spinner {
    animation-duration: 1.5s;
  }
}
```

## Checklist

- [ ] Loading appears within 100ms of action
- [ ] Skeleton matches content structure
- [ ] Progress shown for long operations (>10s)
- [ ] Empty states have helpful actions
- [ ] Error states include retry option
- [ ] Animations respect prefers-reduced-motion
- [ ] Screen readers announce loading state
- [ ] Loading doesn't block entire page unnecessarily

Overview

This skill teaches how to design effective loading states, skeleton screens, spinners, progress bars, and empty states that preserve user confidence when content is delayed or missing. It focuses on choosing the right pattern by duration and context, accessible implementations, and practical rules to avoid common UX mistakes. Use it to make loading feel intentional, informative, and unobtrusive.

How this skill works

The skill inspects the expected content structure and operation duration to recommend an appropriate indicator: instant, subtle, skeleton, spinner, or progress bar. It provides simple CSS/HTML patterns for skeletons, spinners, progress bars, and empty/error states, plus accessibility snippets (aria-busy, reduced motion handling) and a checklist to validate implementations. It also flags cases where a skeleton or spinner is inappropriate and suggests actionable empty-state content.

When to use it

  • When data or UI sections take 100ms–10s to render (skeletons for known layouts, spinners for unknown structures)
  • For very short operations (100ms–1s) use subtle indicators or none
  • For button or inline actions use small spinners or loading text
  • For operations >10s use a progress bar with an estimated percentage or indeterminate animation
  • When a user has no data, or a search/error returns nothing — provide helpful empty states and actions

Best practices

  • Show a loading indicator immediately (within ~100ms) and match skeleton layout to real content
  • Use skeletons for lists, cards, and predictable layouts; avoid skeletons for modals, toasts, dropdowns
  • Prefer progress bars with estimates for long-running tasks and indeterminate bars when percent is unknown
  • Respect motion preferences (prefers-reduced-motion) and ensure screen readers get loading announcements
  • Include helpful CTAs in empty states (create, retry, clear filters) and avoid dead-end messaging
  • Don’t overuse spinners for instant operations or animate aggressively

Example use cases

  • E-commerce product grid: show card skeletons while images and prices load
  • File uploader: show an upload progress bar with percent and cancel retry actions
  • Dashboard with many widgets: display lightweight skeleton blocks per widget to reduce perceived latency
  • Search page: show a "No results" empty state with suggestions and a clear filters button
  • Form submit button: replace text with a small spinner while the request completes

FAQ

When should I use a skeleton instead of a spinner?

Use a skeleton when you know the layout of incoming content (lists, cards, tables). Use a spinner when structure is unknown or for very small components.

How long before I must show progress vs a spinner?

Show a spinner or skeleton for 1–10s. For operations over ~10s prefer a progress bar or estimated time to reduce uncertainty.

How do I make loading accessible?

Announce loading regions with aria-busy, respect prefers-reduced-motion, and avoid hiding essential content. Provide meaningful fallback text for screen readers.