Text Measure Guardrails
Hold long-form text to a readable line length instead of letting it run the full width.
What it adds
A maximum measure applied to the app's prose containers, with named exceptions for content that needs the whole width.
What your agent is told to do
5
What your agent is told to do
5-
1
Find every surface that renders more than a couple of sentences — help articles, changelog entries, terms pages, long empty-state explanations, in-app announcements — and cap the measure on the text container itself rather than on the page shell.
-
2
Express the cap in units that scale with the type, so a larger heading or a user who has raised their base font size gets a proportionally wider column instead of a cramped four-word line.
-
3
Declare which elements are allowed to break out of the measured column — tables, code blocks, images, video, diagrams, full-bleed callouts — and let them span the container while the paragraphs around them stay narrow.
-
4
Do not centre long-form copy to make the narrow column look deliberate. A ragged left edge makes the eye hunt for the start of every line, which is the cost the measure was meant to remove.
-
5
Keep this entry to width only. Text Wrapping Rules owns what happens inside a line — where it breaks, when it truncates, how it hyphenates — so the two briefs do not both try to define overflow behaviour.
Edge cases it handles
7
Edge cases it handles
7- Tables, code samples, and media that are forced into the prose measure become unreadable or scroll horizontally. Let them break out to the container width while the surrounding paragraphs stay capped.
- A measure tuned for body text is too narrow for large display type and too wide for small print. Adjust the cap per step of the type scale rather than applying one number to everything.
- Centred long-form paragraphs cost the reader a fixation on every line return. Reserve centring for single lines such as a page title or an empty-state message.
- The cap must be a maximum, not a fixed width. On a narrow viewport the column has to shrink and keep its gutters, or the text runs into the screen edge.
- Nested containers that each apply the cap compound it and produce a column half the intended width. Apply the measure once, at the outermost prose wrapper.
- In right-to-left locales the column must align to the right edge, not stay pinned left.
- A user who zooms the browser or enlarges their default font must get fewer characters per line, not a horizontally scrolling page.
Definition of done
8
Definition of done
8- Every long-form surface renders its paragraphs within a bounded measure rather than the full page width.
- The measure scales with the type size instead of being a single fixed value across the app.
- Tables, code blocks, and media render at the container width while adjacent paragraphs stay measured.
- No long-form body copy is centred.
- On narrow viewports the column shrinks and retains its gutters, with no horizontal scrolling.
- Nesting two prose containers does not halve the column width.
- 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.