agentleFS
saleorsaleor/saleor-dashboard/.claude/skills/saleor-dashboard-loading/SKILL.md

saleor-dashboard-loading

Skill1.1k starsChanged 8 days agoBSD-3-ClauseView on GitHub

Geist-aligned loading, skeleton, and empty-state rules for Saleor Dashboard entity views. Use when adding loading shells, Skeleton placeholders, spinners, empty states, or fixing flashes of default/form UI before async data resolves. Covers page-level gates vs in-card skeletons, aria-busy, and anti-patterns (fake selected defaults).

Trending

Less talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 3 mentionsMar 2026: 5 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 33 mentionsJul 2026: 3 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 2 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the saleor/saleor-dashboard repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about saleor/saleor-dashboard

The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 50

Talked about on GitHub (50 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user can see “Entire order” selected for a Free shipping voucher for one frame, the design is wrong — keep the skeleton (or don’t …

    line 33
  2. Distinctive:

    Never: use Skeleton as decoration or as a stand-in for empty.

    line 47
  3. Distinctive:

    When the primary entity query is unresolved:

    line 56
  4. Distinctive:

    After the page has revealed, a sub-list may still load (e.g.

    line 84
  5. Distinctive:

    Prefer blocks that mirror tiles, inputs, and metric numbers — not one anonymous bar for a three-tile selector.

    line 98

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Saleor Dashboard Loading

How merchants wait for data — without flashing wrong defaults or layout jumps.

Inspired by Geist Skeleton and Vercel product UI discipline. Implement with macaw-ui-next Skeleton / existing spinners — do not install Geist packages.

Also see: saleor-dashboard-entity-detail (page anatomy), saleor-dashboard-feedback (errors vs loading), saleor-dashboard-styles (tokens).

Canonical dogfood: voucher details — VoucherDetailsPageLoading + gate Form until voucher (and first codes settle).


Principle

Loading UI must look like the final layout, not like a guessed answer. Never show a selected radio, filled metric, or form default that will change when data arrives.

If the user can see “Entire order” selected for a Free shipping voucher for one frame, the design is wrong — keep the skeleton (or don’t mount the form) until truth is known.


Pick the right indicator

IndicatorWhenExamples
SkeletonAsync data fills a known layout (cards, grids, table rows)Detail page shell, discount type tiles, lists
SpinnerSingle in-flight action (button, dialog confirm)Save, delete, modal submit
LoadingDotsIndeterminate inline wait without a fixed box shapeRare; prefer Skeleton when shape is known
EmptyStateQuery finished and there is nothing to showNo codes, no channels

Never use Skeleton as decoration or as a stand-in for empty. When there’s no data after load, render EmptyState.


Page vs region

Page-level shell (entity not loaded)

When the primary entity query is unresolved:

  1. Render a dedicated *DetailsPageLoading (or equivalent) that mirrors DetailPageLayout — TopNav title skeleton, skeleton section-nav labels, card titles/intros (static copy OK on cards), skeleton bodies, disabled Savebar.
  2. Do not mount Form / controlled selection UIs until entity exists.
  3. Remount the form with key={entity.id} when navigating between entities so invent defaults never leak across IDs.

Card titles/intros may stay visible (stable copy). The section map/nav should be skeletons — labels are part of the unknown layout (optional Countries/Catalogue) and reading real nav while the page is empty is premature chrome.

Anything that encodes entity-specific truth (selected discount type, usage counts, schedule status) must be skeleton or hidden until known.

Shape fidelity checklist (compare shell ↔ loaded UI):

  • Skeleton the section map/nav labels (correct item count, including reserved optional slot)
  • Reserve header actions that always exist (+ Add, Manage) as disabled controls
  • Match list/table chrome (header + row + pagination), not one anonymous bar
  • Match variant-specific blocks (e.g. shipping callout vs amount controls)
  • Sidebar cards: reuse real card components with loading so info callouts / intros stay
  • Type-dependent nav count: reserve one optional slot only while entity is unknown; once known, pass real visibility (do not keep a fake Countries row for entire-order vouchers)

Region skeleton (secondary query)

After the page has revealed, a sub-list may still load (e.g. voucher codes pagination). Skeleton inside that card only — do not tear down the whole page on refetch.

Optional: on first paint, keep the page shell until the primary secondary query settles once, so users don’t see “correct form + one skeleton card” flash. Use a hasRevealedContent flag keyed by entity.id; subsequent refetches use in-card skeletons only.


Shape & motion (Geist)

  • Match final width / height / shape so reveal doesn’t reflow (CLS).
  • Prefer blocks that mirror tiles, inputs, and metric numbers — not one anonymous bar for a three-tile selector.
  • Skeletons are decorative; wrap the loading region in aria-busy="true".
  • No focusable controls inside skeleton regions (no enabled Save, Add, Manage).
  • Respect prefers-reduced-motion where we own animation (macaw Skeleton handles common cases; don’t add custom infinite shimmer that ignores it).

Anti-patterns

Don’tDo
Mount Form with ENTIRE_ORDER / 0 used / “Redeemable now”Gate Form; skeleton metrics and status
Show selected choice tiles before dataSkeleton the tile grid
Reveal type-dependent nav (catalogue/countries) earlyHide until type known
Full-page spinner for a known card gridLayout-shaped Skeleton
Skeleton forever when emptyEmptyState after load
Fake progress / invented countsSkeleton or “—” only if product copy allows

Checklist (new / refactored detail views)

  • Gate — no Form / selection UI until primary entity exists; key={id} on remount
  • Shell — loading layout matches final grid (nav + cards + sidebar + savebar)
  • No fake truth — no default selected radios, metrics, or schedule status while loading
  • Secondary lists — in-card skeleton after reveal; optional first-paint wait
  • a11y — aria-busy on loading regions; controls disabled in shell
  • Empty ≠ loading — EmptyState only after query settles with zero items

Reference implementation

PiecePath
Page loading shellsrc/discounts/components/VoucherDetailsPage/VoucherDetailsPageLoading.tsx
Gate + form keysrc/discounts/components/VoucherDetailsPage/VoucherDetailsPage.tsx
Section skeletonsVoucherDiscountSection, VoucherInfo, VoucherLimits, …
Sidebar metrics while loadingVoucherRedemptionsCard (loading hides used/status copy)

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.