Reminder Scheduling
Let users ask the app to bring something back to their attention later.
What it adds
A reminder a user sets on a specific record, delivered at a chosen time through the notification channels the app already has.
What your agent is told to do
5
What your agent is told to do
5-
1
Add a reminder action to the records users actually revisit, and store each reminder against both the user and the record.
-
2
Offer quick presets (tomorrow morning, next week) alongside an exact date and time.
-
3
Schedule against the user's time zone and show the resolved absolute time back to them before saving, so there is no ambiguity about what they picked.
-
4
Deliver through the existing notification center rather than adding a new inbox.
-
5
Do NOT fire a reminder without re-checking that the user can still see the record. Access changes between scheduling and delivery, and a reminder is a leak vector.
Edge cases it handles
6
Edge cases it handles
6- Deleting, archiving, or completing the record must cancel its pending reminders.
- Saving the same reminder twice, or a retried job, must not produce two deliveries — key the schedule so it is idempotent.
- A reminder set for a time already in the past should be rejected at the form, not silently fired immediately.
- If the user changes time zone after scheduling, decide and document whether the reminder moves with them or stays at the original instant.
- A failed delivery (bounced email, revoked push permission) must be visible to the user, not silently discarded.
- Reminders on a record the user has lost access to are cancelled, not delivered with the title redacted.
Definition of done
8
Definition of done
8- Users can set, edit, and cancel a reminder on a record.
- The resolved delivery time is shown before saving, in the user's time zone.
- Deleting or completing the record cancels its reminders.
- Duplicate saves and job retries produce exactly one delivery.
- Access is re-checked at delivery time.
- Delivery failures are surfaced to the user.
- 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.