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
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
Responsive Grid Tokens
Responsive Grid Tokens
Express columns, gaps, and spans as shared tokens rather than per-component guesses.
What it does
A token set describing column counts, gutters, and span behaviour at each breakpoint, used by every grid in the app.
How it works
- 1 Find the grids already in the app — card lists, dashboards, form layouts, media galleries — and record how many columns each uses at each size. The reconciled set is normally three or four column counts, not one per screen.
- 2 Define gutters from the spacing scale rather than inventing grid-specific values, so the gap between cards matches the rhythm of everything around them.
- 3 Express spans in tokens tied to the column count, so a component asking for half a row keeps working when the row drops from four columns to two instead of overflowing.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/responsive-grid-tokens
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.