Tabs
Split a crowded page into sections without another route.
What it adds
Accessible tabbed sections, with the active tab reflected in the URL.
What your agent is told to do
4
What your agent is told to do
4-
1
Use tabs for alternative views of the SAME thing. If the content is unrelated, it wants a separate page.
-
2
Put the active tab in the URL so a tab can be linked, bookmarked, and survives a refresh.
-
3
Implement the WAI-ARIA tabs pattern: arrow keys move between tabs, Tab moves into the panel.
-
4
Lazy-load expensive panels, but don't refetch every time the user switches back.
Edge cases it handles
5
Edge cases it handles
5- A refresh or a shared link must open on the right tab.
- The browser back button should move between tabs if they change the URL.
- Too many tabs to fit must scroll or overflow into a menu, never wrap into a broken row.
- Unsaved changes in one tab must not be silently lost when switching.
- On mobile, tabs often work better as a select or a scrollable row.
Definition of done
7
Definition of done
7- The active tab is in the URL and survives refresh and sharing.
- The ARIA tabs pattern is implemented, with arrow-key navigation.
- Overflowing tabs degrade gracefully.
- Switching tabs doesn't silently discard unsaved input.
- Panels are lazy-loaded but not refetched needlessly.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Deep-Linkable Modals
Deep-Linkable Modals
Make dialogs and detail panels linkable without losing the page behind them.
What it does
Modals and detail panels that live at their own URL, so they can be shared, bookmarked, and closed with the back button.
How it works
- 1 Pick the overlays worth linking — record detail, edit forms, share dialogs — and give each one a real URL.
- 2 When that URL is opened directly, with no page underneath, render the content as a full page instead of an overlay floating on nothing.
- 3 Make the browser back button close the modal and leave the user on the page they were on, not two steps back.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/deep-linkable-modals
Previous and Next Record Navigation
Previous and Next Record Navigation
Move through a result set one record at a time without going back to the list.
What it does
Previous and next controls on a detail view that walk the same sequence the user's list produced.
How it works
- 1 Derive the sequence from the filter, sort, and search that were active on the originating list — not from the table's default ordering. A different order than the list the user came from is a bug, not a fallback.
- 2 Carry the sequence identity in the URL so the detail page is shareable and survives a refresh.
- 3 Disable the controls at genuine boundaries and make that state visible; do not fetch a page of results just to discover there is nothing after the last record.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/previous-and-next-record-navigation
Return-to-Origin Navigation
Return-to-Origin Navigation
Send people back to the exact list they came from, filters and all.
What it does
A shared mechanism for remembering where a workflow started and returning the user there when it finishes.
How it works
- 1 Add one reusable way to carry an origin through a workflow, and use it everywhere instead of hardcoded 'back to index' links.
- 2 Capture the full origin state — filters, page, sort, search query, and scroll position — not just the path.
- 3 Validate the return target before redirecting: it must be a path inside this app that the current user is allowed to see.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/return-to-origin-navigation
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.