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
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.