agentleFS
soilmasssoilmass/motion-design-agent/skills/transitions/SKILL.md

transitions

Skill7 starsChanged 10 months agoMITView on GitHub

Page and component transition patterns from Material Design 3. Use when implementing page transitions, navigation animations, or shared element transitions. References M3 container transform, shared axis, and fade through patterns.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when an element transforms into a full view (card → detail).

    line 28
  2. Distinctive:

    Use for sequential navigation (wizard steps, tabs).

    line 55
  3. Distinctive:

    Use for unrelated content with no spatial relationship.

    line 104
  4. Very specific:

    Use these tokens for video content (from duration.tokens.json):

    line 161
  5. Very specific:

    Use simple opacity crossfade (video.crossfade) instead.

    line 178

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Transition Patterns

M3-based transition patterns for navigation and state changes.

Standards Reference

PatternDocumentation
Container Transformm3.material.io/styles/motion/transitions/transition-patterns
Shared Axism3.material.io/styles/motion/transitions/transition-patterns
Fade Throughm3.material.io/styles/motion/transitions/transition-patterns

Pattern Overview

PatternUse CaseDuration
Container TransformCard → Detail viewlong-2 (500ms)
Shared AxisSequential navigationmedium-4 (400ms)
Fade ThroughUnrelated content swapmedium-2 (300ms)

Container Transform

Use when an element transforms into a full view (card → detail).

Characteristics

  • Origin element morphs into destination
  • Maintains spatial relationship
  • Creates strong visual connection

Token

{
  "duration": "{motion.duration.long-2}",
  "easing": "{motion.easing.emphasized}"
}

Implementation (Framer Motion)

<motion.div
  layoutId="card-1"
  transition={{ duration: 0.5, ease: [0.2, 0, 0, 1] }}
>
  {isExpanded ? <DetailView /> : <CardView />}
</motion.div>

Shared Axis

Use for sequential navigation (wizard steps, tabs).

Characteristics

  • Elements move along X, Y, or Z axis
  • Outgoing fades out while moving
  • Incoming fades in while moving

Variants

  • X-axis: Horizontal navigation (tabs)
  • Y-axis: Vertical navigation (lists)
  • Z-axis: Depth changes (dialogs)

Token

{
  "duration": "{motion.duration.medium-4}",
  "easing": "{motion.easing.emphasized}"
}

Implementation (Framer Motion)

const variants = {
  enter: (direction) => ({
    x: direction > 0 ? 100 : -100,
    opacity: 0
  }),
  center: { x: 0, opacity: 1 },
  exit: (direction) => ({
    x: direction < 0 ? 100 : -100,
    opacity: 0
  })
};

<AnimatePresence custom={direction}>
  <motion.div
    key={page}
    custom={direction}
    variants={variants}
    initial="enter"
    animate="center"
    exit="exit"
    transition={{ duration: 0.4, ease: [0.2, 0, 0, 1] }}
  />
</AnimatePresence>

Fade Through

Use for unrelated content with no spatial relationship.

Characteristics

  • Outgoing fades out completely
  • Incoming fades in
  • Brief overlap or sequential

Token

{
  "duration": "{motion.duration.medium-2}",
  "easing": "{motion.easing.standard}"
}

Implementation (CSS)

.fade-through-exit {
  animation: fadeOut 150ms cubic-bezier(0.2, 0, 0, 1) forwards;
}
.fade-through-enter {
  animation: fadeIn 150ms cubic-bezier(0.2, 0, 0, 1) 150ms forwards;
}

@keyframes fadeOut {
  to { opacity: 0; }
}
@keyframes fadeIn {
  from { opacity: 0; }
  to { opacity: 1; }
}

Decision Guide

Is there a persistent element that transforms?
  → Container Transform

Is navigation sequential (steps, tabs)?
  → Shared Axis

Are views unrelated?
  → Fade Through

Web vs Video Transitions

CRITICAL: Web and video transitions have different timing needs.

ContextDurationReason
Web200-400msUser waits for response feedback
Video100-200msViewer expects quick pacing

Video-Specific Durations

Use these tokens for video content (from duration.tokens.json):

TokenDurationFrames @30fpsUse
video.crossfade100ms3Quick opacity blend
video.dissolve150ms5Scene changes
video.scene-transition150ms5Between scenes
video.cut0ms0Instant cut
video.wipe200ms6Directional wipe

Avoid Pixel Dissolve

Never use pixel/dither dissolve for standard video transitions. It:

  • Feels dated/VHS-era
  • Takes too long visually
  • Distracts from content

Use simple opacity crossfade (video.crossfade) instead.

Implementation (Remotion)

import { videoTransition } from '../presets/remotion-m3';

// Quick crossfade between scenes
const opacity = interpolate(
  frame,
  [exitStart, exitStart + videoTransition.crossfade.frames(fps)],
  [1, 0],
  { extrapolateRight: 'clamp' }
);

// Or use the helper
const transitionFrames = getVideoTransitionFrames('crossfade', fps);

See references/container-transform.md for detailed implementation. See references/shared-axis.md for axis variations. See references/fade-through.md for timing patterns.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.