Text Wrapping Rules
Decide how text breaks, truncates, and hyphenates so nothing overflows or loses meaning.
What it adds
A per-content-type set of wrapping, breaking, and truncation rules applied across the app's components.
What your agent is told to do
5
What your agent is told to do
5-
1
Classify the text the app renders into a few kinds — prose, identifiers, machine strings, user-supplied names, numbers — and define one wrapping rule for each kind rather than patching overflow component by component.
-
2
Give long unbroken strings such as URLs, API keys, record IDs, file paths, and email addresses a break rule that lets them wrap at sensible boundaries instead of pushing their container wider than the viewport.
-
3
Decide per surface whether text truncates or wraps, and make truncation reversible: anything cut off must be recoverable in full through a tooltip, a details view, or an expand control.
-
4
Do not fix overflow by hiding it. Setting a container to clip its contents removes the symptom and leaves the user with a name, an error, or a total that silently ends mid-word.
-
5
Text Measure Guardrails owns how wide a line of prose may be; this entry owns what happens when a string does not fit the width it has been given. Keep the two separate so a change to one does not require a change to the other.
Edge cases it handles
7
Edge cases it handles
7- URLs, identifiers, hashes, and code fragments must never be hyphenated or broken at an arbitrary character, because a broken key is one the user cannot copy or verify. Break them at punctuation boundaries or let them scroll within their own container.
- Hyphenation and word-breaking rules differ by writing system, and languages that do not use spaces between words break on entirely different boundaries. Drive the rule from the content's language rather than the interface language.
- A button whose label wraps to two lines must still look like a button: the height grows, the icon stays aligned with the first line, and the hit area covers both lines. A label that wraps to a single character on the second line needs a shorter label, not a narrower rule.
- When truncation hides meaning — a document title, an error message, a customer name that differs only in its last word — the full value must be reachable without navigating away. Truncation is a display convenience, never a data decision.
- Middle truncation suits filenames and paths, where the end carries the extension and the distinguishing folder; end truncation suits sentences. Choose per content type rather than applying one everywhere.
- Screen readers must receive the complete string, not the visually truncated one, so an ellipsis is never read as the end of a name.
- Multi-line clamping must survive a font change or a resize. A clamp measured once at load will show three and a half lines after the layout reflows.
Definition of done
9
Definition of done
9- Every kind of text in the app has a defined wrapping rule, applied through shared styles rather than per-component patches.
- No long identifier, URL, or path forces its container wider than the viewport.
- Truncated values are recoverable in full through a tooltip, expansion, or detail view.
- Hyphenation and breaking follow the language of the content rather than the interface.
- Wrapped button and control labels stay legible and keep their full hit area.
- Screen readers announce the complete string for every truncated element.
- No container hides overflow without an alternative route to the hidden content.
- 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.