К основному содержанию
скилл CX Codex

choreograph — скилл для Claude Code: связать анимации элементов

Скилл choreograph для Claude Code и других сред, который связывает разрозненные элементы интерфейса в единую анимацию. Координирует время, порядок и перекрытие движений для получения предсказуемого результата.

MIT 32 800 установок ★ 58 678 обновлён 2026-10-11

Установить в Claude Code · Через Skills CLI (Vercel) Все способы и платформы ↓
npx skills add emilkowalski/skills --skill choreograph -a claude-code
Открыть на GitHub

Что делает choreograph

Этот скилл помогает выстроить отношения между анимациями, чтобы группа элементов двигалась как единое целое. Он задаёт роли для каждого компонента — от главного элемента до фоновых украшений, исключая хаотичные движения. Скилл применяет принципы дизайна, которые помогают избежать нагромождения эффектов и лишних задержек.

Система работает через выбор отношений для каждой пары анимируемых объектов. Агент определяет, должны ли элементы двигаться вместе, последовательно или с перекрытием, опираясь на важность каждого компонента. Скилл запрещает использовать одинаковую задержку для всех элементов, так как это делает движение механическим. Для корректной работы требуется понимать логику перекрытия слоёв и быть готовым сократить количество подвижных частей.

При работе с последовательностями агент следит, чтобы анимация не прерывала взаимодействие пользователя с интерфейсом. Всё, что появилось на экране, должно сразу реагировать на клики.

Какие задачи решает

  • связать движение списка и заголовка в один жест
  • исправить прерывистую анимацию появления меню
  • настроить перекрытие анимаций при смене контента
  • убрать лишние задержки в интерфейсе

Примеры запросов агенту

  • Сделай анимацию списка items более плавной, используя логику choreograph.
  • Настрой последовательное появление кнопок в панели, чтобы это не выглядело как очередь.
  • Помоги синхронизировать анимацию выхода старой формы и входа новой.

Как установить choreograph

1Через Skills CLI (Vercel)

npx skills add emilkowalski/skills --skill choreograph -a claude-code

2Вручную: положить файлы

~/.claude/skills/choreograph/SKILL.md

Папка скилла целиком; для одного проекта — .claude/skills/choreograph/

По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов

Вопросы о choreograph

Как установить choreograph в Claude Code?

Выполните npx skills add emilkowalski/skills --skill choreograph -a claude-code. Конфигурация доступна в ~/.claude/skills/choreograph/SKILL.md.

Что делает choreograph?

Скилл координирует порядок, длительность и перекрытие анимаций нескольких элементов. Это превращает набор разрозненных движений в единый, осмысленный жест интерфейса.

Зачем нужен choreograph?

Он помогает избавиться от "механических" анимаций, замедляющих работу пользователя. Скилл внедряет философию анимации Emil Kowalski, основанную на сокращении числа движущихся частей и их правильной последовательности.

Исходный текст

SKILL.md · MIT
---
name: choreograph
description: Coordinate several elements that animate together — decide what moves, in what order, how much they overlap, and what stays still — so a group reads as one intentional motion instead of a pile of separate animations. Use when building or fixing a staggered list, a hero entrance, a view swap inside a container, a multi-step flow, an element leaving while its siblings close the gap, a morph between rich states, or any interaction with several moving parts (icon + background + lines, panel + content, items flying into a target). Triggers on — stagger, sequence, choreography, "one after another", crossfade, AnimatePresence mode, hero entrance, multi-step, useAnimate, "feels mechanical", "too much going on", "feels slow to open".
---

# Choreographing Motion

## Initial Response

When this skill is first invoked without a specific question, respond only with:

> I'm ready to choreograph your animations, my knowledge comes from Emil Kowalski's animation philosophy.

Do not provide any other information until the user asks a question.

This skill handles the relationships *between* animations: order, overlap, timing and stillness. A single animation's easing, duration and origin belong to `animate`. Whether something should animate at all is `find-animation-opportunities` or `remove-animations`. Once two or more things move in response to the same event, the decisions here apply.

## Operating Posture

Agents choreograph by adding. Every child gets a `delay: i * 0.1`, the panel slides in and then its items trickle in, and the old view waits for the new one politely. Each piece is smooth on its own. Put together, the user waits for the interface to finish performing before they can use it.

Good choreography is mostly about **cutting moving parts and running the remaining ones in parallel**. Sequence only when order carries meaning: reading order, cause and effect, or one thing physically arriving before another. When a sequence feels right it reads as one gesture, a wave. When it feels wrong it reads as a queue.

## Hard Rules

1. **One entrance per container.** If the panel slides in, its content is already there. Never animate a parent's entrance *and* stagger its children. That's two layers of entrance, and the user waits through both.
2. **Never stagger on high-frequency or keyboard-triggered UI.** Dropdown items, menu rows, command palettes, tab content and list rows the user opens many times a day appear together, or with no animation. A stagger looks nice the first time and slows every use after that.
3. **Uniform stagger is forbidden.** If every item has the same delay, distance, duration and easing, the group moves like a metronome. Uniform delays affect the group the way `linear` easing affects a single element. Vary the timing by importance.
4. **Choreography never blocks interaction.** Everything on screen must be clickable as soon as it's visible, and a delayed item must not hold back a button the user is already reaching for.
5. **Every sequence must survive interruption.** If a sequence breaks or replays out of order when triggered mid-flight, it isn't finished (see "Interruption").

## Step 1 — Cast the Elements

List every element that moves in response to the event and give each one a role. Do this before writing any timing:

| Role | What it is | Treatment |
| --- | --- | --- |
| **Lead** | The one thing the user must notice: the title, the new view, the item being acted on | Moves first, travels the most, stays on screen the longest |
| **Support** | Secondary content that follows the lead: subtitle, CTAs, the rest of the list | Follows with shorter, smaller motion |
| **Decoration** | Pills, badges, background accents, dividers | Fades only, no movement. Or nothing at all |
| **Static** | Everything else, including containers whose content animates | Doesn't animate |

If more than one element wants to be the lead, the design has a hierarchy problem, and motion can't solve it. Say so.

Most groups shrink at this step. A side panel with eight menu items becomes one move: the panel slides, and the items are just there.

## Step 2 — Pick the Relationship for Each Pair

Any two moving parts relate in one of four ways. Choose one deliberately for each pair:

```
Do both elements belong to the same visual object or the same moment?
├── Yes → TOGETHER. Same start, same timing family. (Drawer height + its content; a chip leaving + siblings closing the gap.)
└── No → Does the order carry meaning (reading order, cause → effect, one arrives before the other)?
         ├── No → TOGETHER. Order without meaning is just delay.
         └── Yes → Would showing both at once look broken (overlap, passing through, two rich views fighting)?
                   ├── Yes → SEQUENCE. The second starts as the first finishes, or just before it.
                   └── No → OVERLAP. A stagger: the second starts while the first is still moving.
```

Then a fifth option that isn't a timing at all:

- **Carry.** When you can't control a child's motion directly (shared layout / `layoutId` animations, for example), animate the **parent** and let the children come along. Images flying into a trash can drop *into* it because the container they belong to moves, not because each image was tuned on its own.

### Together, by default

- **An element that leaves must stop taking up space immediately.** Take it out of the layout at the moment of removal, so its siblings slide into the gap *while* it fades. Without that, the gap only closes after the exit finishes. Both movements are smooth, but the pause between them makes the whole interaction feel slow. In Motion this is `AnimatePresence mode="popLayout"`. Without a library, set the exiting element to `position: absolute` at its current position before animating it out.
- **Swapping views in the same container is a crossfade, so the old view exits while the new one enters.** That means `popLayout` again, not the default `sync` mode, which keeps the exiting view in the layout so both stack until the exit finishes.
- **Sub-animations of one component share a timing family**, so the component reads as a single entity. If a drawer opens in 500ms and then resizes in 200ms, it reads as two different objects. Bring both down to one duration. Inner animations can have a *lighter* curve than the container (for example, a slower content fade so the swap is visible). They must stay in the same easing family, though: an `ease-in-out` body inside an `ease-out` container feels out of sync. Use `MotionConfig` (or one shared CSS custom property) to set the family once.

### Overlap: the stagger

- **Product UI: 30–80ms between items, with the total under ~300ms.** For long lists, stagger only the first handful and let the rest arrive with the last one. Never let item 20 wait 20× the delay.
- **Marketing and first-run moments get more room.** A hero or personal site can run 100–150ms steps on 0.5–0.6s entrances and read as a wave. It's seen once per visit, and the motion is part of the message.
- **Order follows importance, not DOM order.** Usually those match top to bottom, but check. Group the title and first paragraph into one beat (both at step 0) when they read as one unit.
- **Vary the treatment as well as the delay.** The lead slides the furthest. Support slides less. Decoration fades in place. Delays that shrink as the group goes on (or a stagger with easing applied to the delays) read as organic. Equal gaps read as mechanical.
- **Direction follows the reading direction or the cause.** Top to bottom for content, outward from the point of interaction for things the user triggered.

### Sequence: when to wait

Sequence only when overlap would look wrong:

- **Two rich states in a container that changes size in both dimensions.** Morphing between two dense views (a Dynamic Island-style container that changes width *and* height) looks chaotic when both are visible. The old content leaves before the new content starts (`mode="wait"`). If you want a crossfade here anyway, use the duplicate-view technique in [RECIPES.md](RECIPES.md).
- **One element would visibly pass through another.** If items fly into a container whose front face is drawn above them, show the front only when the items have almost landed. Time it with a delay, not with a full sequence.
- **Drawing has a cause and an effect.** A checkbox square draws, and *then* the checkmark draws. The second starts just before the first ends, and both need `forwards` (or `both`) so they hold their end state.

Make the handoff overlap slightly. Starting the second move just before the first ends is what turns a queue into one gesture.

## Step 3 — Sync Secondary Motion to the Moment That Matters

Each supporting animation hooks onto a specific moment of the lead: its start, its impact, or its settle. It doesn't get a delay that happens to look about right.

- **Sync to the cause, not to the trigger that came before it.** In a hover-then-click interaction, the background pulses *on the click*, together with the press, not on hover. Each secondary effect lands on the event it belongs to.
- **Land the accents with the lead.** Motion lines or sparkles around an icon should complete as the main shape finishes its move: a short, punchy burst in the last ~20% of the timeline (`times: [0.7, 0.9]`), with the most important line starting first and the others ~40ms behind.
- **A repeat action skips the buildup.** Once the hover state is in place, a click plays immediately, with no delay on the background and the morph starting earlier in its timeline. Keep the internal proportions the same and move the whole thing earlier.

## Step 4 — Adapt Timing to What Changed

Fixed timing is wrong when the size of the change varies:

- **Scale the duration by distance.** When a container resizes between views, a big jump needs the full fade. A tiny jump with the same fade looks like a flicker. Derive the duration from the delta and clamp it (`clamp(0.15s, Δheight / 500, 0.27s)`). See RECIPES.md.
- **Scale the bounce by size.** Smaller elements need more bounce to read as alive. A large view with the same bounce takes longer to settle and looks faster or heavier than the rest. Tune the bounce per state.
- **When there's a small, finite number of states, hardcode the values per transition.** A dozen hand-tuned transitions beat a clever formula you can't fine-tune. Reach for a formula only when there are too many states to tune by hand.

## Step 5 — Direction and Exits

- **Direction follows the user's mental model.** Forward moves content to the left (new content enters from the right). Back moves it to the right. If Next and Back slide the same way, the motion contradicts the action. Content switching between sibling menus enters from the side of the trigger the user came from.
- **Exits read state when they start, so pass the direction through `custom`** on both `AnimatePresence` and the child. Otherwise the leaving element animates with the old direction.
- **Exits are simultaneous, shorter and simpler.** Don't reverse-stagger items out when something closes. The user has already decided to leave, so everything goes at once.
- **An exit matches its entry.** Something that slid in from the right leaves toward the right on close. It doesn't just fade.

## Interruption

A sequence has more states than a single animation. Test each of these:

- **Re-trigger mid-sequence.** Hover out halfway through a hover sequence. Click Next twice fast. Switch menus while the first is still opening. Each run must stop the in-flight animations before starting new ones. Never stack them.
- **Wait for completion before chaining.** An idle loop that resumes after a hover-out starts only after *all* reset animations finish (`await Promise.all(...)`), or it fights the reset.
- **Rapid view switching** with `AnimatePresence` can leave two children mounted. Check it explicitly, and make sure each child has a stable, unique `key`.

## Attention Loops

An idle animation that invites interaction (a hand that occasionally taps, an icon that wiggles) waits a few seconds before the first run (~2.5s) and repeats rarely (`repeatDelay` ~6s). It stops while the user is interacting, and resumes only after the interaction's reset has finished.

## Reduced Motion

Collapse the choreography; don't just shorten it. Under `prefers-reduced-motion: reduce`, drop the delays and the movement, keep the opacity, and let the group appear together. If the sequence *is* the explanation (a step-by-step illustration), jump between its frames instead of animating between them.

## Implementation

Pick the lightest tool that can express the relationships. Recipes for each are in [RECIPES.md](RECIPES.md).

- **CSS:** a per-item `--delay` custom property with shrinking gaps, on a keyframe with `animation-fill-mode: both` so delayed items don't flash their final state first. Best for one-shot entrances.
- **Motion, declarative:** variants with `delayChildren: stagger(...)` on the parent. `stagger` takes `from` and `ease`, which give you non-uniform delays for free. Use this for groups that enter and exit with React state.
- **Motion, imperative (`useAnimate`):** use it only when several elements coordinate across several events (hover, click, idle timer) and you need to await completion. It's more powerful and much harder to maintain, so don't use it for a simple stagger.

## Workflow

1. **Inventory.** List every element that moves on the event, with `file:line`.
2. **Cast.** Assign Lead / Support / Decoration / Static. Remove the movement from everything that isn't Lead or Support.
3. **Relate.** Choose Together / Overlap / Sequence / Carry for each pair, and record why.
4. **Write the timeline** before coding (format below). Check it against the budgets: product UI groups finish in ≲300ms, and no stagger on high-frequency surfaces. Done when every inventoried element has a row with a role and a relationship.
5. **Implement** with the lightest tool that fits.
6. **Verify.** Record the interaction and step through it frame by frame. A wave and a queue look the same at full speed in your head and different on the recording. Run the interruption checks. Then imagine the 50th use of the day. If you'd skip it, cut it.

## Required Output Format

### Part 1 — Timeline

One row per moving element, in start order:

| Element | Role | Starts | Duration | Motion | Relationship |
| --- | --- | --- | --- | --- | --- |
| Title | Lead | 0ms | 600ms | fade + 12px rise | — |
| Subtitle | Support | 80ms | 500ms | fade + 8px rise | Overlaps title |
| CTAs | Support | 140ms | 500ms | fade + 6px rise | Overlaps subtitle |
| Pill | Decoration | 0ms | 400ms | fade only | Together with title |
| Background | Static | — | — | — | — |

### Part 2 — What doesn't move, and why

List up to 5 elements you deliberately removed motion from, each with its reason ("Menu items: one entrance per container, the panel carries them"). If you removed none, say so.

### Part 3 — Feel check

Say what can't be judged from code: whether the stagger reads as a wave, whether the crossfade reads as one object. Name the specific moment to scrub on a recording.

## Tone

Talk in relationships and moments ("the lines land with the click"), not adjectives. When a sequence is fine as it is, say so. When the right choreography is no choreography at all, say that too.

© emilkowalski · MIT · emilkowalski/skills

Похожие скиллы

Все скиллы по теме «Фронтенд и UI» →
animate aladicf Скилл animate для Claude Code добавляет в интерфейс переходы, микроинтеракции, жесты и состояния наведения. Делает UI понятнее и отзывчивее при частом использовании. CX Codex +1 696установок large-500-800ms dylantarre Скилл large-500-800ms для Claude Code научит агента строить крупные движения между 500 и 800 миллисекундами. Запускается на героических переходах, сложных раскрытиях и моментах, которые должны остановить внимание пользователя. CX Codex +1 558установок slow-800-1200ms dylantarre Скилл slow-800-1200ms для Claude Code, Cursor, Codex и других платформ — задаёт принципы медленной анимации в диапазоне 800–1200 мс. Применяется при сборке стартовых экранов, туториалов и драматичных раскрытий контента. CX Codex +1 547установок transitions-polish Jakubantalik Скилл transitions-polish для Claude Code, Cursor и других платформ, который настраивает существующие переходы по шкале токенов transitions.dev: длительность, расстояние, масштаб, размытие и кривые ускорения. CX Codex +1 14 800установок top-design wondelai Скилл top-design направляет агента на создание веб-интерфейсов уровня Awwwards с акцентной типографикой, выверенной анимацией и оценкой макета по десятибалльной шкале. CX Codex +1 7 800установок motion-patterns jeff Скилл motion-patterns для Claude Code добавляет готовые паттерны анимации для React и Next.js. Оформляет кнопки, модальные окна, toast, переходы страниц и scroll-reveal. CX Codex +1 6 500установок

Из того же набора19

Весь набор →
animate-expo Скилл animate-expo для Claude Code, который автоматизирует создание анимаций в React Native и Expo. Агент выбирает инструменты и методы реализации, ориентируясь на производительность UI-потока. CX Codex +1 189 400установок write-swift Скилл write-swift для Claude Code помогает писать и разбирать современный Swift. Включается при создании, ревью или миграции Swift-кода, а также при поиске ошибок конкурентности и проблем с памятью. CX Codex +1 169 400установок mobile-native Скилл mobile-native убирает мелочи, из-за которых веб-приложение на телефоне выдаёт себя: залипающий hover, вспышку при тапе, ошибку с 100vh. CX Codex +1 141 900установок break-ui Скилл break-ui для Claude Code находит уязвимости интерфейса с помощью граничных данных и отчёта о сбоях. CX Codex +1 121 000установок animation-performance Скилл animation-performance для Claude Code, помогающий удерживать веб-анимации в рамках бюджета кадров. Диагностирует причины рывков и просадок FPS, предлагая замену ресурсоемких свойств на композитные. CX Codex +1 93 400установок remove-animations Скилл remove-animations для Claude Code удаляет лишнюю анимацию из интерфейса и сокращает ту, у которой есть функция. Запускается по просьбе уменьшить движение или найти анимации, из-за которых приложение кажется медленным. CX Codex +1 47 000установок gestures Скилл gestures для Claude Code помогает создавать и чинить перетаскивание, свайпы и шторки. Подключается к задачам, где элемент должен двигаться за пальцем и реагировать на отпускание жеста. CX Codex +1 24 200установок learn-taste Скилл learn-taste для Claude Code превращает правки по дизайну в правила с объяснениями. Он разбирает замечания из текущей сессии и предлагает, что сохранить для следующих задач. CX Codex +1 13 700установок

Спонсоры проекта

Компании, которые помогают держать аналитику открытой