Algolia Search Implementation

Use this skill as the execution checklist for net-new Algolia search builds, loaded from algolia-discovery-planning once the phase plan marks a greenfield implementation in scope. Its job is to make data, events, index configuration, UI, and release QA visible decision points, especially when an agent needs to move quickly or proceed with provisional assumptions.

Use the whole Algolia lens: data and events are not side quests. The data contract determines what search can retrieve, rank, filter, display, merchandise, secure, and attribute. The event foundation determines whether analytics, personalization, Recommend, Dynamic Re-Ranking, NeuralSearch evaluation, and Agent Studio feedback loops can be trusted. Let UI and AI feature decisions inherit from those foundations instead of discovering them late.

Recommended Workflow

For any net-new Algolia search, browse, autocomplete, ecommerce, recommendations, personalization, or Dynamic Re-Ranking implementation, work through these checkpoints in order when practical:

1. Data contract checkpoint: use algolia-data-modeling.
2. Event instrumentation checkpoint: use algolia-events-insights.
3. Index configuration checkpoint: use algolia-index-configuration.
4. UI implementation checkpoint:
   • Choosing the UI library, framework fit, SSR/routing strategy, or mobile SDKs: use algolia-ui-libraries.
   • Autocomplete or typeahead: use algolia-autocomplete.
   • Search results page, browse page, filters, facets, routing, sort, pagination, or current refinements: use algolia-instantsearch-ui.
   • Current framework APIs and production code details: use the official instantsearch skill alongside algolia-instantsearch-ui or algolia-autocomplete.
5. Release QA checkpoint: use algolia-release-qa.