Highlight Clip Maker
Turn a selected passage of a transcript into a short clip that can be shared.
What it adds
Selection of transcript lines that renders a trimmed, captioned clip of the source media with a shareable link.
What your agent is told to do
5
What your agent is told to do
5-
1
Build the selection on top of the app's interactive transcript. The user selects a run of lines, sees the resulting start and end time and duration, and adjusts the edges before rendering.
-
2
Render clips through the app's existing background job system so the user is not held on a progress bar, and notify them through the existing notification centre when the clip is ready or has failed.
-
3
Burn the transcript text into the clip as captions, since most places a clip is shared autoplay it silently. Give the user a way to turn captions off before rendering.
-
4
Share clips through the app's existing signed share link mechanism rather than making a new public URL scheme, and honour the source media's visibility when deciding whether sharing is allowed at all.
-
5
Do not build a general video editor. Trim, captions, and a single output size cover the case; multi-segment editing, overlays, and transitions should be deferred rather than half-built.
Edge cases it handles
8
Edge cases it handles
8- Snap the clip edges to sentence boundaries from the transcript rather than to the raw selection, so a clip does not open and close mid-word. Let the user nudge past the snap when they need to.
- Enforce a maximum clip length. Warn as the selection approaches it and block rendering beyond it, because an unbounded selection is really a request to re-encode the whole recording.
- Rendering happens in the background and can take minutes. Show the job's state where the user will see it, notify them on completion, and make the clip retrievable later without repeating the selection.
- Captions burned into the clip must be legible over the underlying video at small sizes, which means a background or outline rather than plain white text on whatever happens to be behind it.
- When the source media is deleted, its clips and their share links must stop working. Revoke or expire them rather than leaving a public URL pointing at content the owner believed they had removed.
- A failed render must report why in plain language and leave the selection intact so the user can retry, not discard the work and return them to the transcript.
- Clips of private media must not become public by being clipped. Default the share link to the same audience as the source and require a deliberate step to widen it.
- The same selection requested twice should reuse the existing rendered clip rather than queueing a second identical job.
Definition of done
9
Definition of done
9- Selecting transcript lines produces a clip with visible start, end, and duration before rendering.
- Clip edges snap to sentence boundaries and can still be adjusted manually.
- Clips over the maximum length are warned about and cannot be rendered.
- Rendering runs as a background job with a completion or failure notification.
- Captions are burned in by default and remain legible at small sizes.
- Deleting the source media revokes its clips and their share links.
- Clip sharing defaults to the source media's audience.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Digital Business Card
Digital Business Card
Give every member a shareable card page with their photo, links, and save-to-contacts.
What it does
A per-member public card page with photo, role, links, and a download that imports into a phone's contacts.
How it works
- 1 Build this as a presentation of the app's existing Public Profile Pages, not a second profile. One record, two layouts. A member who updates their title should not have to update it twice.
- 2 Take the photo from Avatar Upload rather than adding a new image field, and reuse the crop and compression the app already applies so a card photo is not a full-resolution original served to every visitor.
- 3 Give each card a save-to-contacts download containing the fields the member has chosen to publish, and nothing else. Everything on the card and nothing beyond it.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/digital-business-card
Share Image Generator
Share Image Generator
Give every shared link a proper preview image instead of a blank card.
What it does
Server-side generation of a per-page preview image, referenced by the page's existing share metadata.
How it works
- 1 Find where the app already sets its share metadata, most likely alongside Social Sharing or Shareable Deep Links, and point the image tag at the generated URL rather than adding a parallel metadata block.
- 2 Generate the image on the server from the record's own title, author, and a brand mark. Do not render it in the visitor's browser; the services that fetch previews do not run scripts.
- 3 Design one template that degrades well, then add variants only where the content type genuinely differs. Three good templates beat a configurable layout engine nobody tunes.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/share-image-generator
Public Profile Pages
Public Profile Pages
Give users a page worth sharing.
What it does
A public, shareable profile page per user, with control over what's visible.
How it works
- 1 Give each user a public URL with a slug they choose, not a database ID.
- 2 Let the user decide what appears — default to private and let them opt in.
- 3 Make the page work signed-out, and give it proper SEO and share metadata.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/public-profile-pages
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.