Agent skill · software engineering · jeremylongshore
algolia-reference-architecture
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".
Why this skill is useful
Provides specific patterns and scripts for implementing Algolia architecture that the AI wouldn't reliably generate on its own.
What it needs
Requires algolia-sdk installed locally. Requires algolia account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/algolia-reference-architecture