Collapsible Sections
Let users fold away the parts of a crowded page they do not need right now.
What it adds
Sections with a heading that expands and collapses, so a long page can be reduced to the parts in use.
What your agent is told to do
5
What your agent is told to do
5-
1
Find the pages carrying several distinct groups of content and give each group a real heading plus a disclosure control.
-
2
Make the whole heading row the trigger, using a native button with the correct expanded state exposed, and render the collapsed content in a way that is genuinely removed from tab order and screen reader flow.
-
3
Choose sensible defaults per section rather than collapsing everything — a page that opens fully collapsed is a page with no content.
-
4
When a validation error, a search match, or a deep link targets content inside a collapsed section, expand that section and scroll to the target.
-
5
Do not collapse required actions, blocking warnings, or anything the user must act on. Hiding a problem behind a chevron does not solve it.
Edge cases it handles
6
Edge cases it handles
6- Persisted expansion state must be discarded when the section no longer exists or the user's permissions have changed.
- Browser find-in-page cannot search collapsed content — accept this and make section headings descriptive enough to find.
- Collapsing a section containing focus must move focus to the section heading, not lose it.
- The animation must respect prefers-reduced-motion, and must not be applied to sections restored as collapsed on first paint.
- A section whose content is empty should say so rather than expanding into nothing.
- Sections that are expanded on load must not shift layout after data arrives — reserve space or keep them collapsed until loaded.
Definition of done
8
Definition of done
8- Every section has an accessible trigger reporting its expanded state.
- Collapsed content is out of tab order and hidden from assistive technology.
- Validation errors, deep links, and search hits auto-expand their section.
- Warnings and required actions are never collapsible.
- Focus is handled deliberately when a section closes.
- Animation respects prefers-reduced-motion and does not run on initial paint.
- 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.