Skip to content
Skills Library
Design & UX · Building & coding

wait

/wait

Shape the perceived wait — loading indicators, skeletons, optimistic updates. Use when building UI where content takes time to arrive, or when reviewing a screen that stalls. Not for the latency budget itself (how long a wait is acceptable) or for post-action success confirmation; the broader state floor lives in frontend:guidelines.

Licence
MIT
Last repository change
27.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Shape the perceived wait — loading indicators, skeletons, optimistic updates. Use when building UI where content takes time to arrive, or when reviewing a screen that stalls. Not for the latency budget itself (how long a wait is acceptable) or for post-action success confirmation; the broader state floor lives in frontend:guidelines.

Original author description

Shape the perceived wait — loading indicators, skeletons, optimistic updates. Use when building UI where content takes time to arrive, or when reviewing a screen that stalls. Not for the latency budget itself (how long a wait is acceptable) or for post-action success confirmation; the broader state floor lives in frontend:guidelines.

How it works

  1. Choosing the Pattern
  2. Duration Tiers
  3. Motion and Layout
  4. Completion
Original SKILL.md headings · 39 lines, 331 words
SKILL.md preview
---
name: wait
description: 'Shape the perceived wait — loading indicators, skeletons, optimistic updates. Use when building UI where content takes time to arrive, or when reviewing a screen that stalls. Not for the latency budget itself (how long a wait is acceptable) or for post-action success confirmation; the broader state floor lives in frontend:guidelines.'
---

# Loading States

Design every wait a user can hit — initial load, submit, pagination, refresh, image loads. Pick each state deliberately, never leave it to a framework default.

## Choosing the Pattern

Default to **skeleton**: a shimmering outline of the layout. It sets expectation and makes the wait feel shortest. Deviate only when a condition earns it:

- **Measurable progress** (upload, multi-step job) — a determinate progress bar with percent or step count.
- **Tiny, unknown-duration action** (button submit) — an inline spinner in the triggering control.
- **User-caused mutation** (like, save, toggle) — optimistic UI: render the result instantly, roll it back visibly on failure.
- **Slow media** — progressive reveal: blur-up images, critical content first, lazy-load below the fold.

## Duration Tiers

| Wait        | Response                                                            |
| ----------- | ------------------------------------------------------------------- |
| Under 100ms | No indicator; the wait is invisible                                 |
| 100ms–1s    | Subtle skeleton or opacity shift                                    |
| 1–10s       | Skeleton plus spinner; progress bar if measurable                   |
| Over 10s    | Progress detail, a time estimate, and a cancel or background option |

## Motion and Layout

- Fade content in over ~200ms so arrival reads as a continuation of the shimmer, not a flash.
- Reserve skeleton dimensions matching the final content, so loaded content lands without shifting layout.
- Keep scroll position stable across refreshes.
- Honor `prefers-reduced-motion`: swap the shimmer for a static placeholder.
- For staggered lists, brief successive delays feel organic — each item reads as arriving, not rendering.

## Completion

- Every wait state above 100ms has a chosen pattern — including the error and empty outcomes of the load.
- First paint always carries a loading affordance; the screen shows intent from frame one.
- One loading indicator per region at a time.
- Loads over 10s offer a way out or a way to background them.
- Verified on a throttled connection (e.g. Slow 3G), where skeleton proportions and transition timing are actually exercised.

Versions

RepositoryScoreLicence
This page · j0hanz/j0hanz-marketplace90MIT
colonyops/hive95MIT

Database snapshot: 13.11.2026 · package version 41f9944d4f13 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90loading-states
    Design waiting experiences — spinners, skeletons, optimistic updates, and progressive reveal. Use when content takes time to arrive. For the latency budget itself use `doherty-threshold`; for success confirmation use `feedback-patterns`.
  • 100loading-states-and-perceived-performance
    Spinners, skeletons and staggered reveals that manage wait times. Use when designing loading states, async data or the feel of a slow interface.
  • 90interaction-feedback
    Use when designing UI feedback around user actions and system state: loading, skeletons, optimistic updates, progress, success, errors, empty states, retries, disabled/pending states, autosave, undo, and perceived latency. Do NOT use for the words inside feedback (use…
  • 90approval-wait
    Pipeline phase skill for state `approval-wait`. Use when current_state is approval-wait.
  • 85ux-loaders-and-progress
    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,…
  • 90smooth-ux
    Make a web app feel responsive and alive. Every click answers (pressed, busy, done), predictable actions update optimistically and revert on failure, slow data shows content-shaped skeletons, route changes give instant feedback, and motion is cheap (transform and opacity only).…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.