Favorites
Let people pin the things they keep coming back to.
What it adds
A star/save action on your records, plus a place to see everything saved.
What your agent is told to do
4
What your agent is told to do
4-
1
Add a favorite toggle to the app's primary record type(s), on both the list and detail views.
-
2
Store favorites as a join between user and record with a uniqueness constraint — favoriting twice must not create two rows.
-
3
Give favorites a home: a filter on the list, and a section on the dashboard.
-
4
Update the toggle optimistically so it feels instant, but reconcile with the server response.
Edge cases it handles
4
Edge cases it handles
4- Double-clicking the star must not create a duplicate or leave the UI out of sync.
- Favoriting requires sign-in — prompt rather than silently doing nothing.
- A favorited record that gets deleted must be removed from favorites.
- A favorited record the user loses access to must not appear in their list.
Definition of done
7
Definition of done
7- Favoriting is one click from both the list and the detail view.
- The database prevents duplicate favorites.
- There is a single place to see everything favorited.
- The toggle feels instant and stays correct if the request fails.
- Signed-out users are prompted to 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
Interactive Transcript
Interactive Transcript
Put the transcript next to the player so clicking any line jumps playback to that moment.
What it does
A time-aligned transcript panel beside the audio or video player, with click-to-seek, a moving highlight, and in-transcript search.
How it works
- 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.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/interactive-transcript
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.