Motion Token System
Give the app one shared vocabulary of durations and easing curves instead of ad hoc numbers.
What it adds
A named set of durations and easing curves, each tied to a category of motion, replacing the timing values scattered through the app's components.
What your agent is told to do
5
What your agent is told to do
5-
1
Inventory every duration and easing value currently written into the app and group them by what they do: something entering, something leaving, something being emphasised, and something changing size or position.
-
2
Name a small set of durations — roughly instant, quick, standard, and deliberate — and a small set of curves, then map each motion category to a pairing. Four or five of each is enough for an entire product.
-
3
Give entrances and exits different treatment. Something arriving should decelerate into place; something leaving should accelerate away and take less time, because nobody wants to wait for a dismissal.
-
4
Define a reduced-motion value for every token rather than a single global switch that sets everything to zero. Some motion should shorten, some should become a cross-fade, and some should vanish entirely.
-
5
Do not use a single easing curve for everything. A curve that suits a panel sliding in makes a hover state feel sluggish, and the same curve on a layout change reads as the interface hesitating.
Edge cases it handles
7
Edge cases it handles
7- Every token needs a defined behaviour when the user has asked for reduced motion, and the answer is not always zero — a shortened fade often communicates better than an instant jump.
- One curve applied to every kind of motion is the failure this feature exists to prevent; entrances, exits, emphasis, and layout changes each need their own pairing.
- Motion attached to something a user does many times an hour — a menu opening, a row expanding — must sit at the short end of the scale, because a duration that feels elegant once feels like lag on the fiftieth repetition.
- Interrupting a transition partway through must resolve from the current position rather than snapping to the start, or rapid clicking produces visible jumps.
- This entry owns the values only. Which properties are allowed to animate and where motion is omitted belongs to Transition Consistency, and the mounting and unmounting lifecycle belongs to Enter and Exit Animation Pattern.
- Durations must survive being read from a stylesheet by scripted animation too, so the two do not drift apart.
- Tokens need to be inspectable at runtime, or nobody will be able to tell which one a given element is using when it looks wrong.
Definition of done
8
Definition of done
8- Durations and easing curves are defined once as named tokens and referenced everywhere.
- No component in the app carries a hardcoded duration or curve.
- Entrances, exits, emphasis, and layout changes each map to a distinct pairing.
- Every token has a defined reduced-motion counterpart.
- Frequently repeated interactions use the shortest durations in the scale.
- Scripted animation and stylesheet animation read the same token values.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Semantic Color Tokens
Semantic Color Tokens
Name colours by the job they do, so changing a theme is one edit rather than a sweep.
What it does
A vocabulary of role-named colour tokens — surface, text, border, accent, danger, success — that components reference instead of literal values.
How it works
- 1 Inventory every literal colour value in the codebase and group them by the job they are doing rather than by the shade they happen to be. Two different greys used as card backgrounds are one role; the same grey used as a background and as a border is two.
- 2 Define the role names once and map each role to a value per theme. A role may resolve to a light grey in one theme and a near-black in another; what must not change is which components reference it.
- 3 Stop shared components accepting raw colour values. A primitive that takes a hex string as a prop guarantees that some product screen will hardcode a colour the themes never learn about.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/semantic-color-tokens
Container Width System
Container Width System
Give pages a few defined widths instead of a different max-width on every screen.
What it does
A small set of named page widths — narrow, standard, wide, and full-bleed — applied consistently across the app.
How it works
- 1 Measure the max-width used on every top-level page and group them. Settings forms, prose, dashboards, and data tables usually want three or four distinct widths between them, not the eleven the codebase currently has.
- 2 Pick each width from the content it holds. A reading column is bounded by comfortable line length, a settings form by field width, and a table by the number of columns that must stay visible.
- 3 Make horizontal page padding part of the container rather than something each page adds, so content never touches the viewport edge on a narrow screen even at the widest setting.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/container-width-system
Border System
Border System
Give borders defined jobs so structure, focus, and selection never look the same.
What it does
A set of border tokens covering structural dividers, interactive outlines, focus rings, selection, and error emphasis.
How it works
- 1 Audit every border in the app and sort it into one of a few jobs: separating content, outlining a control, marking focus, marking selection, or signalling an error. Anything that does not fit a job is decoration that should be removed rather than tokenised.
- 2 Keep structural borders and interactive borders visually distinct. A divider between table rows and the outline of a text input should not share a colour, or users will read inert content as clickable.
- 3 Define focus separately from selection and from hover. Focus follows the keyboard, selection follows intent, and a control that is both focused and selected must show both without one hiding the other.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/border-system
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.