Edit Conflict Detection
Catch it when someone else saved the record while you were editing it.
What it adds
Detects that a record changed underneath an open editor and gives the user a real choice about what to keep.
What your agent is told to do
5
What your agent is told to do
5-
1
Give every editable record a version token — a counter or updated-at value — and send it back with the save. Compare it inside the same transaction as the write, not before it.
-
2
When the token does not match, reject the write and show a conflict screen: what the user typed, what is now stored, and which fields actually differ.
-
3
Offer three explicit outcomes — merge the non-overlapping fields, overwrite with the user's version, or discard the user's version and reload.
-
4
Persist the losing draft somewhere the user can get it back before applying any resolution. A conflict must never be the reason work disappears.
-
5
Do NOT build snapshots, diffs of past revisions, or a restore timeline here — that is Version History's job. This feature only handles the collision at the moment of writing.
Edge cases it handles
6
Edge cases it handles
6- Autosave must not throw a modal every few seconds. Detect the conflict once, pause autosave, and hold the draft locally until the user resolves it.
- Two users editing different fields of the same record should merge cleanly without either being asked anything.
- A conflict caused by the same user in a second tab still needs resolving — do not skip the check because the author matches.
- If the record was deleted while the editor was open, that is a conflict too, and 'overwrite' must not resurrect it silently.
- Comparing serialized JSON or rich text will report conflicts on whitespace and key order. Normalize before you diff.
- The version token must come from the server. A client-generated timestamp on a machine with a wrong clock defeats the whole mechanism.
Definition of done
8
Definition of done
8- A stale write is rejected by a server-side version check inside the write transaction.
- The conflict UI shows the user's version, the stored version, and the specific differing fields.
- Merge, overwrite, and discard are all available and all work.
- The losing draft is recoverable after any resolution.
- Non-overlapping edits merge without prompting.
- Autosave surfaces a conflict once, not repeatedly.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Direct Messages
Direct Messages
Let two users hold a private conversation inside the app instead of leaving to email.
What it does
One-to-one private threads with message history, per-conversation unread counts, and blocking.
How it works
- 1 Build the conversation list, the thread view, and the unread badge. Keep the first version to one-to-one threads only and defer group conversations, reactions, threading, and file attachments rather than shipping all of them half-finished.
- 2 Reuse the app's existing Read and Unread State and Notification Center rather than inventing a second unread mechanism and a second alert path. A message notification should sit alongside every other notification the user gets.
- 3 Reuse the composer, mention handling, and rendering rules from Comments and Mentions instead of writing a second message editor with subtly different escaping.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/direct-messages
Voice Notes
Voice Notes
Say it instead of typing it, and attach the recording where the conversation is.
What it does
In-app recording of short audio notes attached to a record, comment, or message.
How it works
- 1 Add recording to the places where people already leave text, most likely alongside Comments and Mentions, so a voice note is another kind of comment rather than a separate feed nobody checks.
- 2 Store the recording through the app's existing file upload path so a voice note inherits the same retention and access rules as any other attachment on the record, and disappears with the record when it is deleted.
- 3 Show a live duration and a simple level meter while recording, and let the user review and discard before it is sent. Nobody should be committed to a recording the instant they stop.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/voice-notes
Assign Ownership
Assign Ownership
Make it obvious who is responsible for each record.
What it does
An assignee on records, with a picker, notifications on change, and a history of who owned what.
How it works
- 1 Add a nullable assignee to the relevant records. Unassigned is a real, valid state — do not force a default owner just to avoid the null.
- 2 Restrict the picker to users who can actually access the item, and validate that server-side as well as filtering the list.
- 3 Notify the new assignee when they are assigned by someone else, and record every change with the actor and timestamp.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/assign-ownership
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.