Skip to main content
skill CX Codex

notifications-toasts — Claude Code skill: what it does, how to install

Guides AI assistants on animating toasts and system alerts using classic animation principles. Useful when building smooth UI notifications.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add dylantarre/animation-principles --skill notifications-toasts -a claude-code
Open on GitHub

What notifications-toasts does

The skill equips coding agents with concrete motion rules for interface notices. It covers squash on landing and a 100ms scale down to 95% right before auto-dismissing. Instead of arbitrary values, the model gets exact durations: 200-300ms for entrance and 150-250ms for exits.

It details layer separation where secondary actions lag behind the primary container slide, such as icons animating after arrival. Progress bars must animate via transform and transform-origin rather than width to prevent costly layout recalculations.

What it helps with

  • create CSS keyframe animations for toast entrance and exit
  • build a performant auto-dismiss progress bar without layout thrashing
  • signal upcoming toast dismissal with scale anticipation
  • select timing curves and durations for system error shakes

Example prompts for the agent

  • Generate CSS entrance and exit animations for a toast alert
  • Animate an auto-dismiss progress bar using CSS transforms
  • Add a slight anticipation scale effect before the alert vanishes

How to install notifications-toasts

1Skills CLI (Vercel)

npx skills add dylantarre/animation-principles --skill notifications-toasts -a claude-code

2Manually: put the files in place

~/.claude/skills/notifications-toasts/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/notifications-toasts/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about notifications-toasts

How to install notifications-toasts in Claude Code?

Run npx skills add dylantarre/animation-principles --skill notifications-toasts -a claude-code in your terminal. It places the instruction into ~/.claude/skills/notifications-toasts/SKILL.md.

What does notifications-toasts do?

It teaches AI agents to apply Disney animation principles to UI toasts, giving them precise timings, keyframes, and CSS properties.

What timing rules does this skill prescribe?

It specifies 200-300ms for entrances, 150-250ms for exits, and an auto-dismiss delay of 3000-5000ms.

Source text

SKILL.md · MIT
---
name: notifications-toasts
description: Use when animating notifications, toasts, alerts, snackbars, or system messages to grab attention appropriately
---

# 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

```css
.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

© dylantarre · MIT · dylantarre/animation-principles

Similar skills

Everything for Frontend and UI →

From the same set142

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor