Algolia UI Libraries

Use this skill to choose the right current Algolia UI library and docs path. Do not treat this skill as a frozen API reference or package-version source.

Customer-Facing Standard

• Verify current public docs before recommending package names, imports, SSR patterns, routing, or upgrade steps.
• Choose the library from the customer journey and framework, not from generic preference.
• Use public academy.algolia.com for learning alignment and public algolia.com/doc for current implementation guidance when source-backed context is needed.
• When an Academy metadata reference pack is available, use only its title, url, course, module, learning_objectives, and updated_at fields for structure. If it is stale or no match exists, fall back to live Academy/docs lookup. Do not treat cached metadata as course content or implementation authority.
• Do not require custom Academy/docs access; use customer-provided sources only as optional context.
• When live Algolia data, analytics, index inspection, settings changes, or account actions are needed, use Algolia MCP, the Algolia CLI, or official Algolia skills for the live operation, then apply this skill to interpret results and validate the customer-ready implementation path.
• Route to InstantSearch, Autocomplete, Events, or Release QA when implementation depth is needed.

Official Companion Skills

• Use official instantsearch for production implementation, source-of-truth checks, framework-specific rules, and code-level InstantSearch or Autocomplete work.
• Use this skill before the official implementation step to choose the right current UI path and after implementation to validate routing, SSR, events, and upgrade assumptions.