Menu

Individual skill

ux-loaders-and-progress

0upvotes

Design or critique loading states and progress indicators — match the feedback type (spinner, text, determinate bar, skeleton, progress tracker) to the wait duration and task structure, and manage perceived performance. Trigger when the user asks to design or review loaders, spinners, loading states, skeleton screens, progress bars, progress trackers, steppers, or multi-step flow progress.

ux/components/loaders-and-progress/SKILL.md

Read pinned source

Source commit 5007cd0241ccaa51ae2e4681f9618912dc10e239

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
40
Repository last updated
Jul 2, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Loaders & Progress Skill

## How this skill behaves (read first)

This is a **generative** skill. The default failure modes: **one spinner for everything** (a full-page spinner whether the wait is 1 second or 60), **no endpoint when one exists** (indeterminate loops for measurable tasks), and **progress theater** (trackers on 2-step forms, percentages that lie). The feedback type is determined by *wait duration* and *task structure* — and a loader's real job is shaping perceived time, not decorating it. This skill gates:

1. **Establish the wait type** — how long, is it measurable, what initiated it, is it a multi-step journey?
2. **Apply the always-true core** — the duration ladder, placement, state visibility.
3. **Surface the context-dependent decisions** (skeletons, custom animation, tracker labeling, save/autosave) with trade-offs.

Then it **hands off to `ux-heuristics-audit`, `ux-accessibility-audit`, `ux-aesthetics-audit`, and `ux-microcopy-audit`** for validation.

---