---
name: algolia-reference-architecture
description: >-
  Design or review an Algolia search architecture across source data, indexing, query, UI, events, and operations. Use when establishing system boundaries or evaluating an existing integration. Trigger with "Algolia architecture", "design search platform", or "review Algolia integration".
argument-hint: "[repository-path] [system-scope]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.8.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
  - saas
  - algolia
  - architecture
model: inherit
effort: medium
compatibility: Designed for Claude Code
title: algolia-reference-architecture
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/algolia-reference-architecture
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/official-docs.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/algolia-reference-architecture/references/official-docs.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/algolia-reference-architecture`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/algolia-reference-architecture`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/algolia-reference-architecture) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/algolia-reference-architecture`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/algolia-reference-architecture --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/algolia-reference-architecture --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Algolia Reference Architecture

## Overview

This skill produces an evidence-backed architecture tailored to the repository. It avoids presenting optional Algolia products or provider features as mandatory and makes trust, data, and failure boundaries explicit.

## Prerequisites

- A named repository, environment, and Algolia application or index in scope
- The local lockfile and installed client types as implementation authority
- A safe read-only query or explicitly disposable test target
- Current first-party documentation for any provider behavior that affects the change

## Tool Discipline

Use `Read`, `Glob`, and `Grep` to inspect local code, configuration names, tests, and dependency versions. Use `WebFetch` only for current official Algolia documentation. Use `Write` or `Edit` only after identifying the target files, constraints, and verification plan.

## Current Contract

- The source system remains authoritative; Algolia is a derived search projection.
- Separate indexing, browser search, server search, events, analytics, and workforce administration trust zones.
- Version record transforms and search configuration with the application.
- Design task completion, reconciliation, observability, and rollback before production cutover.

## Authentication

Assign distinct least-privilege credentials to each machine actor and use provider team controls for human access. Generate tenant-scoped secured keys only on trusted servers.

## Instructions

1. Map current components, data stores, producers, consumers, credentials, indices, and deployment environments.
2. Define the record contract, stable identity, deletion semantics, settings ownership, and freshness objective.
3. Choose query and UI boundaries, including browser versus server execution and tenant restrictions.
4. Add event flow only where consent, user-token, query-ID, and validation requirements are owned.
5. Model failures for source lag, partial indexing, key denial, provider degradation, and relevance regressions.
6. Produce architecture decisions, interfaces, tests, observability, rollout, and rollback.

## Approval Boundaries

Do not select paid features, centralize unrestricted credentials, or authorize a migration solely from a generic reference diagram.

## Output

Return the as-is and proposed boundaries, data and trust flows, decision records, interfaces, failure modes, security controls, validation plan, and phased rollout.

## Error Handling

| Condition | Response |
|---|---|
| Repository contradicts assumed topology | Follow repository evidence and revise the design. |
| Feature entitlement unknown | Mark it optional pending current account confirmation. |
| Trust boundary crosses browser | Replace write access with a backend capability. |
| Rollback projection missing | Add a retained prior target or rebuild path. |

## Examples

Use this compact input and expected handoff to calibrate scope and evidence quality.

Input:

```text
scope=catalog-search; source=postgres; consumers=web,mobile; tenants=120
```

Expected handoff:

```text
projection=versioned; browser=secured-search; indexing=job-key; rollback=prior-index
```

## Resources

- [Skill-specific official documentation](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/algolia-reference-architecture/references/official-docs.md)
- [Sending and managing data](https://www.algolia.com/doc/guides/sending-and-managing-data)
- [API keys](https://www.algolia.com/doc/guides/security/api-keys)
- [Sending events](https://www.algolia.com/doc/guides/sending-events)
