Algolia Index Sync
Keep the search index matching the database, including who is allowed to see what.
What it adds
A sync pipeline that mirrors records into a search index with tenant-scoped filters and scheduled reconciliation.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Run backfills in batches sized to the provider's limits and throttled so a reindex does not starve live updates, and make a full rebuild something an operator can run without taking search offline.
-
5
Schedule a reconciliation that compares the index against the source of truth and repairs the difference. Search indexes drift, and a system with no reconciliation will be quietly wrong within a month.
Edge cases it handles
8
Edge cases it handles
8- An identifier derived from mutable data such as a slug or a title creates a duplicate document on every rename. Key documents by the record's permanent identifier.
- A deleted record, or one whose access was revoked, must leave search immediately. A stale document that still matches is a data leak, not a cosmetic bug.
- Filters enforced only in client code can be edited by the user. The filter has to be signed into the search credential the server issues, and that credential has to expire.
- Bulk operations exceed the provider's request size and rate limits. Chunk the payload, respect the retry interval it returns, and back off rather than dropping records on the floor.
- Indexing jobs fail, notifications are missed, and deploys interrupt queues. Reconciliation must find both missing and orphaned documents and repair each without a manual export.
- Index writes are eventually consistent. A user who saves a record and searches for it a second later may not find it, so drive the immediate view from the database rather than from search.
- Indexed content can include fields the searching user may not see. Decide per field what is indexed and returned, and keep private fields out of the document entirely rather than hiding them at render time.
- When the provider is unavailable the app must fall back to whatever database-backed search or listing it already has, with a notice, rather than showing an empty result page.
Definition of done
9
Definition of done
9- Every searchable record type has a document keyed by a permanent identifier.
- Create, update, and delete propagate through background jobs and are idempotent on replay.
- Deletion and access revocation remove the record from search results.
- Search credentials are issued server-side, scoped to the caller's tenant and visibility, and expire.
- Backfills batch within provider limits and do not block live updates.
- A scheduled reconciliation finds and repairs missing and orphaned documents.
- A provider outage falls back to the app's own search with a visible notice.
- 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
Mapbox Geocoding
Mapbox Geocoding
Convert typed locations into coordinates and structured addresses the app can use.
What it does
Forward and reverse geocoding with confirmed matches, controlled result bias, and coordinate precision rules.
How it works
- 1 Separate the two directions explicitly: text to coordinates for entry and search, coordinates to address for a dropped pin or a device location. They take different inputs, carry different confidence, and fail differently.
- 2 Present ambiguous matches as a list the user confirms. Silently taking the first result is how a record ends up in the wrong country with nobody noticing for months.
- 3 Bias results toward a location only when the app genuinely knows one, such as a workspace address or the map viewport the user is already looking at.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/mapbox-geocoding
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.