Notification Digests
Bundle routine notifications into one scheduled summary instead of a stream.
What it adds
Batched delivery of low-urgency notifications on a per-user schedule, grouped into a readable summary.
What your agent is told to do
5
What your agent is told to do
5-
1
Extend the existing notification preference model with a per-category delivery cadence — instant, daily, weekly, off — rather than creating a separate digest settings table.
-
2
Mark each notification type as digestible or urgent. Security alerts, mentions, and direct assignments should keep going out immediately; routine activity is what batches.
-
3
Assemble a digest from the notifications accumulated since the last one, grouped by record and by actor so it reads as a summary rather than a log dump.
-
4
Schedule sends in the user's own time zone at a chosen local hour, and define a cutoff so events arriving mid-assembly land in the next digest instead of being dropped.
-
5
Do NOT send an empty digest. No activity means no email, and no 'nothing happened this week' message either.
Edge cases it handles
6
Edge cases it handles
6- Anything already delivered instantly must be excluded, or users get told twice.
- Items the user can no longer access by send time must be filtered out at assembly, not just at enqueue.
- Ten changes to one record should collapse into one line with a count, not ten lines.
- A user changing time zone mid-window must not get a double digest or skip one entirely.
- Switching a category from instant to daily must not replay the backlog that was already sent.
- Digest assembly must be idempotent — a retried job cannot send the same summary twice.
Definition of done
8
Definition of done
8- Cadence is set per category on the existing preference model.
- Urgent types bypass digesting and still send immediately.
- Digests group and deduplicate events by record and actor.
- Delivery lands at the chosen local hour in the user's time zone.
- No digest is sent for an empty window.
- Retried assembly jobs do not produce duplicate sends.
- 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.