Typography Scale
Replace ad-hoc font sizes with a small set of named type steps.
What it adds
A fixed set of type steps, each pairing a size with its weight, line height, and letter spacing.
What your agent is told to do
5
What your agent is told to do
5-
1
Collect every distinct font size, weight, and line height currently used in the app and reduce them to a small set of steps. A codebase with nineteen sizes almost always has six real ones and thirteen accidents.
-
2
Bind line height and letter spacing to each step rather than leaving them to be set per component, because the same size at two different line heights reads as two different styles.
-
3
Keep adjacent steps far enough apart to be told apart at a glance. Steps a single pixel apart give authors a decision they cannot make correctly and produce inconsistency by themselves.
-
4
Separate the semantic element from the visual step: a heading level is about document structure, and the step it renders at is a layout decision. A section heading that needs to look small must not become a lower heading level to get there.
-
5
How each step behaves between viewport sizes is owned by Fluid Typography; this feature owns which steps exist and what belongs to each. Define the steps first, then let the fluid rules interpolate them.
Edge cases it handles
7
Edge cases it handles
7- Steps that sit too close together are indistinguishable in use, so authors pick arbitrarily and the scale stops meaning anything.
- Translated copy runs longer than the English it replaced, so every step must be checked with long German compounds and with scripts that need more vertical space than Latin.
- Heading levels convey structure and must not be chosen for their size; the scale has to make it possible to render an h3 at a small step without demoting it to h5.
- Line height and weight that read well on a light background can look thin or heavy inverted, so each step needs checking in every theme rather than only the default one.
- Scripts with tall ascenders and deep descenders, and text with diacritics, will clip in any step whose line height was tuned to lowercase Latin.
- User-generated content arrives with its own markup and must be mapped onto the scale, or a pasted document introduces sizes that exist nowhere in the system.
- The scale must survive the browser's own text-size setting and page zoom, which rules out expressing steps in units that ignore the user's preference.
Definition of done
9
Definition of done
9- The app renders text from a fixed set of named steps with no ad-hoc font sizes remaining in components.
- Each step defines its size, weight, line height, and letter spacing together.
- Adjacent steps are visually distinguishable side by side.
- Heading level and visual step are chosen independently of one another.
- Every step is legible in each theme and does not clip diacritics or descenders.
- The scale responds to browser text-size settings and zoom.
- Viewport interpolation is delegated to Fluid Typography rather than duplicated here.
- 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
Spacing Scale
Spacing Scale
Reduce the app's spacing to a small set of steps that repeat across every surface.
What it does
A named spacing scale covering gaps, padding, and section rhythm, with every existing value in the app mapped onto it.
How it works
- 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.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/spacing-scale
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
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.