Watch an Item
Follow one record and get told when something changes on it.
What it adds
Per-record change subscriptions, with automatic watching when a user comments or is assigned, and one-click unwatch.
What your agent is told to do
5
What your agent is told to do
5-
1
Add a watch subscription joining a user to a single record, with a control on the record itself showing current state and the watcher count.
-
2
Auto-watch a user when they comment on, are assigned to, or create a record — then tell them you did it, and make the unwatch obvious.
-
3
Define the exact list of events that notify watchers, and let a watcher mute event types they do not care about while staying subscribed.
-
4
Put an unwatch action inside every notification the subscription generates, so the user can stop it at the moment it annoys them rather than hunting for the record.
-
5
Do NOT reuse or duplicate Favorites. Favorites is a personal bookmark for finding things again; a watch is a subscription that sends messages. Keep them as separate state with separate controls.
Edge cases it handles
6
Edge cases it handles
6- One user action that fires several internal events must produce one notification, not four.
- A user must never be notified about their own change to a record they watch.
- Losing access to the record must stop delivery immediately, including for anything already queued.
- Deleting, archiving, or merging a record needs a defined outcome for its watchers — silently dropping them loses the notification they were waiting for.
- Watch state belongs to a workspace. The same user in two workspaces must not leak subscriptions between them.
- A record with many watchers must fan out asynchronously; do not send during the request that made the change.
Definition of done
8
Definition of done
8- Any record can be watched and unwatched, with the current state visible on the record.
- Commenting on or being assigned to a record starts a watch and tells the user.
- Watchers can mute specific event types without unwatching.
- Every generated notification carries a working unwatch action.
- Users are not notified about their own changes and duplicate events collapse into one.
- Revoked access stops delivery immediately, including queued messages.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Prize Wheel Giveaway
Prize Wheel Giveaway
Run a spin-the-wheel giveaway where each entrant gets one spin and a recorded prize.
What it does
A giveaway with a wheel interface, one server-decided spin per entrant, and a durable record of every result.
How it works
- 1 Decide the outcome on the server before the wheel starts turning. The request returns a prize, the animation lands on it, and the client is only ever playing back a result it was given.
- 2 Model prizes with explicit weights and optional stock counts, and let an operator edit them without a deploy. A giveaway whose odds live in code cannot be corrected once it is live.
- 3 Tie an entry to an account where the app has one, and where it does not, combine the strongest identifiers available and treat a single spin as the hard limit across all of them.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/prize-wheel-giveaway
Poll Widget
Poll Widget
Ask a one-question poll anywhere in the app and show the results as soon as someone votes.
What it does
An embeddable single-question poll with a vote control and a results view revealed after voting.
How it works
- 1 Keep it to one question with a small set of options. The moment it grows a second question it is a survey and belongs in the survey feature instead.
- 2 Record the vote on the server and return the updated tallies in the same response, so the results the voter sees are the real counts rather than an optimistic local guess that may disagree after a refresh.
- 3 Hold voting open to signed-out visitors if the poll is public, and identify them well enough to prevent casual repeat voting without demanding an account for a single click.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/poll-widget
Announcement Bar
Announcement Bar
Put a timed message across the top of the site without shipping a deploy.
What it does
An operator-configured, dismissible strip at the top of public pages, with scheduling and a link.
How it works
- 1 Extend the existing Service Incident Banner rather than adding a second bar. It already handles scheduling, targeting, dismissal, and severity; this is a marketing-styled variant of the same component, and two independent bars will eventually stack on top of each other.
- 2 Let an operator set the message, an optional link, background and text colours, and a start and end time from an admin screen. Requiring a deploy to run a weekend promotion means it goes live late.
- 3 Insert the bar into the document flow so it pushes fixed headers and sticky navigation down. Overlaying it on top of the header hides navigation on exactly the pages people arrived on.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/announcement-bar
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.