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

saleor-dashboard-feedback

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

Rules for surfacing errors, warnings, and success feedback in Saleor Dashboard (Geist/Vercel-aligned). Use when adding useNotifier/toasts, save/mutation error handling, form validation, banners, setup blockers, or dogfooding feedback quality on entity views (vouchers first). Covers when to toast vs inline vs persistent UI, toast copy quality, stickiness, and anti-patterns.

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

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If a toast is the only place the full error exists, the design is wrong.

    line 31
  2. Distinctive:

    Never: use a toast alone for: billing/permission denials, multi-step triage, field validation, or setup blockers.

    line 46
  3. Very specific:

    Prefer existing commonMessages / feature messages over one-off strings.

    line 100
  4. Distinctive:

    Default: title only, or title + ≤ 2 short lines of description.

    line 106
  5. Very specific:

    If the full message needs reading time, it belongs in a banner/dialog/checklist, not the toast.

    line 108
  6. Very specific:

    Prefer explicit title; don’t lean on generic “Error” / “Success” defaults for product flows.

    line 134
  7. Very specific:

    Use this skill when touching src/discounts/ voucher create/details/list.

    line 159

≈ “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 Feedback

How merchants learn that something worked, failed, or needs attention — without offloading triage into toasts.

Inspired by Geist Toast and Vercel product UI discipline. Implement with macaw-ui-next + useNotifier / our toast queue — do not install Geist packages.

Also see: saleor-dashboard-entity-detail (page anatomy), saleor-dashboard-microcopy (hint copy), toast implementation under src/components/notifications/.


Principle

Feedback lives next to the problem when the merchant must act. Toasts acknowledge terminal, non-blocking outcomes of an action they just took.

If a toast is the only place the full error exists, the design is wrong.


Channel ladder (pick the lowest that fits)

ChannelWhenStays untilExamples
Inline fieldA specific input is invalidField corrected / next submitRequired code, bad date, amount out of range
Section / card errorError belongs to a settings block or list rowNext successful save or explicit dismissRule form error border, codes table row failure
Page banner / alertPage-level blocker or recovery path the merchant must see while on the pageCondition clears or dismissPermission denied, channel not ready, conflict on load
Setup checklistReadiness / configuration funnelStep completedMissing requirements before activate
ToastNon-blocking ack of a user-initiated actionAuto (~5s) or sticky if error/action“Changes saved”, “Couldn’t delete code. Try again.”
BackgroundTasksLong-running jobTask UIExports, bulk ops

Never use a toast alone for: billing/permission denials, multi-step triage, field validation, or setup blockers.


When to use a toast

Do toast

  • Success after Save / create / delete / assign the merchant just triggered
  • Short failure of that same action when the page already shows context (or a one-line recovery is enough)
  • Undo-style confirmations with a single action (Undo)
  • Terminal state of an async flow (one toast at the end — not start/middle/end)

Do not toast

  • Narrating a multi-step mutation sequence (Saving… → Validating… → Saved)
  • Dumping raw GraphQL / API payloads or stack traces
  • Repeating the same error on every keystroke or every failed field
  • Anything the merchant must still fix on this page without a matching inline/banner home
  • N toasts for N row failures — aggregate (3 codes couldn’t be deleted)

Pairing rule (Geist)

For serious failures, prefer:

  1. Short toast (≤ ~6 words in the title sense): Couldn’t save voucher
  2. Persistent surface with the recovery step and enough identity to act
Toast:  Couldn’t save voucher
Page:   banner or field — “End date must be after start date.”

Toast quality bar

Our queue: max 3 visible, FIFO overflow, dedupe by status + title, dismiss-visible only when 2+ show. Errors and actionBtn stay until dismissed (getNotificationDuration → Infinity). See notificationQueue.tsx.

Copy

KindShapeExample
Success{Noun} {past-participle} — no “successfully”Voucher saved, Codes deleted
Neutral / cancelPast tense of what happenedExport canceled
ErrorWhat failed + recovery (two short sentences OK)Couldn’t delete codes. Try again.
WarningRisk or partial outcome, still scannableSome codes were skipped
  • Sentence case. Single-sentence success: no trailing period.
  • Error: use Couldn’t for user/state issues; Failed to for system/infra — stay consistent in one flow.
  • Match the button verb: Delete → … deleted, not … removed.
  • Title carries the punch; description is optional context — not a paragraph.
  • Prefer existing commonMessages / feature messages over one-off strings.

Length

Sonner/Geist do not ship show-more. Canonical fix is shorter copy.

  • Default: title only, or title + ≤ 2 short lines of description.
  • Our Toast clamps long descriptions (2 lines + chevron) as a safety net for legacy/API text — do not rely on it for new work.
  • If the full message needs reading time, it belongs in a banner/dialog/checklist, not the toast.

Behavior

StatusAuto-dismissNotes
success / info / warning (no action)~5s (DEFAULT_NOTIFICATION_SHOW_TIME)Pauses on hover
errorSticky until dismissDefault; don’t preempt other toasts
error + explicit autohideThat durationUse when field/section already owns recovery (paired ack); prefer PAIRED_ERROR_NOTIFICATION_SHOW_TIME (~10s) for save/create failures
any + actionBtnSticky until dismiss or actionOne clear action label; wins over autohide
  • One terminal toast per user action.
  • Deduping replaces same status + title — update description if the detail changed; don’t spam.
  • Bulk: one aggregated notify, not a toast per row.

useNotifier checklist

notify({
  status: "success", // or error | warning | info
  title: intl.formatMessage(messages.voucherSaved), // prefer explicit title
  // text: optional short description
  // actionBtn: only when a single recovery/undo is real
});
  • Prefer explicit title; don’t lean on generic “Error” / “Success” defaults for product flows.
  • Pass actionBtn only for a safe, single next step (Undo, Open settings) — not primary navigation dumps.
  • On save failure: map GraphQL errors to fields/sections first; toast is the ack, not the encyclopedia.

Decision tree

Did the merchant just complete an action?
  no  → persistent UI only (banner / checklist / empty state). No toast.
  yes → Did it succeed?
          yes → success toast (short). Done.
          no  → Can they fix it on a specific field/section?
                  yes → inline/section error + short error toast (optional if inline is obvious).
                  no  → Is it a page-level / permission / readiness issue?
                          yes → banner or checklist + short error toast.
                          no  → short sticky error toast with recovery sentence;
                                file a follow-up if this keeps happening (wrong surface).

Dogfood: vouchers (first)

Use this skill when touching src/discounts/ voucher create/details/list.

Audit checklist

  • Save success → one Voucher saved / Changes saved toast; no second toast from the same submit
  • Field validation (dates, limits, codes) → inline / section errors; toast does not carry the full validation list
  • Code bulk delete / generate failures → aggregated toast; row/section detail if the merchant must retry specifics
  • Permission / channel blockers → banner or checklist, not toast-only
  • No toast on every codes-table refetch or filter change
  • Error toast copy: couldn’t/failed + recovery; sticky by default (or autohide when paired with inline/section); no raw API blob in text
  • Action buttons on toasts only for real undo/recovery (not “Close”)

Anti-patterns to remove when found

// ❌ Toast-only validation
notify({ status: "error", text: errors.map(e => e.message).join(", ") });

// ❌ Narrating the flow
notify({ status: "info", text: "Saving voucher…" });
notify({ status: "success", text: "Voucher saved successfully." });

// ✅ Terminal ack + inline home for the problem
form.setError("endDate", { message: intl.formatMessage(messages.endBeforeStart) });
notify({
  status: "error",
  title: intl.formatMessage(messages.couldNotSaveVoucher),
  text: intl.formatMessage(messages.checkHighlightedFields),
  autohide: PAIRED_ERROR_NOTIFICATION_SHOW_TIME,
});

Implementation map

ConcernWhere
Notify APIsrc/hooks/useNotifier/useNotifier.tsx
Duration / sticky rulessrc/hooks/useNotifier/utils.ts
Queue (cap 3, FIFO, dedupe)src/components/notifications/notificationQueue.tsx
Toast UI (clamp safety net)src/components/notifications/Toast.tsx
Common success/error stringssrc/intl.ts, src/utils/errors/common.ts

Restraint tests

Before shipping feedback:

  1. Squint test — can you tell success vs failure in under a second?
  2. Absent-toast test — if the toast never appeared, could the merchant still recover from on-page UI?
  3. Tall-toast test — if description needs show-more, shorten the copy or move it out of the toast.
  4. Stack test — would a slow merchant still see the important message with max 3 + FIFO? If not, it shouldn’t be toast-only.

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.