Page Table of Contents
Turn a long page into a scannable set of anchored sections.
What it adds
A generated list of a page's headings, with anchor links and an indicator for the section currently in view.
What your agent is told to do
5
What your agent is told to do
5-
1
Generate the table from the headings actually rendered on the page. Do not maintain a hand-written list beside the content — it will drift.
-
2
Derive stable anchor ids from heading text, and disambiguate repeated headings deterministically so a shared link keeps pointing at the same section.
-
3
Offset every jump by the height of any sticky header, so the target heading is not hidden underneath it.
-
4
Track the section in view and mark it, but debounce the switch — a highlight that flickers between two entries at a boundary is worse than none.
-
5
Do not render the table for pages with fewer than about three sections; it adds noise and no navigation value.
Edge cases it handles
6
Edge cases it handles
6- Headings inside collapsed sections must expand their section when linked to, not scroll to nothing.
- A deep-linked anchor on first load must land correctly even though layout shifts as images and fonts settle.
- Very long heading text must truncate in the table while keeping the full text as its accessible name.
- On mobile there is no room for a sidebar — collapse the table to a control at the top rather than dropping it.
- Content that loads after first paint must update the table, not leave it stale.
- Keyboard users must be able to tab into the table and land focus on the target heading after activating a link, not just scroll the page.
Definition of done
8
Definition of done
8- Every rendered heading appears in the table, and nothing else does.
- Anchor ids are stable across reloads and unique when headings repeat.
- Jumps clear any sticky header.
- The active-section indicator does not flicker at boundaries.
- The table is usable on mobile and by keyboard, and moves focus to the target.
- Short pages render no table at all.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
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
Pagination
Pagination
Split long lists into numbered pages without losing filters or the user's place.
What it does
Discrete paged lists with an explicit page control, where page number, page size, filters, and sort all live in the URL.
How it works
- 1 Build a real page control: previous, next, and a way to jump to a specific page or the last page. This feature is for lists people navigate deliberately. If the list is a feed people graze, choose progressive appending instead.
- 2 Put page, page size, filters, and sort in the URL so every page is linkable, bookmarkable, and survives a refresh.
- 3 Show enough context to orient: current page, total pages or a clear next-page affordance, and the range of items shown out of the total.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/pagination
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
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.