Index of every page on this site: llms.txt
All skills
dylantarre avatar

/notifications-toasts

@8359713
Run it yourself

Use when animating notifications, toasts, alerts, snackbars, or system messages to grab attention appropriately

  • 1 file
  • 2.7 KB
  • Updated 11 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/dylantarre/animation-principles/notifications-toasts

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈33 tokens for metadata: the name and description. ≈659 when used: this file.

Description uses 1.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈134 characters, or 1.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Notification & Toast Animation Principles

Apply Disney's 12 principles to notifications for attention-grabbing yet non-disruptive alerts.

Principles Applied to Notifications

1. Squash & Stretch

Toast can compress slightly on entrance impact, then stretch back. Creates a "landing" feel as if it arrived from off-screen.

2. Anticipation

Before auto-dismiss, toast can contract slightly (95% scale) for 100ms. Signals imminent departure to user.

3. Staging

Notifications should appear in consistent locations. Use color and icons to stage importance: info, success, warning, error.

4. Straight Ahead & Pose to Pose

Define states: entering, visible, exiting, stacked. Clear keyframes for entrance, attention (if needed), and exit.

5. Follow Through & Overlapping Action

Icon animates after container arrives (checkmark draws, bell wobbles). Progress bar for auto-dismiss follows toast entrance.

6. Ease In & Ease Out

Enter: ease-out (fast in, slow settle). Exit: ease-in (slow start, fast out). cubic-bezier(0.68, -0.55, 0.27, 1.55) for bounce.

7. Arcs

Toasts sliding from corners can follow slight arc. Bell icons should swing in arc, not rotate rigidly.

8. Secondary Action

While toast slides in (primary), shadow appears (secondary), icon animates (tertiary), progress bar starts (quaternary).

9. Timing

  • Toast enter: 200-300ms
  • Toast exit: 150-250ms
  • Auto-dismiss delay: 3000-5000ms
  • Attention pulse: 1000ms loop
  • Success checkmark draw: 300ms
  • Stack reorder: 200ms

10. Exaggeration

Error notifications can shake or pulse red. Critical alerts can be larger, bolder animations. Match urgency to importance.

11. Solid Drawing

Maintain consistent toast sizing. Icons should be crisp. Progress bars should be smooth (use transforms, not width).

12. Appeal

Smooth notifications feel polished. Jarring popups annoy users. A well-animated toast conveys professionalism.

CSS Implementation

.toast {
  animation: toastEnter 300ms cubic-bezier(0.68, -0.55, 0.27, 1.55);
}

.toast.exiting {
  animation: toastExit 200ms ease-in forwards;
}

@keyframes toastEnter {
  from {
    opacity: 0;
    transform: translateY(-100%) scale(0.9);
  }
  to {
    opacity: 1;
    transform: translateY(0) scale(1);
  }
}

@keyframes toastExit {
  to {
    opacity: 0;
    transform: translateX(100%);
  }
}

.toast-progress {
  transform-origin: left;
  animation: progress 4000ms linear forwards;
}

Key Properties

  • transform: translate, scale
  • opacity: fade
  • animation: entrance/exit sequences
  • transform-origin: progress bars
  • box-shadow: depth

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 8359713. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Dormantupdated 11 months ago

README badge

README badge for dylantarre/animation-principles/notifications-toasts