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
Z-Index Registry
Z-Index Registry
Keep every stacking value in one file so nobody has to guess a bigger number.
What it does
A single source of named z-index tokens, with reserved ranges per layer and a check that blocks raw values.
How it works
- 1 Find every z-index in the codebase, including inline styles and values buried in third-party overrides, and list them with the component that owns each. The count is usually higher than anyone expects and several will be arbitrary large numbers.
- 2 Reserve a range for each layer rather than assigning single values, so a new dropdown can slot between existing ones without renumbering everything above it. Leave real gaps between ranges.
- 3 Name each token after the layer it belongs to and derive the ordering from Elevation Layer Map. That feature decides what covers what; this one holds the numbers and stops them being invented locally.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/z-index-registry
Shadow Scale
Shadow Scale
Replace ad hoc shadows with a small set tied to what each surface actually is.
What it does
A fixed ladder of shadow tokens, each named for an elevation role rather than a blur radius.
How it works
- 1 Collect every shadow currently declared anywhere in the app and group them by what they sit on — a resting card, a hovered card, a dropdown, a dialog, a toast. Most apps have a dozen near-identical values that collapse into four or five roles.
- 2 Name each step for its role, not its appearance. A token called menu tells the next person which surfaces may use it; a token called shadow-md-2 does not.
- 3 Use a single light source for the whole scale, so offset, blur, and spread grow together as elevation rises. Two shadows lit from different directions on the same screen read as a rendering bug.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/shadow-scale
Radius Scale
Radius Scale
Fix the app's corner radii to a few steps that agree with one another.
What it does
A small radius scale mapped to component roles — controls, cards, overlays, pills, media — and applied throughout.
How it works
- 1 Collect every corner radius in the codebase and reduce it to three or four steps, then assign each step a role: controls and inputs, cards and panels, overlays and sheets, fully rounded pills.
- 2 Set nested radii so the inner corner is smaller than the outer one by roughly the padding between them. An inner element with the same radius as its container leaves a visible sliver of gap at each corner.
- 3 Scale the radius with the component: the step that reads as softly rounded on a small button reads as barely rounded on a large panel, and as a lozenge on a short chip.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/radius-scale
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.