Infinite Scroll with Load More
Load a long feed progressively without trapping people in an endless page.
What it adds
One growing list that appends the next batch as the user nears the end, driven by a sentinel and a visible load-more button.
What your agent is told to do
7
What your agent is told to do
7-
1
Append to a single accumulating list rather than replacing it. This is for feeds people graze. Lists people navigate deliberately, or need to link to a specific position in, want numbered pages instead.
-
2
Place a sentinel element after the last item and load the next batch when it comes into view, with a generous margin so the content arrives before the user reaches it. Always render a visible load-more button alongside it.
-
3
Move focus to the first newly appended item when the user loads more by button, so keyboard users are not thrown back to the top of the list.
-
4
Track loaded batches so the same record is never appended twice, and dedupe by ID on append rather than trusting batch boundaries.
-
5
Cancel in-flight requests when the filter, sort, or search term changes, and clear the accumulated list before loading the new one.
-
6
Show a clear end-of-results state. A feed that simply stops loading is indistinguishable from one that is broken.
-
7
Do NOT make the page footer unreachable. If there are links or legal text below the list, either move them or keep the feed inside its own scrolling region.
Edge cases it handles
8
Edge cases it handles
8- Navigating to a detail view and back must restore both the loaded range and the scroll position, or the user loses everything they scrolled past.
- A failed page load needs a visible retry in place, not a silent stop that looks like the end of the list.
- Keyboard and screen reader users need the load-more button as the primary path. An observer that only fires on scroll never fires for them.
- Announce the count of newly appended items politely. Do not read the whole batch out, and do not leave the append silent.
- The sentinel must not sit inside a container it can never intersect, and must be disconnected once results are exhausted or it will fire forever.
- Very long sessions accumulate DOM nodes until the page stutters. Virtualize, or cap the list and offer a jump back to the top.
- Items deleted from earlier pages while the user scrolls must not leave gaps or cause the next page to skip records.
- Restoring position must wait until the restored items have rendered, or the browser will scroll to the wrong place.
Definition of done
10
Definition of done
10- A manual load-more control is always present and works without scrolling.
- Loading more appends to the existing list and moves focus to the first new item when triggered by the button.
- No record appears twice, including when data changes between requests.
- Changing filters or search cancels in-flight requests and resets the list.
- The end of results is explicitly stated.
- Back navigation restores the loaded range and scroll position.
- Failed page loads show an inline retry.
- Footer content remains reachable.
- 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.