Add to Calendar Button
Let people put an event straight into whichever calendar they already use.
What it adds
A control beside every date-bearing event that hands the event off to the user's calendar of choice.
What your agent is told to do
5
What your agent is told to do
5-
1
Find every place the app already shows a date and time a person would want to keep: a confirmed booking, a webinar, a trial expiry, a deadline. Put the control there rather than inventing a new events page.
-
2
Offer a handoff for the common hosted calendars and a downloadable calendar file for everything else, and let the download be the fallback rather than a separate hidden option.
-
3
Build the event payload on the server from the same record the confirmation email uses, so the title, location, and description never disagree between the two.
-
4
If the app already creates events directly through Google Calendar Event Creation or Microsoft Outlook Calendar Events, treat this as the unauthenticated path for people who have not connected an account, and reuse the same event-building code rather than writing a second version of it.
-
5
Do not paste the raw event fields into a link and hope for the best. Escape line breaks, commas, and semicolons in the title, location, and notes, because an unescaped one silently truncates or corrupts the event on arrival.
Edge cases it handles
8
Edge cases it handles
8- Line breaks, commas, and semicolons inside the title, location, or notes must be escaped for the destination format. Unescaped, they end the field early and the user gets an event whose description stops mid-sentence.
- An all-day event is encoded as a date range whose end is the day after the last day. Getting this wrong shifts the event by one day, and the user finds out by arriving on the wrong date.
- Give each event a stable identifier derived from the record, not from the moment of generation. Without it, a user who adds the event twice, or adds it after a time change, ends up with two conflicting entries instead of one updated one.
- When a handoff link fails or the destination is blocked by the user's network, fall back to the downloadable file with an explanation rather than leaving a dead button.
- Cap the description length before the destination provider truncates it. Put the essential detail and a link back to the app in the first line, so anything trimmed is trimmed from the end.
- Timed events must carry an explicit time zone, not a floating local time. A floating time moves when the user travels.
- A cancelled or rescheduled booking should not keep offering the old time. Regenerate from the current record every time the control is rendered.
- The control needs a text label, not only an icon, and must be reachable and operable from the keyboard.
Definition of done
8
Definition of done
8- Every event surface in the app offers an add-to-calendar control.
- Titles, locations, and notes containing punctuation and line breaks arrive intact in the calendar.
- All-day events land on the correct day, and timed events carry an explicit time zone.
- Adding the same event twice updates the existing entry rather than creating a duplicate.
- A failed handoff falls back to a downloadable calendar file with a visible explanation.
- The event payload is generated from the same server-side source as the confirmation email.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Contentful Entry Sync
Contentful Entry Sync
Create and update Contentful entries against the connected space, environment, and locale.
What it does
A sync that writes app records into Contentful entries using the connected space's content model and locale configuration.
How it works
- 1 Have the operator select the space, the environment, and the default locale during connection, and store all three, because writing production content into a sandbox environment is an easy and expensive mistake.
- 2 Fetch the content model at connection time and again before each sync run, map app fields to entry fields by their stable identifiers, and validate the value type against the model before attempting the write.
- 3 Write every localized field under an explicit locale rather than relying on whatever the space treats as default, and state clearly which locales the app owns and which it leaves to editors.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/contentful-entry-sync
Typesense Index Sync
Typesense Index Sync
Keep a search index in step with your records so results stay current and correctly scoped.
What it does
A one-way sync from the app's records into a Typesense collection, with server-enforced tenant filtering and a rebuild path.
How it works
- 1 Identify every model users search today and declare the indexed shape explicitly: the fields people type into, the fields they filter and sort on, and nothing more. Treat a missing or newly added field as absent rather than letting the document fail validation.
- 2 Reuse the app's existing background-job system to push creates, updates, and deletes. Do not index inside the request cycle; a slow or unreachable search service must never make a save fail or hang.
- 3 Build the tenant, workspace, and permission filter on the server at query time and attach it to every search. Do not accept a filter, collection name, or scope value from a client-supplied parameter, because anything the browser can set the browser can change.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/typesense-index-sync
Algolia Index Sync
Algolia Index Sync
Keep the search index matching the database, including who is allowed to see what.
What it does
A sync pipeline that mirrors records into a search index with tenant-scoped filters and scheduled reconciliation.
How it works
- 1 Identify every record type that should be searchable and define one index document per record, keyed by an identifier that never changes for the life of that record.
- 2 Push changes through the app's existing background-job system on create, update, and delete, and make every write idempotent so a replayed job produces the same document rather than a duplicate.
- 3 Put tenant, workspace, and visibility values on each document as filter attributes, and have the server issue short-lived scoped search credentials that pin those filters. The browser must never choose its own filter.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/algolia-index-sync
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.