---
name: fractal-motion
description: "Implement or review motion in Fractal product interfaces: state transitions, disclosure, overlays, and loading. Excludes decorative animation in unrelated brands."
---

# Make state changes legible

Read [core](../../../../core.md) and [motion rules](../../references/motion.md); use bundle `motion`.

1. Identify what the motion explains: state, location, causality, or measured progress. Remove motion with no such purpose.
2. Inspect existing component behavior and tokens before adding an animation. Use the relevant pattern's named duration and easing; a specific component rule applies to that component.
3. Choose the properties needed for the change. Prefer transform/opacity; color feedback, shimmer, and necessary disclosure geometry have explicit allowances. Never use `transition: all`.
4. Keep hover to color/surface changes. Only eligible single-step actions use the documented pressed scale; multi-step triggers reveal their panel instead. Product UI has no bounce or spring behavior.
5. Preserve spatial origin, state visibility, and exits no slower than entrances. Loading motion cannot pretend to measure unknown progress.
6. Supply reduced-motion behavior at the same time. Remove ambient loops and nonessential movement without removing content, controls, or state information.

For SidePanel, read its [specific pattern](../../references/components/side-panel.md). Check opening, interruption/repeated interaction, dismissal, and reduced-motion output in context. Use the installed package for existing runtime behavior; extend `fractal-ui` for reusable behavior changes.
