# Motion Design Principles

> Practical motion design rules for agent-made videos and animated UI: timing in frames, easing, pacing, visual hierarchy, on-screen text readability, safe areas, aspect ratios per platform, and reduced-motion and flashing accessibility. Use this skill when designing or reviewing animation in a video (Remotion, HyperFrames, After Effects-style work) or in a web UI, or when a render "feels off" and needs a critique. Activate when: motion design, animation timing, easing, cubic-bezier, pacing, kinetic typography, title card, lower third, safe area, title safe, aspect ratio, 9:16, vertical video, reduced motion, prefers-reduced-motion, flashing content.

- Skill: `latestaiagents/motion-design-principles` (Agent Skill)
- Install (CLI): `npx get-skill add latestaiagents/motion-design-principles`
- Raw SKILL.md: https://api.skillmd.com/api/skills/latestaiagents/motion-design-principles/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Design & Media
- Author: latestaiagents (https://skillmd.com/u/latestaiagents)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/latestaiagents/motion-design-principles

---


# Motion Design Principles

**Motion should explain, direct attention, or connect two states. If it does none of those, cut it.**

Agents tend to over-animate: everything slides, bounces, and fades at once. This skill gives concrete defaults and a critique checklist. It is framework-neutral; apply it in Remotion, HyperFrames, CSS, or any keyframe tool.

## When to Use

- Choosing durations and easing for a composition
- Laying out titles, lower thirds, and captions across aspect ratios
- Critiquing a draft render that feels busy, slow, or hard to read
- Making animated output accessible (reduced motion, flashing)

## Workflow

### Step 1: Think in Frames, Not Milliseconds

Video renders at a fixed frame rate, so durations are frame counts. Convert once and keep a table in the project.

| Duration | 24 fps | 30 fps | 60 fps |
|----------|--------|--------|--------|
| 0.2 s | 4.8 → 5 | 6 | 12 |
| 0.5 s | 12 | 15 | 30 |
| 1 s | 24 | 30 | 60 |

Round to whole frames. Keep the composition frame rate equal to the source footage frame rate; YouTube's upload guidance is to encode at the frame rate the content was recorded at.

### Step 2: Pick Durations by Distance and Importance

Starting points, then judge by eye:

| Motion | Typical range | Notes |
|--------|---------------|-------|
| Small UI feedback (highlight, press) | ~0.1–0.2 s | Should feel instant |
| Element entering / leaving | ~0.25–0.5 s | Larger distance → longer |
| Full-frame transition / scene change | ~0.4–0.8 s | Longer feels "cinematic", then "slow" |
| Hold on readable text | Long enough to read twice | See Step 5 |

For reference, Material Design 3's motion tokens span 50 ms (`short1`) to 1000 ms (`extra-long4`); UI transitions generally sit in the short-to-medium band. Video titles can hold longer because the viewer is not trying to act.

### Step 3: Ease Almost Everything

Linear motion reads as mechanical. Use linear only for continuous motion (tickers, progress bars, rotation loops) or when matching a physical constant speed.

| Intent | Curve | Example (Material 3 token values) |
|--------|-------|-----------------------------------|
| Default move between two on-screen positions | Standard | `cubic-bezier(0.2, 0, 0, 1)` |
| Entering the frame (arrive and settle) | Decelerate | `cubic-bezier(0.05, 0.7, 0.1, 1)` (emphasized decelerate) |
| Leaving the frame (gather speed, exit) | Accelerate | `cubic-bezier(0.3, 0, 0.8, 0.15)` (emphasized accelerate) |

Rules:

- **Enter with ease-out, exit with ease-in.** Exits are usually shorter than entrances.
- **Overshoot / springs sparingly.** One springy element per scene draws the eye; five is noise.
- **Use the framework's interpolation helpers** (for example Remotion's `interpolate`/`spring`, or the animation library a HyperFrames composition uses) rather than hand-rolled math. See their official skills.

### Step 4: Direct Attention with Hierarchy and Stagger

- One focal point per moment. Animate the thing the VO is talking about; keep everything else still.
- Stagger related elements (list items, chart bars) by a few frames each so the eye reads them in order. Keep total stagger short enough that the last item arrives before the viewer loses interest.
- Motion direction should mean something: content that "comes next" enters from the reading direction; dismissed content leaves the way it came.
- Change one property at a time when possible (position *or* scale *or* opacity), especially on text.

### Step 5: Make On-Screen Text Readable

- **Size for the smallest screen it will play on.** Vertical social video is watched on phones; test by viewing the render on a phone, not a monitor.
- **Contrast:** text over footage needs a scrim, shadow, or solid plate. Check contrast on the busiest frame, not the calmest.
- **Hold time:** a line must stay still long enough to read it twice at a relaxed pace. Do not animate text while the viewer is reading it.
- **Few words:** on-screen text summarizes, it does not transcribe the VO. Captions handle the transcript.
- **No orphan text:** avoid a single word on the last line of a title.

### Step 6: Respect Safe Areas and Aspect Ratios

Broadcast safe areas (EBU R 95, 16:9): keep essential action inside the **action safe area** (3.5% in from each edge) and graphics inside the **graphics safe area** (5% in from each edge). On the web these are a sensible minimum margin.

Social platforms overlay UI (captions, buttons, usernames, progress bars) on top of video, particularly in vertical feeds. Their safe-zone guidance changes; check the platform's current creative spec before final layout and keep text well inside the frame, away from the bottom and right edges in vertical feeds.

| Placement | Aspect ratio | Source |
|-----------|--------------|--------|
| YouTube (standard player on computer) | 16:9 | YouTube Help: recommended upload encoding settings |
| YouTube Shorts | Square or vertical, up to 3 minutes | YouTube Help: upload Shorts |
| Instagram Reels, TikTok, other vertical feeds | Commonly 9:16 vertical | Check each platform's current spec page |
| LinkedIn, X, feed posts | Varies by placement (landscape, square, vertical) | Check each platform's current spec page |

Plan composition per ratio: in 9:16, stack elements vertically and keep the subject in the middle band; in 16:9, use horizontal thirds.

### Step 7: Make Motion Accessible

- **Flashing:** nothing may flash more than three times in any one-second period unless it stays below the general and red flash thresholds (WCAG 2.3.1). Avoid strobing transitions, rapid cuts between light and dark frames, and flickering glitch effects.
- **Reduced motion in interactive output:** when motion runs in a browser (HTML previews, embedded animations, animated landing pages), honour `prefers-reduced-motion`:

```css
.title { animation: slide-in 400ms cubic-bezier(0.05, 0.7, 0.1, 1) both; }

@media (prefers-reduced-motion: reduce) {
  .title { animation: fade-in 200ms linear both; } /* replace movement with a fade */
}
```

- **Rendered video cannot read user preferences.** Keep large-scale panning, zooming, and parallax restrained, and do not make motion the only carrier of information (Apple's HIG: "Make motion optional").
- Provide captions (see `captions-and-transcription`).

## Critique Checklist

Run this on every draft render:

- [ ] Can you say what each animation is for?
- [ ] Is there exactly one focal point at each moment?
- [ ] Do entrances ease out and exits ease in?
- [ ] Is every text line still and readable for long enough?
- [ ] Do all text and key visuals sit inside safe areas in every aspect ratio?
- [ ] Any sequence with more than three flashes per second?
- [ ] Does it still make sense muted?

## Best Practices

1. Store durations as frame constants at the composition's fps
2. Default to ease-out for entrances and ease-in for exits; use linear only for continuous motion
3. Animate one focal element at a time; keep the rest still
4. Never animate text while it needs to be read
5. Lay out each aspect ratio deliberately; do not rely on auto-crop
6. Check platform safe zones from the platform's current spec, not from memory
7. Treat flashing and large-scale motion as accessibility issues, not style choices

## References

- Material Design 3 motion tokens (easing and duration values): https://github.com/material-components/material-web/blob/main/tokens/versions/v0_192/_md-sys-motion.scss
- Apple Human Interface Guidelines, Motion: https://developer.apple.com/design/human-interface-guidelines/motion
- EBU R 95, Safe areas for 16:9 television production: https://tech.ebu.ch/docs/r/r095.pdf
- MDN, `prefers-reduced-motion`: https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-motion
- WCAG 2.2 SC 2.3.1 Three Flashes or Below Threshold: https://www.w3.org/WAI/WCAG22/Understanding/three-flashes-or-below-threshold.html
- YouTube recommended upload encoding settings: https://support.google.com/youtube/answer/1722171
- YouTube Shorts upload requirements: https://support.google.com/youtube/answer/12779649

