Previous and Next Record Navigation
Move through a result set one record at a time without going back to the list.
What it adds
Previous and next controls on a detail view that walk the same sequence the user's list produced.
What your agent is told to do
6
What your agent is told to do
6-
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.
-
4
Prompt before leaving a record with unsaved changes, and keep the user on the record if they cancel.
-
5
Capturing where the user came from and returning them there is owned by Return-to-Origin Navigation; extend that rather than building a second one. This feature only walks the sequence.
-
6
Bind keyboard access (conventionally J/K or the arrow keys with a modifier) and do not swallow those keys while a text field is focused.
Edge cases it handles
6
Edge cases it handles
6- The current record can be deleted while it is open — move to the neighbour and say what happened, do not dead-end.
- Records inserted or edited by other users can shift the sequence; decide whether the sequence is a snapshot or live, and be consistent about it.
- A record that no longer matches the active filter after an edit must still be navigable away from.
- Crossing a pagination boundary must load the next page transparently rather than stopping at position 25.
- A user arriving by direct link has no sequence — hide the controls rather than inventing one.
- A record the user may see in a list but not open must be skipped or shown as denied, never a blank page.
Definition of done
8
Definition of done
8- The traversal order matches the list's active filter and sort exactly.
- The sequence survives refresh and is encoded in the URL.
- Boundaries disable the controls without an extra request.
- Deleted or filtered-out records do not strand the user.
- Pagination boundaries are crossed transparently.
- Unsaved changes are protected before navigating away.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Workspace Switcher
Workspace Switcher
Move between organizations without mixing their data.
What it does
A switcher for users who belong to several workspaces, with clean state isolation on every switch.
How it works
- 1 Show the current workspace at all times, prominently enough that nobody edits the wrong account's data by accident.
- 2 Resolve the active workspace on the server from the session or the URL. Never trust a client-held value to scope a query.
- 3 On switch, clear every piece of cached state tied to the previous workspace: query caches, filters, drafts, selections, realtime subscriptions.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/workspace-switcher
Tabs
Tabs
Split a crowded page into sections without another route.
What it does
Accessible tabbed sections, with the active tab reflected in the URL.
How it works
- 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.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/tabs
Shareable Deep Links
Shareable Deep Links
Let people copy a URL that reopens exactly what they were looking at.
What it does
Encode the current record, tab, filter set, and selection in the URL so a copied link restores the same view for whoever opens it.
How it works
- 1 Audit the app for view state that currently lives only in memory: active tab, applied filters, sort order, expanded rows, selected items, scroll target.
- 2 Move that state into the URL and make the app read it back on load, so a pasted link reconstructs the view rather than dumping the user on a default screen.
- 3 Add a visible copy-link affordance on every view that supports it, and confirm the copy so the user knows it worked.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/shareable-deep-links
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.