Comments and Mentions
Keep discussion on the record instead of in chat and email.
What it adds
Threaded comments attached to a record, with @-mentions that notify the person mentioned.
What your agent is told to do
5
What your agent is told to do
5-
1
Attach comments to a record polymorphically so the same component works across object types rather than being rebuilt per model.
-
2
Store mentions as structured references to user IDs, not as raw text parsed at render time. Display names change; IDs do not.
-
3
Restrict the mention picker to users who can already see the record, and reject mentions of anyone else on the server.
-
4
Notify each mentioned user once per comment. Track what has been sent so an edit or a delivery retry cannot fire a second notification.
-
5
Do NOT allow raw HTML in comment bodies. Sanitize to a small allowlist and render links with rel=noopener — comments are the most-pasted surface in any app.
Edge cases it handles
6
Edge cases it handles
6- Editing a comment to add a new mention should notify only the newly added person, never everyone again.
- A deleted user's past mentions must still render as inert text, not as a broken link or a blank.
- Deleting a comment with replies must not orphan them — either soft-delete with a tombstone or cascade deliberately.
- Mentioning someone must never grant them access. If they cannot open the record, the notification is a dead link.
- Comments arriving in realtime must insert in a stable order, and must not scroll the reader away from what they were reading.
- Show edited and deleted state. A silently rewritten comment is a trust problem in any thread people rely on.
Definition of done
8
Definition of done
8- Comments attach to any supported record type through one implementation.
- Mentions are stored as user references and survive display-name changes.
- Only users with access to the record can be mentioned, enforced server-side.
- Each mention notifies exactly once, including across edits and retries.
- Comment bodies are sanitized to an allowlist and links carry rel=noopener.
- Edited and deleted comments are visibly marked and ordering stays stable under realtime updates.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
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
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
Internal Notes
Internal Notes
Give staff a place to write things the customer must never see.
What it does
Notes attached to a record that are readable only by internal roles, and that never appear in any export, feed, or API response.
How it works
- 1 Model an internal note as a distinct visibility state on the server, not a flag the client filters on. Every read path — record view, search, digest emails, exports, webhooks, API serializers — must exclude internal notes for anyone without the internal role.
- 2 Give internal notes a visual treatment that cannot be confused with a public comment: different surface, a persistent label, and a warning that survives collapse or truncation. If a user has to remember which box is which, this feature has failed.
- 3 Decide explicitly what an impersonating admin or a support session sees, and state the rule in the UI. Support staff reading internal notes is usually fine; a support session rendering them inside a screen the customer is watching is not.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/internal-notes
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.