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
Opening Hours Display
Opening Hours Display
Say whether you are open right now and when you next open.
What it does
A live open or closed state alongside the weekly hours, with holiday closures folded in.
How it works
- 1 Lead with the current state in plain words and follow it with the next transition: open until a time, or closed until a day and time. The weekly table is supporting detail, not the headline.
- 2 Store hours as intervals against the business's own zone, and keep holiday and one-off closures as overrides that win over the regular week rather than as edits to it.
- 3 Compute the state on the server for the first render so the page does not briefly claim the wrong thing, then let the page update itself as the clock crosses a boundary without a reload.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/opening-hours-display
Dark Mode
Dark Mode
Add a dark theme that respects the system preference and the user's choice.
What it does
A complete dark theme, defaulting to the operating system preference and overridable by the user.
How it works
- 1 Audit every colour in the app first and report where they are defined. If colours are hardcoded throughout, extract them into tokens before anything else — that refactor is the bulk of this work.
- 2 Define a dark palette against those tokens. Do not simply invert the light theme.
- 3 Default to the system preference via prefers-color-scheme, and let the user override it.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/dark-mode
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.