orchestrated-sequences — Claude Code skill: choreographed motion
A skill for multi-part animation: it tells you how to set delays, easing curves and element roles so a reveal reads as one composed moment.
npx skills add dylantarre/animation-principles --skill orchestrated-sequences -a claude-codeWhat orchestrated-sequences does
The skill covers orchestration through the Disney principles: one elasticity across all elements, anticipation that starts with the lead element, a clear hierarchy where secondary parts support rather than compete, and a cascading settle. It ships CSS for linear, accelerating and decelerating staggers, a set of cubic-bezier curves from a single easing family, and a .orchestrated-item pattern that flips to .visible.
For longer scenes there is a JavaScript example: an array of objects with a selector, delay and duration that drives the sequence. Typical ground is a page load, a dashboard reveal, a card grid, a menu opening, a chart build or onboarding steps.
One thing to plan for: the skill calls pose to pose mandatory here, because choreography needs precise timing control. Build the sequence straight ahead and the elements will drift out of sync.
What it helps with
- stagger a card grid reveal
- set delays for onboarding steps
- match easing curves across primary and secondary elements
- cascade the settle after a lead action
- drive a sequence from a JavaScript array
Example prompts for the agent
- build a staggered reveal for the card grid, 75ms between items
- sequence the hero, title, subtitle and CTA on page load
- pick one easing family for the primary and secondary elements
How to install orchestrated-sequences
1Skills CLI (Vercel)
npx skills add dylantarre/animation-principles --skill orchestrated-sequences -a claude-code2Manually: put the files in place
~/.claude/skills/orchestrated-sequences/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/orchestrated-sequences/
1Skills CLI (Vercel)
npx skills add dylantarre/animation-principles --skill orchestrated-sequences -a codex2Manually: put the files in place
.agents/skills/orchestrated-sequences/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dylantarre/animation-principles --skill orchestrated-sequences -a cursor2Manually: put the files in place
.cursor/skills/orchestrated-sequences/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dylantarre/animation-principles orchestrated-sequences2Manually: put the files in place
.github/skills/orchestrated-sequences/SKILL.md1Skills CLI (Vercel)
npx skills add dylantarre/animation-principles --skill orchestrated-sequences -a gemini-cli2Platform CLI
gemini skills install https://github.com/dylantarre/animation-principles --path skills/10-by-time-scale/orchestrated-sequencesManually: put the files in place
.devin/skills/orchestrated-sequences/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add dylantarre/animation-principles --skill orchestrated-sequences -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about orchestrated-sequences
How do I install orchestrated-sequences in Claude?
Run npx skills add dylantarre/animation-principles --skill orchestrated-sequences -a claude-code. The skill lands at ~/.claude/skills/orchestrated-sequences/SKILL.md.
What does orchestrated-sequences do?
It helps you plan a multi-part animation: when each element enters, how it moves, and how the elements relate. It includes CSS stagger examples, easing curves and a JS sequence pattern.
Why does the skill insist on pose to pose?
Choreography depends on precise timing control, so delays and durations are set up front. Animating straight ahead makes it hard to keep several elements in sync.
Source text
SKILL.md · MIT
---
name: orchestrated-sequences
description: Use when building multi-part animation sequences - staggered reveals, choreographed UI, coordinated motion where multiple elements work together
---
# Orchestrated Sequences
Orchestrated sequences coordinate **multiple elements across time**. Like a conductor directing an orchestra, you control when each element enters, how it moves, and how elements relate.
## Disney Principles for Orchestration
### Ensemble Coordination
**Squash & Stretch**: Unified style - all elements should share consistent elasticity. Mix bouncy and stiff looks chaotic.
**Anticipation**: Staggered preparation - lead element anticipates first, others follow in sequence.
**Staging**: Clear hierarchy - primary action leads, secondary elements support but don't compete.
**Straight Ahead/Pose to Pose**: Pose to pose mandatory - choreography requires precise timing control.
**Follow Through**: Cascading settle - elements land in sequence with overlapping follow-through.
**Slow In/Slow Out**: Shared easing family - use variations of same curve for cohesion.
**Arcs**: Coordinated paths - elements should move in complementary directions, not randomly.
**Secondary Action**: Intentional support - every element has a role in the composition.
**Timing**: The heart of orchestration - stagger delays, duration variations, tempo changes.
**Exaggeration**: Proportional emphasis - primary elements more exaggerated, supporting less.
**Solid Drawing**: Consistent dimensional logic - shared perspective, depth, scale relationships.
**Appeal**: Unified performance - the sequence should feel like one composed moment.
## Timing Strategies
```css
/* Linear stagger - equal delays */
.item:nth-child(n) {
transition-delay: calc(var(--index) * 50ms);
}
/* Accelerating stagger - getting faster */
.item:nth-child(1) { transition-delay: 0ms; }
.item:nth-child(2) { transition-delay: 80ms; }
.item:nth-child(3) { transition-delay: 140ms; }
.item:nth-child(4) { transition-delay: 180ms; }
/* Decelerating stagger - slowing down */
.item:nth-child(1) { transition-delay: 0ms; }
.item:nth-child(2) { transition-delay: 40ms; }
.item:nth-child(3) { transition-delay: 100ms; }
.item:nth-child(4) { transition-delay: 180ms; }
```
## Easing Recommendations
```css
/* Cohesive family - same curve, different durations */
.primary { transition: all 400ms cubic-bezier(0.16, 1, 0.3, 1); }
.secondary { transition: all 350ms cubic-bezier(0.16, 1, 0.3, 1); }
.tertiary { transition: all 300ms cubic-bezier(0.16, 1, 0.3, 1); }
/* Sequence curve - smooth start, confident end */
animation-timing-function: cubic-bezier(0.22, 1, 0.36, 1);
```
## Best Use Cases
- Page load sequences
- Dashboard reveals
- Card grid animations
- Navigation menu opens
- Feature section reveals
- Data visualization builds
- Onboarding step sequences
- List population animations
## Implementation Pattern
```css
/* Staggered reveal system */
.orchestrated-item {
opacity: 0;
transform: translateY(20px);
transition: opacity 300ms ease-out,
transform 400ms cubic-bezier(0.16, 1, 0.3, 1);
}
.orchestrated-item.visible {
opacity: 1;
transform: translateY(0);
}
/* Apply delays via CSS custom properties or nth-child */
.orchestrated-item:nth-child(1) { transition-delay: 0ms; }
.orchestrated-item:nth-child(2) { transition-delay: 75ms; }
.orchestrated-item:nth-child(3) { transition-delay: 150ms; }
.orchestrated-item:nth-child(4) { transition-delay: 225ms; }
```
```javascript
// JS orchestration for complex sequences
const sequence = [
{ el: '.hero', delay: 0, duration: 500 },
{ el: '.title', delay: 100, duration: 400 },
{ el: '.subtitle', delay: 200, duration: 350 },
{ el: '.cta', delay: 350, duration: 400 },
];
```
## Key Insight
Orchestration is **composition in time**. Just as visual design arranges elements in space, animation orchestration arranges motion in time. The goal is a single, coherent performance, not a collection of individual animations.
© dylantarre · MIT · dylantarre/animation-principles