loading-states-and-perceived-performance

Designs user-centered loading strategies for mobile and web interfaces.

33|6|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/dembrandt/dembrandt-skills --skill loading-states-and-perceived-performance-dembrandt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loading-states-and-perceived-performance
Source: https://github.com/dembrandt/dembrandt-skills/tree/main/skills/loading-states-and-perceived-performance
Command: npx skills add https://github.com/dembrandt/dembrandt-skills --skill loading-states-and-perceived-performance-dembrandt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps interfaces communicate progress clearly and feel responsive during delays, preventing frustration, layout shifts, duplicate actions, and uncertainty while content or operations are loading.

Core Features & Use Cases

  • Choose appropriate loading patterns: Select inline spinners, skeleton screens, determinate progress bars, or staggered entry animations based on expected wait duration and context.
  • Improve perceived performance: Load high-value content first, stream secondary content progressively, preserve layout stability, and prefetch predictable next steps.
  • Add resilient interaction feedback: Use optimistic UI with rollback handling, branded microcopy, progressive storytelling, and subtle arrival transitions.
  • Use Case: Design a dashboard that shows skeleton cards during a medium-length fetch, renders the primary metric first, streams secondary panels afterward, and respects reduced-motion preferences.

Quick Start

Ask the loading-states-and-perceived-performance skill to design an appropriate loading experience for this data-heavy screen, including skeleton structure, timing, priority loading, and accessibility considerations.

Frequently Asked Questions about loading-states-and-perceived-performance

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

FAQPage Schema
What is the best way to design loading states for data-heavy dashboards?

Optimistic UI improves perceived performance by immediately reflecting the expected result of an interaction, then handling rollback if the operation fails. This resilient interaction feedback prevents duplicate actions and uncertainty while API calls complete.

How do I choose between inline spinners and skeleton screens?

Choose between inline spinners and skeleton screens based on expected wait duration and context. Use inline spinners for quick operations, determinate progress bars for longer waits, and skeleton screens to preserve layout stability during data fetches.

How do I implement progressive loading while respecting reduced motion preferences?

Implement progressive loading by loading high-value content first and streaming secondary content, while respecting reduced motion by disabling staggered entry animations. Provide accessible arrival feedback and subtle transitions that adapt to user motion preferences.

When should I use predictable prefetching for page transitions?

Use predictable prefetching for page transitions when you can anticipate the user's next step to make waits feel faster. Prefetching loads resources in advance, ensuring immediate availability and smoother transitions without visible loading delays.