Interactive Transcript
Put the transcript next to the player so clicking any line jumps playback to that moment.
What it adds
A time-aligned transcript panel beside the audio or video player, with click-to-seek, a moving highlight, and in-transcript search.
What your agent is told to do
5
What your agent is told to do
5-
1
Render the transcript from the timestamps the app already stores. If Voice Transcription exists, extend its output and its data model rather than producing a second transcript with its own timings.
-
2
Make every line a real seek target: clicking or pressing enter on a line moves playback to that time and keeps focus where the user left it.
-
3
Highlight the line currently being spoken and keep it in view as playback advances, using the player's own time updates rather than a separate timer.
-
4
Add a search box over the transcript that lists matches and jumps playback to any of them. Reuse the app's existing search match highlighting so results look the same as everywhere else.
-
5
Do not render thousands of lines into the page at once. Virtualise the list, and make sure seeking to a far-off match still works when the target line has not been rendered yet.
Edge cases it handles
8
Edge cases it handles
8- Auto-scrolling the active line into view fights a user who is scrolling by hand. Suspend follow mode as soon as they scroll away, and offer a visible control to jump back to the current position.
- A transcript of several thousand lines will stall the page if every line is mounted and every line re-renders on each time update. Virtualise, and update only the lines whose highlight state actually changed.
- In-transcript search must show how many matches there are and let the user step between them, jumping playback to each. A search that only dims non-matching text is not enough on a long recording.
- Changing playback speed must not drift the highlight. Derive the active line from the player's reported current time, never from an interval that assumes real-time playback.
- On a narrow screen the side-by-side layout has to stack, with the player pinned so it stays visible while the user scrolls the transcript. A transcript that scrolls the player off the top is unusable.
- Lines with missing or overlapping timestamps must still render as text and simply not be clickable, rather than seeking to zero.
- Seeking must survive the media not being loaded yet: queue the seek and apply it once the player is ready.
- The transcript must remain selectable and copyable as plain continuous text, including across the boundaries of virtualised lines.
Definition of done
9
Definition of done
9- Clicking or keyboard-activating any line seeks playback to that moment.
- The active line is highlighted and follows playback, and manual scrolling suspends follow until the user returns.
- A transcript of several thousand lines scrolls and highlights without visible lag.
- In-transcript search reports match counts and jumps playback to each match.
- The highlight stays correct at every supported playback rate.
- The layout stacks on narrow screens with the player still visible.
- Transcript text can be selected and copied as continuous prose.
- 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.