Scroll Shadow Indicator
Show people that a panel or table has more content past its edge.
What it adds
Edge shading on scrollable containers that appears only on the sides where content continues.
What your agent is told to do
5
What your agent is told to do
5-
1
Find the containers that scroll independently of the page — tables, side panels, dialog bodies, tab strips, code blocks — and give each an edge treatment that appears only where content continues past that edge.
-
2
Recompute the indicators whenever the scroll position moves, the container resizes, or the content changes. A shadow that was correct at first render is wrong the moment a row is filtered out.
-
3
Handle both axes. A wide table needs left and right indicators far more urgently than top and bottom, because horizontal overflow is the kind users are least likely to guess at.
-
4
Draw the indicator so it never sits on top of a sticky header, a frozen first column, or a pinned action row. Those elements own their edge, and a shadow over them reads as a rendering fault — take the offsets from Safe Sticky Positioning rather than guessing at heights.
-
5
Do not leave a permanent shadow on every scrollable container. An indicator that shows when there is nothing more to see teaches users to ignore it, which defeats the whole point.
Edge cases it handles
7
Edge cases it handles
7- Content that loads late, a filter that removes rows, or a section that expands all change whether overflow exists, so the indicators must be driven by live measurement rather than computed once when the container mounts.
- A container that scrolls on both axes needs four independent indicators, and the corner where two of them meet must not double up into a dark blot.
- A shadow drawn over a sticky header or a frozen column looks like a smudge rather than an affordance; the indicator has to sit beneath the pinned content or begin below it.
- Containers whose content fits must show nothing at all, including during the moment they briefly overflow while a resize is in progress.
- The indicator is decoration and must be invisible to assistive technology and transparent to pointer events. A shadow that swallows a click on the first row is worse than no shadow.
- Forced-colours and high contrast modes drop shadows entirely, so a container relying on one alone gives no hint of overflow — pair it with a border or accept the loss deliberately.
- Measuring on every scroll event in a long table is expensive; sample the position rather than forcing a layout calculation on each frame.
Definition of done
9
Definition of done
9- Every independently scrolling container indicates its edges only where content continues.
- Indicators update on scroll, on container resize, and when the content changes.
- Horizontal and vertical overflow are both indicated, including in containers that scroll on both axes.
- No indicator overlaps a sticky header, frozen column, or pinned row.
- Containers with no overflow show no indicator at all.
- Indicators receive no pointer events and are not announced to screen readers.
- Overflow remains discoverable in forced-colours mode.
- 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.