Display Density
Let users pick comfortable or compact spacing without breaking the layout.
What it adds
A density setting that tightens row height, padding, and font size across the app's data surfaces.
What your agent is told to do
5
What your agent is told to do
5-
1
Express spacing as tokens first. If padding is hardcoded across components, extract it before adding the setting.
-
2
Offer two or three levels, no more. Comfortable and compact cover almost everyone.
-
3
Apply density consistently to tables, lists, menus, cards, and form rows. A compact table beside a comfortable form looks broken.
-
4
Apply the stored choice before first paint so rows do not resize under the cursor.
-
5
Do not shrink touch targets below the accessible minimum in compact mode. Reduce padding and line height, not hit area.
Edge cases it handles
6
Edge cases it handles
6- Compact mode must not clip descenders or truncate text that fitted before.
- Icons and avatars need their own scale steps; leaving them at full size defeats the compaction.
- Touch devices should default to comfortable regardless of the desktop preference.
- In a multi-tenant app, decide whether density follows the user or the workspace, and say which.
- Row heights used by virtualized lists must be recalculated when density changes, or scrolling will misplace items.
- Density must not change the number of columns or hide content, only the spacing around it.
Definition of done
7
Definition of done
7- Density applies uniformly across tables, lists, menus, cards, and forms.
- The choice persists and is applied before the page renders.
- Touch targets stay at least 44x44px in every mode.
- No text is clipped or truncated in compact mode.
- Virtualized lists measure correctly after a density change.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
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
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
Expandable Text
Expandable Text
Shorten long text without making the full content hard to reach.
What it does
Long text clamped to a few lines, with an explicit control to show the rest and collapse it again.
How it works
- 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.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/expandable-text
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.