Overscroll Control
Stop scrolling inside a panel from taking the whole page with it.
What it adds
Explicit scroll-chaining rules for nested scrollable surfaces such as dialogs, drawers, menus, and side panels.
What your agent is told to do
5
What your agent is told to do
5-
1
Identify the nested scrolling surfaces where continuing past the end currently drags the page behind them: dialogs, drawers, dropdown menus, chat panes, sidebars, and long tables. Where a surface is both sticky and scrollable, the offsets belong to Safe Sticky Positioning and only the chaining rules belong here.
-
2
Contain the scroll within those surfaces so reaching the end stops the gesture rather than handing it to the page. Contain it rather than forbidding it — the surface itself must still scroll normally throughout.
-
3
Apply the same rule to every input route. Wheel, trackpad momentum, touch drag, and keyboard paging all arrive at the boundary and all must behave identically when they do.
-
4
Preserve and restore the underlying page position whenever a full-screen surface opens and closes, so dismissing a dialog does not return the user to the top of a long list.
-
5
Do not lock scrolling globally by freezing the document while an overlay is open. That approach loses the scroll position, misbehaves on mobile as the address bar collapses, and can leave keyboard users unable to move within the overlay itself.
Edge cases it handles
7
Edge cases it handles
7- Containment must apply only where a surface genuinely scrolls. Applied indiscriminately it makes ordinary page scrolling stop dead wherever the pointer happens to be resting.
- Suppressing overscroll at the top of the document also disables pull-to-refresh and, on some platforms, back-swipe navigation, so scope the rule to the nested surfaces rather than to the document.
- Trackpad momentum keeps delivering events after the finger has lifted, so a boundary reached mid-flick will chain unless containment is expressed as a property of the scrolling surface rather than by cancelling individual events.
- A keyboard user paging through an overlay must still reach its end and then move focus out. Containment applies to scrolling, never to focus movement or to dismissing the surface.
- Bounce at the end of a list is meaningful feedback on some platforms, and removing it makes the surface feel broken. Suppress the chaining without suppressing the bounce.
- A surface that grows after opening — a menu whose list is filtered, a dialog that gains a validation summary — must recompute whether it scrolls at all.
- Zooming changes what overflows: a layout with no nested scrolling at default zoom often acquires it at two hundred percent, and the rules must hold there too.
Definition of done
8
Definition of done
8- Reaching the end of a nested scrolling surface does not scroll the page behind it.
- Nested surfaces continue to scroll normally within their own bounds.
- Wheel, trackpad momentum, touch, and keyboard paging all respect the same boundary.
- Pull-to-refresh and browser navigation gestures still work outside the contained surfaces.
- Opening and closing an overlay preserves the underlying page scroll position.
- Keyboard focus can always leave a contained surface.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Feedback Widget
Feedback Widget
Let anyone report a bug or send a comment from the page they are looking at.
What it does
An always-available launcher that opens a short feedback form and submits it with page context attached.
How it works
- 1 Put a single persistent launcher in one corner of the app and open a compact form in place. Do not route the user to a separate feedback page and lose the context they were about to describe.
- 2 Attach the current URL, the app version, the viewport size, the signed-in account, and a short trail of recent client errors automatically, so the reporter does not have to describe where they were.
- 3 Show the captured context to the user before they send it, in a collapsible section, and let them remove it. Silent collection of screen state is a trust problem.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/feedback-widget
Booking Page
Booking Page
A shareable page where someone picks an open time and confirms it in a few clicks.
What it does
A public scheduling page listing open slots, taking a booking, and confirming it to both sides.
How it works
- 1 Build the visitor path first: pick a date, see open times in their own zone, fill a short form, confirm, and receive an email with the details and a cancellation link. That is the minimum coherent version.
- 2 Derive open slots from the owner's availability rules and existing bookings on the server at request time. Do not trust a slot list the browser has been holding since page load.
- 3 Reuse the app's existing Time Zone-Aware Scheduling for conversion and storage, store every time as an absolute instant, and display it converted to the visitor's detected zone with the zone named on screen.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/booking-page
Date and Time Display Component
Date and Time Display Component
Render every date and time through one component so none of them are ambiguous.
What it does
A single shared way of displaying dates and times, covering absolute format, time zone, and optional relative phrasing.
How it works
- 1 Find every place the app renders a date or a time — tables, activity feeds, audit logs, exports, emails, tooltips — and route them all through one display path rather than formatting at each call site.
- 2 Never render an all-numeric date whose day and month could be swapped. Spell or abbreviate the month, or use an unambiguous ordering consistently, because a reader has no way to tell 04/07 from 07/04.
- 3 State the time zone whenever the value is a specific moment rather than a calendar day, and be explicit about whose zone it is — the viewer's, the record's, or the account's — rather than leaving it implied.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/date-and-time-display-component
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.