Return-to-Origin Navigation
Send people back to the exact list they came from, filters and all.
What it adds
A shared mechanism for remembering where a workflow started and returning the user there when it finishes.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Scope the origin to the workflow that set it and clear it on completion, so a stale value cannot hijack an unrelated flow later.
-
5
Do NOT trust the Referer header or an unvalidated redirect parameter. Both are attacker-controlled and turn this into an open redirect.
Edge cases it handles
6
Edge cases it handles
6- An origin pointing at a deleted or now-forbidden record must fall back to a sane default, not a 404.
- An external or protocol-relative URL must be rejected outright.
- Cancelling must return to the origin too, not just saving.
- Multi-step flows must survive a refresh mid-way without losing the origin.
- Restore scroll position only when the list still contains the item; otherwise return to the top.
- Do not append the origin to URLs the user might share — a bookmark should not carry someone else's return state.
Definition of done
7
Definition of done
7- Finishing or cancelling a nested task returns to the originating list with filters, sort, and page intact.
- Return targets are validated as internal and permitted before use.
- An invalid or expired origin falls back to a documented default destination.
- Origin state does not leak into unrelated workflows.
- The mechanism is used consistently across the app rather than reimplemented per screen.
- 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.