agentleFS
Sign inStart free
malinskibeniaminmalinskibeniamin/skills/ask-sonner/SKILL.md

ask-sonner

Skill4 starsChanged 10 days agoMITView on GitHub

Set up, style, or troubleshoot Sonner React toasts: Toaster placement, promise/loading lifecycles, duplicate messages, theme, portals, and custom content.

31 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brandkit, design-taste-frontend-v1 and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnasX7Skill

    brandkit

    Premium brand-kit image generation skill for creating high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations. Trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems. Optimized for intentional logo concepting, refined composition, sparse typography, strong symbolic meaning, premium mockups, art-directed imagery, and flexible grid layouts.

    Also in 6 projects that use this

  • HK-hubSkill

    design-taste-frontend-v1

    The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is `design-taste-frontend` (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.

    Also in 4 projects that use this

  • OpenAISkill

    image-to-code

    Implement a selected image, screenshot, mockup, or Image Gen reference as a faithful, responsive frontend.

    Also in 6 projects that use this

  • AnasX7Skill

    imagegen-frontend-mobile

    Elite mobile app image-generation skill for creating premium, app-native screen concepts and flows. Designed for iOS, Android, and cross-platform mobile products. Prioritizes clean hierarchy, comfortably readable text, strong multi-screen consistency, controlled color palettes, non-generic creative direction, textured surfaces, image-led composition, tasteful custom iconography, and clean phone mockup framing. By default, screens should be shown inside a subtle premium iPhone or similar phone mockup with a visible frame, while the main focus stays on the app content itself. This skill generates images only. It does not write code.

    Also in 4 projects that use this

  • HK-hubSkill

    stitch-design-taste

    Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.

    Also in 4 projects that use this

  • +7 more from AnasX7

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the installed Sonner version and existing design-system wrapper.

    line 6
  2. Distinctive:

    Read installed types/current official docs before using version-dependent props or return values.

    line 8
  3. Very specific:

    Call toast on the client at the operation boundary.

    line 16
  4. Very specific:

    Use success/error/info/warning calls for outcomes.

    line 18
  5. Distinctive:

    Read RECIPES.md for update/dismiss and error-handling patterns.

    line 20
  6. Distinctive:

    Keep important failure/recovery state inline as well as transient notification.

    line 21
  7. Distinctive:

    Never treat a loading toast, optimistic start, or swallowed rejection as success.

    line 22
  8. Very specific:

    Use wrapper variants/tokens first.

    line 40
  9. Distinctive:

    Verify one operation gives one notification, resolves/rejects correctly, can dismiss, and stays usable with keyboard, screen reader …

    line 45

“Common” is measured: kept by at least 6 in 10 of the 17 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.

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

Use the installed Sonner version and existing design-system wrapper. Adapted from Emil Kowalski; provenance. Read installed types/current official docs before using version-dependent props or return values; this is guidance, not a frozen API spec.

Integration

  • Reuse the project's Toaster wrapper, usually under @/components/ui/. Mount once at a stable app root outside clipping/stacking ancestors. Additional Toasters need a supported, explicit targeting scheme; do not assume multi-toaster props exist.
  • Call toast on the client at the operation boundary. Server code returns a result; the client announces it. Prefer event/mutation outcomes over render/effect side effects.
  • Use success/error/info/warning calls for outcomes; toast.loading plus a stable id for manual lifecycle, or toast.promise for a promise that actually settles. Read RECIPES.md for update/dismiss and error-handling patterns.
  • Keep important failure/recovery state inline as well as transient notification. Never treat a loading toast, optimistic start, or swallowed rejection as success.

Diagnosis

SymptomInspect before changing
Missing toastToaster lifetime, client call, targeted id if supported
DuplicatesMultiple Toasters or effect replay; stable operation id
Loading foreverUnsettled promise, missed catch/finally, persistent duration
Wrong themeResolved theme passed by the existing provider/wrapper
Behind dialog/clippedPortal placement, ancestor transform/filter/overflow, stacking layers
Lost stylesInstalled package CSS export and framework stylesheet lifecycle
Classes ignoredCascade/layers and wrapper configuration; scope override at its owner
Mobile overlapSupported offset props, safe area, keyboard and placement
Swipe jumps, ignores flicks or cannot be caughtExisting Sonner gesture driver and CSS overrides; load gestures without adding a competing drag handler

Styling and verification

Use wrapper variants/tokens first; fix specificity at the source instead of scattering !important. Consider unstyled or toast.custom only when the installed API supports the needed behavior. Custom controls use the project's Button/Link and accessible labels; headless content does not supply semantics automatically.

Verify one operation gives one notification, resolves/rejects correctly, can dismiss, and stays usable with keyboard, screen reader announcements, reduced motion, themes, and dialogs. Verify the persistent error path too. Explain/review requests return findings; build/fix requests continue through project tests and delivery gates.

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.

Check your setup, free