Booking Page
A shareable page where someone picks an open time and confirms it in a few clicks.
What it adds
A public scheduling page listing open slots, taking a booking, and confirming it to both sides.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
If the app already has Calendly Booking Sync or Google Calendar Event Creation, write confirmed bookings through those so the owner's calendar stays the source of truth, rather than maintaining a second parallel calendar.
-
5
Defer payments, round-robin assignment across a team, recurring appointments, and group events. Ship single-person, single-slot booking that works, rather than half of a scheduling product.
Edge cases it handles
8
Edge cases it handles
8- A visitor filling in the form is not yet booked. Place a short expiring hold on the slot when they begin, release it if they abandon, and show a clear message if the hold lapses before they submit.
- Two visitors can confirm the same slot within the same second. Enforce the conflict as a uniqueness constraint at the database level, and when the second booking loses, tell that visitor and offer the nearest open times rather than showing a generic failure.
- Times must be shown in the visitor's local zone and stored as absolute instants. A booking rendered in the owner's zone will be attended an hour early or missed entirely.
- Minimum notice and maximum horizon both have to be enforced server-side. Without them a visitor books a slot ten minutes from now, or something eighteen months out that will never be honoured.
- A slot near a daylight saving transition can be ambiguous or nonexistent in local time. Resolve it against the absolute instant and never generate a slot that does not exist locally.
- A cancellation or reschedule link must be unguessable and scoped to one booking, since the person holding it is not signed in.
- The confirmation email can fail to send. The booking still exists, so surface the details on screen and retry delivery rather than leaving the visitor unsure.
- The public page is an unauthenticated form and will be scraped and spammed. Rate-limit by address and require email confirmation before the slot is held permanently.
Definition of done
9
Definition of done
9- A visitor can pick a slot and confirm a booking without an account.
- Open slots are computed server-side from availability and existing bookings at request time.
- Two simultaneous confirmations for the same slot result in exactly one booking, and the loser is offered alternatives.
- Times display in the visitor's zone with the zone named, and are stored as absolute instants.
- Minimum notice and booking horizon are enforced on the server and cannot be bypassed from the client.
- Slots spanning a daylight saving change resolve to the correct instant, with no nonexistent local times offered.
- Both parties receive confirmation, and cancellation links work without sign-in.
- 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
Audio Chapter Markers
Audio Chapter Markers
Break a long recording into named chapters listeners can see and jump between.
What it does
Named, timestamped chapters on long audio or video, shown in a list and on the scrubber, each addressable by its own link.
How it works
- 1 Store chapters as an ordered list of start times and titles attached to the existing media record, and render them both as a list beside the player and as markers on the scrubber.
- 2 Let an author add, rename, reorder by moving start times, and delete chapters in the player itself, with the current playback position offered as the default start time for a new chapter.
- 3 If chapters are generated automatically, treat the generated set as a first draft. The author's edits must win and must survive the next generation run.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/audio-chapter-markers
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.