algolia-multi-env-setup

name	algolia-multi-env-setup
description	Configure Algolia across dev/staging/production: index prefixing, per-environment API keys, settings-as-code, and environment isolation guards. Trigger: "algolia environments", "algolia staging", "algolia dev prod", "algolia environment setup", "algolia config by env".
allowed-tools	Read, Write, Edit, Bash(npm:*), Bash(gcloud:*), Bash(vault:*)
version	1.0.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","search","algolia"]
compatible-with	claude-code

Algolia Multi-Environment Setup

Overview

Algolia doesn't have built-in environment separation. You either use separate Algolia applications (strongest isolation) or index prefixing within one application (simpler). This skill covers both approaches.

Environment Strategies

Strategy	Isolation	Cost	Complexity
Index prefixing	Shared app, prefixed names	Lowest	Low
Separate API keys	Shared app, scoped keys	Low	Medium
Separate applications	Full isolation	Highest	High

Instructions

Step 1: Index Prefixing (Recommended for Most Teams)

// src/algolia/config.ts
import { algoliasearch, type Algoliasearch } from 'algoliasearch';

type Environment = 'development' | 'staging' | 'production';

interface AlgoliaConfig {
  appId: string;
  apiKey: string;
  searchKey: string;
  environment: Environment;
}

function getConfig(): AlgoliaConfig {
  const env = (process.env.NODE_ENV || 'development') as Environment;

  return {
    appId: process..!,
    : process..!,
    : process..!,
    : env,
  };
}


  ():  {
   { environment } = ();
   (environment === )  base;  
   ;
  
}

 :  |  = ;

  ():  {
   (!_client) {
     config = ();
    _client = (config., config.);
  }
   _client;
}