The PR adds a drawer and a new easing: cubic-bezier(0.4, 0, 0.2, 1) in one file, ease-in-out in another, and a commented “TODO: tweak.” The design system already has --motion-ease-standard and --motion-ease-emphasized. The new numbers may be fine. Nobody previewed them next to the existing curves, and they are not on the token list.
I’ve started treating a raw cubic-bezier in a component as a draft value, not as a token. Tune it against a moving preview, then write the winning value into the motion scale — or reuse a token that is already close enough.
This is not a request to invent a new easing for every animation. Most UI motion should use the standard and emphasized curves the team already shipped.
When a one-off curve is actually needed
Good fit:
- A new motion token the design team asked for, with a name and a use
- A preview to decide whether the existing standard curve is enough
- Comparing two candidate values before a token change
Poor fit:
- A one-off bezier in a leaf component when
--motion-ease-standardalready exists - Copying a bezier from a random CodePen into a production token without a preview
- “Improving” the standard curve in a single button hover
If reduced motion is on, the curve does not matter; the component still needs the reduced-motion path. Do not tune a bezier and skip that path.
A simple motion-token policy
- Reuse the existing ease tokens first
- A new curve becomes a named token, not a magic value in JSX or CSS
- Preview the curve against a duration the app actually uses (150ms, 200ms, 300ms — whatever the scale already has)
- Do not add a second motion library to “get better easings”
Paste the current token list into the prompt when the agent is adding animation. Ask it to cite the token it reused, the same way you ask it to cite a design-system component.
Preview the curve, then store the value
You want a local preview: drag the control points, watch a sample motion, copy the cubic-bezier() string. No account, and no reason to invent the numbers from memory.
When you are already in the browser, an in-tab bezier editor is enough. Uwarp’s cubic-bezier tool previews the curve and copies the CSS value, so you can compare it with the standard token before you touch the scale. Handy for one new motion token. If the team already has a motion playground in Storybook or in the design-token docs, use that as the source of truth.
Caveats: a curve that looks lively at 600ms can feel snappy or late at 150ms. Preview at the duration you will ship. And do not drop the copied value into a styled button if a token already matches it within a rounding error — point the component at the token instead.
If the agent already wrote a magic bezier, the review question is not “is this a pretty curve?” It is “which existing token is this supposed to be, and if none, where is the new token name?”
Reject / send back
Reject
- A one-off
cubic-bezier(...)in a component when a motion token already exists - A new easing library added for a single transition
- A token change with no preview and no duration
- An animation that still has no reduced-motion path
Accept
- A component that reuses
--motion-ease-standardor the existing named token - A new named motion token, previewed, and used by the new animation
- A documented decision that the existing curve is close enough, with no magic value