Quick Create
Create a common record from anywhere without leaving what you're doing.
What it adds
A compact creation surface, reachable from anywhere in the app, holding only the fields a record genuinely requires.
What your agent is told to do
6
What your agent is told to do
6-
1
Pick the record types users create most and include only their required fields. If the short form needs eight fields, that record does not belong here.
-
2
Filter the list of creatable types by the current user's permissions, evaluated on the server. A hidden menu item is not authorisation.
-
3
Prefill defaults from the current context — the workspace, project, or record being viewed — and never from a workspace the user has since left. Stale context leaks data across boundaries.
-
4
When validation needs a field the short form does not have, expand to the full form with everything the user already typed still in place. Losing their input is the fastest way to make them stop using this.
-
5
Return focus to whatever triggered the creation, and refresh the affected list in place rather than reloading the page.
-
6
Do not build a keyboard-driven command launcher here. Invocation by keystroke is owned by Command Palette; register this as an action there rather than building a second one.
Edge cases it handles
6
Edge cases it handles
6- Closing mid-entry must either warn or preserve a draft — silent discard of typed content is unacceptable.
- A double submit must not create two records; disable and guard server-side with an idempotency key.
- Creating from a filtered list may produce a record that does not match the filter — say so rather than appearing to create nothing.
- A record type the user could create when the surface opened may be revoked before they submit; handle the rejection cleanly.
- On mobile the surface must not be covered by the on-screen keyboard.
- The created record must be reachable immediately — link to it, do not just close.
Definition of done
8
Definition of done
8- The surface is reachable from every main screen.
- Only record types the user may create are offered, enforced server-side.
- Defaults come from live context and never from a stale or foreign workspace.
- Escalating to the full form preserves all entered data.
- The underlying list updates and focus returns to the trigger on success.
- Duplicate submissions cannot create duplicate records.
- 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.