Beautiful Empty States
Replace blank screens with useful, contextual empty states.
What it adds
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.
What your agent is told to do
4
What your agent is told to do
4-
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,
-
4
Use the app's existing icon set. Do not add a new icon library.
Edge cases it handles
4
Edge cases it handles
4- Loading is not empty. Do not flash the empty state while data is still
- Error is not empty. A failed request is an error state.
- The user cannot create. Do not show a "Create" action they lack permission for.
- Pagination. Page 3 of a 2-page list is a filtered empty, not a first-run empty.
Definition of done
7
Definition of done
7- Every collection view in the app has an empty state.
- First-run, filtered, and cleared empties are worded differently.
- The empty state never appears during loading or on error.
- One reusable component, built from the existing design system.
- Actions are wired to the app's real handlers.
- It reads correctly at a 320px viewport.
- Screen readers announce the state.
Related features
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
Toast Notifications
Toast Notifications
Give every action a clear, non-blocking confirmation.
What it does
A small, temporary message confirming that something worked — or explaining that it did not.
How it works
- 1 Add a single global toast region and a way to trigger it from anywhere.
- 2 Find every mutating action in the app (create, update, delete, upload) and give it a toast on success and on failure.
- 3 Wire it into the app's existing flash/notification mechanism if one exists, rather than building a parallel system.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/toast-notifications
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.