Audio Chapter Markers
Break a long recording into named chapters listeners can see and jump between.
What it adds
Named, timestamped chapters on long audio or video, shown in a list and on the scrubber, each addressable by its own link.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Make each chapter linkable through the app's existing shareable deep link mechanism, so opening the link starts playback at that chapter rather than at the beginning.
-
5
Do not build a separate chapter editing screen away from the player. Editing a boundary without hearing what is at that boundary produces chapters that start one sentence late.
Edge cases it handles
8
Edge cases it handles
8- Authors must be able to override both generated titles and generated boundaries. Automatic segmentation reliably names a chapter after the first thing said in it, which is often the end of the previous topic.
- Chapters only a few seconds long turn the scrubber into a picket fence. Enforce a minimum duration, and either merge or refuse to display markers that would collide at the current scrubber width.
- Re-encoding or trimming the media invalidates absolute marker positions. Detect that the source duration changed, and either remap the markers or flag them as needing review rather than silently seeking to the wrong place.
- Each chapter needs a deep link that starts playback at that point, and that link must still land somewhere sensible if the chapter has since been deleted.
- A recording with a single chapter should render as an ordinary recording with no chapter list, not as a list with one entry and an empty scrubber.
- Chapter titles travel further than the player: they land in the episode description and in any feed the audio is syndicated to, where the app cannot edit them afterwards. Limit their length so they do not overflow the scrubber, and screen them before the recording is published.
- A chapter start time beyond the end of the media, or two chapters starting at the same second, must be rejected at save time with a clear message.
- The chapter list must be keyboard navigable and announce the current chapter, and marker positions must not be the only indication of where a chapter begins.
Definition of done
9
Definition of done
9- Chapters appear as a list beside the player and as markers on the scrubber.
- Authors can add, rename, and delete chapters from the player, with the current position as the default start.
- Author edits survive a regeneration of automatic chapters.
- Each chapter has a deep link that starts playback at its start time.
- Chapters below the minimum duration are prevented, and overlapping or out-of-range start times are rejected on save.
- A single-chapter recording renders without chapter chrome.
- The chapter list is keyboard navigable and announces the active chapter.
- 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.