Mapbox Geocoding
Convert typed locations into coordinates and structured addresses the app can use.
What it adds
Forward and reverse geocoding with confirmed matches, controlled result bias, and coordinate precision rules.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Keep the request credential off the public page, or scope it to one capability and origin. Store returned coordinates at a precision that suits the use, and record who is permitted to see them.
-
5
Google Places Address Lookup covers address autocomplete for form entry. Where both exist, use one provider per field and keep their stored identifiers separate, because identifiers from the two providers are not interchangeable.
Edge cases it handles
8
Edge cases it handles
8- Bias applied without real context distorts results — a user searching for a place in another country gets local noise instead of the answer. Guessed bias is worse than none.
- Two plausible matches must be offered as a choice. Automatic selection is acceptable only when the match is unambiguous and the app can explain why.
- The provider's terms govern attribution and how long results may be cached. Show the required attribution where results appear and respect the caching window rather than building a permanent local copy.
- Reverse lookup of a coordinate in open country may return only a broad region or nothing at all. Treat an empty result as a valid outcome, not an error.
- Coordinates describing a person are personal data. Round to the precision the feature actually needs, state who can see the exact value, and do not store street-level precision for a feature that only needs a city.
- Rate limits apply per credential. Debounce interactive lookups, run bulk work through the app's existing background-job system, and back off on throttling instead of hammering.
- A geocode failure must not block a save. Keep the typed text, mark the record as not yet geocoded, and retry later.
- Coordinates that arrive reversed or outside valid bounds must be rejected before they reach a map or a distance calculation.
Definition of done
9
Definition of done
9- Forward and reverse lookup are separate paths with their own error handling.
- Ambiguous matches are confirmed by the user rather than auto-selected.
- Bias is applied only from known context and never from a guessed source.
- Required attribution is shown and caching stays within the provider's terms.
- Stored coordinate precision matches the feature's need and is covered by an access rule.
- A failed or empty geocode leaves the record saveable with the typed text intact.
- Bulk geocoding runs as background jobs that back off when throttled.
- 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.