Skip to main content
skill CX Codex

large-500-800ms — Claude Code skill: large 500–800ms animations

A skill that tells your coding agent how to build 500–800ms animations: hero transitions, complex reveals, moments that deserve the user's attention.

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

What large-500-800ms does

This skill covers what changes when an animation runs 500–800ms. At that length motion becomes an event, and people stop to watch. The author's advice is to keep the range for significant moments only, not for everyday interface actions.

Inside is a walkthrough of the twelve Disney animation principles at large scale. Squash and stretch goes to 20–30% deformation, anticipation stretches to 150–200ms, follow through keeps elements moving 100–200ms past the main action. Timing lands at 30–48 frames at 60fps. Four easing curves ship with it, including cubic-bezier(0.16, 1, 0.3, 1) for a dramatic entrance and cubic-bezier(0.68, -0.55, 0.265, 1.55) for an elastic landing. There is also an implementation pattern with staggered delays for a title, subtitle and call to action.

The catch is straightforward: put this duration on a common action and the interface starts to drag. Several large animations competing on one screen break staging too. Worth checking how many of those moments you actually have per view.

What it helps with

  • build a hero section transition on page load
  • introduce a major feature during onboarding
  • celebrate a completed action
  • reveal portfolio cards one after another
  • pick an easing curve for a dramatic entrance

Example prompts for the agent

  • Build a 700ms hero transition with the title and button appearing in sequence
  • Which animation principles fit a 600ms portfolio card reveal?
  • Pick an easing curve for an element that lands elastically after a large move

How to install large-500-800ms

1Skills CLI (Vercel)

npx skills add dylantarre/animation-principles --skill large-500-800ms -a claude-code

2Manually: put the files in place

~/.claude/skills/large-500-800ms/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/large-500-800ms/

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

Questions about large-500-800ms

How do I install large-500-800ms in Claude?

Run npx skills add dylantarre/animation-principles --skill large-500-800ms -a claude-code. The skill file then lands at ~/.claude/skills/large-500-800ms/SKILL.md.

What does large-500-800ms do?

It gives the agent rules for 500–800ms animations: how to apply the Disney principles at large scale, which easing curves to use, and how to stagger elements into view.

When should I use this duration?

Hero reveals, major feature introductions, success celebrations, onboarding sequences and dashboard data loads. For common actions the author recommends shorter durations.

Source text

SKILL.md · MIT
---
name: large-500-800ms
description: Use when building larger movement animations between 500-800ms - hero transitions, complex reveals, animations that tell a story and deserve attention
---

# Large Animations (500-800ms)

At 500-800ms, animations become **events**. Users stop and watch. Reserve this duration for significant moments that deserve attention and communicate importance.

## Disney Principles at Large Scale

### Full Expression of All Principles

**Squash & Stretch**: Dramatic deformation - 20-30% stretch visible and characterful. Objects feel elastic and alive.

**Anticipation**: Extended wind-up - 150-200ms anticipation sells the action. Clear "about to happen" signal.

**Staging**: Sophisticated choreography - multiple elements with clear hierarchy and timing offsets.

**Straight Ahead/Pose to Pose**: Definitely pose to pose - complex motion needs keyframe control.

**Follow Through**: Extended settling - elements continue moving 100-200ms after main action completes.

**Slow In/Slow Out**: Dramatic easing - strong deceleration creates impact at endpoints.

**Arcs**: Essential - all movement should follow natural curved paths.

**Secondary Action**: Rich layering - primary, secondary, and tertiary actions possible.

**Timing**: 30-48 frames at 60fps. Full cinematic range.

**Exaggeration**: Go bold - this duration supports theatrical expression.

**Solid Drawing**: Full 3D transforms - depth, perspective, complex rotations.

**Appeal**: Memorable moments - users will recall these animations.

## Easing Recommendations

```css
/* Dramatic entrance */
transition: all 600ms cubic-bezier(0.16, 1, 0.3, 1);

/* Powerful deceleration */
transition: all 700ms cubic-bezier(0, 0.55, 0.45, 1);

/* Elastic landing */
transition: transform 650ms cubic-bezier(0.68, -0.55, 0.265, 1.55);

/* Smooth, cinematic */
transition: all 800ms cubic-bezier(0.25, 0.1, 0.25, 1);
```

## Best Use Cases

- Hero image/section reveals
- Major feature introductions
- Success/completion celebrations
- Onboarding sequences
- Dashboard data loads
- Portfolio piece reveals
- First-time user experiences
- Important state changes

## Implementation Pattern

```css
.hero-reveal {
  opacity: 0;
  transform: translateY(60px) scale(0.9);
  transition: opacity 500ms ease-out,
              transform 700ms cubic-bezier(0.16, 1, 0.3, 1);
}

.hero-reveal.visible {
  opacity: 1;
  transform: translateY(0) scale(1);
}

/* Staggered reveal with follow-through */
.hero-title { transition-delay: 0ms; }
.hero-subtitle { transition-delay: 100ms; }
.hero-cta { transition-delay: 200ms; }
```

## Warning Signs

- If users seem impatient, duration is too long
- If used for common actions, flow suffers
- If multiple large animations compete, staging fails

## Key Insight

Large animations are **moments of theater**. They punctuate the experience and create memory. Use sparingly - every large animation should earn its duration.

© dylantarre · MIT · dylantarre/animation-principles

Similar skills

Everything for Frontend and UI →

From the same set86

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