Card and List View Toggle
Let users switch between a visual card view and a compact list without losing context.
What it adds
Two renderings of the same result set, sharing one query, one selection, and one set of controls.
What your agent is told to do
5
What your agent is told to do
5-
1
Drive both views from a single query and a single result set. The toggle is a rendering choice, not a second data path.
-
2
Keep search, filters, sort, selection, and pagination identical across views. Switching must not clear a filter or reset the page.
-
3
Give every row action a card equivalent and every card action a row equivalent. If an action exists in only one view, users will not find it.
-
4
Switch without refetching data you already have, and without a flash of empty state on the way.
-
5
Persisting the chosen view is owned by Persistent View Preferences; use it rather than adding another storage mechanism.
Edge cases it handles
6
Edge cases it handles
6- Page size that suits a list is usually wrong for cards — if it differs, changing view must keep the user looking at the same records, not the same page number.
- Selection must survive the switch, including selections scrolled out of view.
- The empty, loading, and error states need a treatment in both views, not just the default one.
- Both views must enforce the same permissions — a card must not reveal a field the list hides.
- Cards without an image need a defined placeholder, or the grid collapses into ragged rows.
- The toggle itself must be keyboard-operable and announce the current view, not just show a highlighted icon.
Definition of done
8
Definition of done
8- Switching views issues no additional data request and shows no flicker.
- Search, filters, sort, selection, and position in the result set are preserved.
- Every action is available in both views.
- Empty, loading, and error states exist for both renderings.
- The two views expose exactly the same fields under the same permissions.
- The chosen view is persisted through Persistent View Preferences.
- 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.