Relative Time Component
Show times as ages people can read, without losing the exact moment underneath.
What it adds
One shared timestamp element that renders an age in words and carries the precise local date with it.
What your agent is told to do
5
What your agent is told to do
5-
1
Find every place the app prints a date or a time — activity feeds, comment headers, audit rows, table cells, tooltips — and route them all through one component so the wording is identical everywhere.
-
2
Render from a machine-readable instant supplied by the server in a single unambiguous format, and do the conversion to the viewer's zone at display time rather than storing a formatted string.
-
3
Refresh the visible text on a schedule that matches its own granularity: something a few seconds old updates often, something two days old does not need to update at all.
-
4
Cross over to an absolute date once relative wording stops helping. Anything older than about a week reads better as a real date than as a count of days.
-
5
Do not run one global timer that re-renders every timestamp on the page each second. On a long feed that is a repeated layout cost for text that has not changed.
Edge cases it handles
7
Edge cases it handles
7- Update intervals must follow the age of the value — a per-second tick on a timestamp measured in months is wasted work, and a per-minute tick on something seconds old reads as frozen.
- There has to be a defined threshold at which relative wording gives way to an absolute date, because 'in 428 days' tells a reader nothing they can act on.
- A device clock that is wrong, or a record written a moment ago on a server that is slightly ahead, will produce a timestamp in the future. Clamp small skew to 'just now' rather than printing a negative age.
- The exact local time must be reachable, not just visible on hover. Put it in the element's accessible text and its title so keyboard and screen reader users get the same detail as a mouse user.
- Time zone and locale come from the viewer, not the server, and a user who travels or changes their profile zone must see the new zone without a hard reload.
- Boundaries like 'yesterday' and 'today' shift at local midnight, so a page left open overnight must not still be claiming that a two-day-old event happened today.
- Durations and ranges are a different problem from ages — do not force a start-to-end span through the same wording.
Definition of done
8
Definition of done
8- Every rendered date and time in the app comes from the single shared component.
- Relative text updates at an interval proportional to the value's age, with no global per-second re-render.
- Values past the defined threshold render as absolute dates in the viewer's locale.
- Timestamps slightly in the future render as 'just now' rather than as a negative or nonsensical age.
- The precise local date and time are available to screen readers and keyboard users, not only on hover.
- Zone and locale follow the viewer's settings and update when those settings change.
- 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.