Spacing Scale
Reduce the app's spacing to a small set of steps that repeat across every surface.
What it adds
A named spacing scale covering gaps, padding, and section rhythm, with every existing value in the app mapped onto it.
What your agent is told to do
5
What your agent is told to do
5-
1
Collect every spacing value currently in the codebase and count how often each appears. The result is usually a handful of genuine intentions surrounded by dozens of near-misses that were nudged once and never revisited.
-
2
Define a scale that is fine at the small end, where control padding lives, and coarse at the large end, where section separation lives. A linear scale gives too many indistinguishable large steps and too few small ones.
-
3
Separate the tokens used inside a component from the ones used between components and between page sections, and name them so the difference is obvious. The same number serving both purposes means a change to button padding also changes the gap between sections.
-
4
Migrate one component family at a time and remove the old values as you go. Do not add the scale alongside the existing spacing and leave both in use — a half-migrated system is less consistent than the one it replaced, because now there are two right answers.
-
5
Display Density owns switching the whole app between comfortable and compact; this entry owns the steps themselves. Express the scale so a density mode can rescale it, and leave the mode switching to that feature.
Edge cases it handles
7
Edge cases it handles
7- Spacing inside a component and spacing between components change for different reasons and at different rates. Keep them in separate token groups, or tightening a card's padding will also close up the gap between cards.
- A density mode has to rescale the whole scale coherently. Values that are hardcoded, or expressed in units the mode cannot touch, will stay at their comfortable size while everything around them tightens.
- Optical alignment sometimes demands a value that is not on the scale — an icon that needs a half step to sit on the text baseline, a badge that needs to overlap its anchor. Allow those, name them, and record why, rather than pretending the scale covers every case.
- Values that sit close to a token but not on it are the ones that erode the system. Flag them during review so a stray value has to be justified rather than merged unnoticed.
- Adjacent margins can collapse into one another, so a value that looks correct in isolation produces a smaller gap in place. Prefer a single owner of each gap over margins on both sides.
- The scale must hold across breakpoints. A section gap that is right on a wide screen is usually too large on a phone, so define which steps change responsively and which are fixed.
- Do not renumber or reorder the scale after adoption. Every existing usage silently shifts, and the change is invisible in review.
Definition of done
9
Definition of done
9- A single spacing scale is defined, with steps that are fine at the small end and coarse at the large end.
- Internal component spacing and layout spacing are separate named groups.
- Every migrated component uses scale tokens, with no leftover hardcoded values alongside them.
- The scale can be rescaled as a whole for a density mode.
- Off-scale values exist only as documented optical exceptions with a recorded reason.
- Near-token values are flagged during review rather than merged unnoticed.
- Which steps change at each breakpoint is defined and applied consistently.
- 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
Motion Token System
Motion Token System
Give the app one shared vocabulary of durations and easing curves instead of ad hoc numbers.
What it does
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.
How it works
- 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.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/motion-token-system
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
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.