Expandable Text
Shorten long text without making the full content hard to reach.
What it adds
Long text clamped to a few lines, with an explicit control to show the rest and collapse it again.
What your agent is told to do
5
What your agent is told to do
5-
1
Clamp by rendered lines, not by character count. Cutting a string at a fixed length breaks words, mangles markup, and truncates differently at every width.
-
2
Only show the expand control when the text is genuinely clipped. A 'Show more' on a two-line paragraph is noise.
-
3
Use a real button with an accessible label naming what expands, and expose the expanded state. An untagged 'more...' is invisible to a screen reader.
-
4
Keep the full text in the document and hide the overflow visually, so find-in-page, copy, and assistive technology see all of it.
-
5
Do not truncate anything the user must read to make a decision — error messages, warnings, legal terms, or the only description a record has.
Edge cases it handles
6
Edge cases it handles
6- Re-measure after font load, container resize, and content change; a clamp decided once at mount will be wrong later.
- A link or interactive element in the clipped region must not be focusable while collapsed.
- Collapsing must not jump the page — keep the top of the block in view rather than the bottom.
- Rich text with lists, headings, or code blocks does not clamp cleanly; decide whether it collapses to a fixed height instead.
- Right-to-left and vertical text need the fade or ellipsis on the correct edge.
- Text with no spaces, such as a long URL or token, must wrap or truncate rather than forcing horizontal scroll.
Definition of done
8
Definition of done
8- Truncation happens by rendered space and never breaks words or markup.
- The control appears only when content actually overflows.
- The trigger is a labelled button reporting its expanded state.
- Full text remains findable by browser search and copyable.
- Clamping is re-evaluated on resize and font load.
- Collapsing does not move the block out of view.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Countdown Timer
Countdown Timer
A live countdown to a deadline that ends cleanly instead of running negative.
What it does
A countdown component driven by a server-provided deadline, with a defined finished state.
How it works
- 1 Send the deadline and the server's current time together, compute the offset between server and device once, and count against the corrected value. The device clock cannot be trusted to be right.
- 2 Recompute the remaining time from the corrected clock on every tick rather than decrementing a stored number, so a suspended tab does not resume showing a value minutes behind reality.
- 3 Define the finished state explicitly: what the component shows at zero, whether it reveals something, disables a control, or triggers a refetch. Reuse the app's existing Progress Indicator System styling rather than introducing new type and colour for the digits.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/countdown-timer
Beautiful Empty States
Beautiful Empty States
Replace blank screens with useful, contextual empty states.
What it does
Every list, table, and dashboard in your app has a "nothing here yet" state. Most
apps ship a blank rectangle — and it is often the very first thing a new user sees.
An empty state should say what belongs here, why it is empty, and what to do next.
How it works
- 1 Inventory the empty cases first. List every collection view in the app and
- 2 Distinguish the three kinds of empty. They are not the same, and must not
- 3 Build one reusable empty-state component from the existing design system,
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/beautiful-empty-states
Safe Area Insets
Safe Area Insets
Stop notches, home indicators, and browser chrome from swallowing the interface.
What it does
Insets applied at the viewport edges of edge-to-edge layouts, so fixed and full-bleed elements clear device hardware.
How it works
- 1 Identify every element that touches a viewport edge: fixed headers, bottom navigation, sticky action bars, drawers, toasts, and any full-bleed background. Those are the only places insets belong.
- 2 Add the inset to the element's existing padding rather than replacing it, so a bar keeps its designed internal spacing on devices with no notch at all and simply gains the extra clearance where it is needed.
- 3 Let the background extend to the physical edge while the content pulls inward. A bottom bar that stops short of the edge shows a strip of page behind it and reads as a rendering fault.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/safe-area-insets
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.