loading-states
Skill7 starsChanged 10 months agoMITView on GitHub
Animation patterns for loading, progress, and waiting states. Use for skeleton screens, progress indicators, optimistic UI, and content placeholder transitions. Keeps users informed and engaged during async operations.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- pengGgxp/skillstheir own version, first seen Oct 11, 2026
- sanky369/vibe-building-skillstheir own version, first seen Jul 2, 2026
- miovrag/claude-skillstheir own version, first seen Jun 12, 2026
- launchapp-dev/animus-clitheir own version, first seen Mar 15, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- launchapp-dev/animus-cli★ 39same name
- sanky369/vibe-building-skills★ 30same name
- miovrag/claude-skills★ 1same name
- pengGgxp/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository87 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- motion-designSkill
- 3d-transformsSkill
- accessibilitySkill
- android-nativeSkill
- animation-recipesSkill
- anticipationSkill
- arc-motionSkill
- attention-choreographySkill
- attentionSkill
- audio-reactiveSkill
- blurSkill
- brand-animationSkill
- cameraSkill
- characterSkill
- choice-resolutionSkill
- cinematicSkill
- code-generationSkill
- colorSkill
- component-animationsSkill
- compositingSkill
- consequenceSkill
- container-transformSkill
- css-advancedSkill
- data-visualizationSkill
- depthSkill
- distortionSkill
- dramaturgySkill
- durationSkill
- easingSkill
- emotional-journeySkill
- emotion-mappingSkill
- emotion-selectionSkill
- empty-statesSkill
- entrance-patternsSkill
- exaggerationSkill
- exit-patternsSkill
- exportSkill
- figma-integrationSkill
- follow-throughSkill
- frame-timingSkill
- gesture-motionSkill
- glow-shadowSkill
- intentSkill
- ios-nativeSkill
- loopingSkill
- lottieSkill
- masksSkill
- microstateSkill
- morphingSkill
- motion-auditSkill
- motion-blurSkill
- motion-principlesSkill
- motion-specsSkill
- narrative-arcSkill
- notificationsSkill
- onboardingSkill
- opacitySkill
- orchestratorSkill
- particlesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 121
Update UI immediately, reconcile with server after.
- Distinctive: line 201
No immediate feedback: - Always show something within 100ms
- Distinctive: line 202
Spinner for known content: - Use skeleton when structure is known
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Loading States
Animation patterns that keep users informed and engaged during asynchronous operations. Good loading states reduce perceived wait time and prevent abandonment.
Core Principles
- Immediate feedback - Show something within 100ms
- Progressive disclosure - More detail as wait extends
- Accurate expectations - Determinate when possible
- Minimal distraction - Subtle animation, not attention-grabbing
Pattern Categories
| Pattern | Use When | Duration |
| Skeleton | Content structure known | 200ms - 3s |
| Spinner | Unknown structure/duration | 200ms - 10s |
| Progress bar | Duration known/calculable | 500ms - 60s |
| Optimistic UI | Action likely to succeed | Instant |
| Placeholder | Content being generated | 1s+ |
Skeleton Screens
Placeholder that mirrors content structure. Reduces perceived load time by 30-40%.
CSS Implementation
/* Base skeleton */
.skeleton {
background: linear-gradient(
90deg,
var(--skeleton-base) 25%,
var(--skeleton-highlight) 50%,
var(--skeleton-base) 75%
);
background-size: 200% 100%;
animation: skeleton-shimmer 1.5s ease-in-out infinite;
}
:root {
--skeleton-base: #e0e0e0;
--skeleton-highlight: #f0f0f0;
}
@media (prefers-color-scheme: dark) {
:root {
--skeleton-base: #2a2a2a;
--skeleton-highlight: #3a3a3a;
}
}
@keyframes skeleton-shimmer {
0% { background-position: 200% 0; }
100% { background-position: -200% 0; }
}
/* Skeleton shapes */
.skeleton-text { height: 1em; border-radius: 4px; }
.skeleton-title { height: 1.5em; width: 60%; border-radius: 4px; }
.skeleton-avatar { width: 48px; height: 48px; border-radius: 50%; }
.skeleton-image { aspect-ratio: 16/9; border-radius: 8px; }Progress Indicators
Determinate Progress
/* Linear progress bar */
.progress-bar {
height: 4px;
background: var(--progress-track);
border-radius: 2px;
overflow: hidden;
}
.progress-fill {
height: 100%;
background: var(--progress-fill);
border-radius: 2px;
transition: width 200ms ease-out;
}Indeterminate Progress
/* Indeterminate linear */
.progress-indeterminate {
height: 4px;
background: var(--progress-track);
overflow: hidden;
position: relative;
}
.progress-indeterminate::after {
content: '';
position: absolute;
top: 0;
left: 0;
height: 100%;
width: 30%;
background: var(--progress-fill);
animation: indeterminate 1.5s ease-in-out infinite;
}
@keyframes indeterminate {
0% { left: -30%; }
100% { left: 100%; }
}Optimistic UI
Update UI immediately, reconcile with server after. See references/optimistic-patterns.md for implementation details.
Key Pattern
// Optimistic update flow
const handleAction = async () => {
const newValue = !value;
setValue(newValue); // Optimistic update
try {
await api.update(newValue);
} catch {
setValue(!newValue); // Revert on failure
}
};Content Placeholder Transitions
Smooth transition from skeleton to real content:
<AnimatePresence mode="wait">
{isLoading ? (
<motion.div
key="skeleton"
initial={{ opacity: 0 }}
animate={{ opacity: 1 }}
exit={{ opacity: 0 }}
transition={{ duration: 0.2 }}
>
{skeleton}
</motion.div>
) : (
<motion.div
key="content"
initial={{ opacity: 0, y: 10 }}
animate={{ opacity: 1, y: 0 }}
transition={{ duration: 0.3, ease: 'easeOut' }}
>
{children}
</motion.div>
)}
</AnimatePresence>Timing Guidelines
| Wait Duration | Pattern |
| < 100ms | No indicator needed |
| 100ms - 300ms | Subtle opacity change |
| 300ms - 1s | Skeleton or spinner |
| 1s - 10s | Progress bar if determinable |
| 10s+ | Progress + time estimate |
Accessibility
// Announce loading state to screen readers
<div aria-live="polite" aria-busy={isLoading}>
{isLoading && <span className="sr-only">Loading content...</span>}
{!isLoading && content}
</div>
// Progress bar with aria labels
<div
role="progressbar"
aria-valuenow={progress}
aria-valuemin={0}
aria-valuemax={100}
aria-label="Upload progress"
>
{progress}%
</div>Common Mistakes
- No immediate feedback - Always show something within 100ms
- Spinner for known content - Use skeleton when structure is known
- Indeterminate when determinate possible - Show progress when calculable
- Forgetting error states - Loading can fail, handle it
- Jarring transitions - Smooth fade from skeleton to content
Related Skills
animation-recipes- Pre-built loading animation recipesaccessibility- WCAG compliance for loading statescomponent-animations- Button loading states, form submissions
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

