algolia-multi-env-setup
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".
Best use case
algolia-multi-env-setup is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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".
Teams using algolia-multi-env-setup should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/algolia-multi-env-setup/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How algolia-multi-env-setup Compares
| Feature / Agent | algolia-multi-env-setup | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# 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)
```typescript
// 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.env.ALGOLIA_APP_ID!,
apiKey: process.env.ALGOLIA_ADMIN_KEY!,
searchKey: process.env.ALGOLIA_SEARCH_KEY!,
environment: env,
};
}
// Prefix index names with environment
export function indexName(base: string): string {
const { environment } = getConfig();
if (environment === 'production') return base; // No prefix in prod
return `${environment}_${base}`;
// development_products, staging_products, products
}
let _client: Algoliasearch | null = null;
export function getClient(): Algoliasearch {
if (!_client) {
const config = getConfig();
_client = algoliasearch(config.appId, config.apiKey);
}
return _client;
}
```
### Step 2: Scoped API Keys Per Environment
```typescript
import { algoliasearch } from 'algoliasearch';
const adminClient = algoliasearch(process.env.ALGOLIA_APP_ID!, process.env.ALGOLIA_ADMIN_KEY!);
// Create environment-scoped keys that can ONLY access their own indices
async function createEnvironmentKeys() {
// Staging key: can only access staging_* indices
const { key: stagingKey } = await adminClient.addApiKey({
apiKey: {
acl: ['search', 'addObject', 'deleteObject', 'editSettings', 'browse'],
description: 'Staging environment — full access to staging indices only',
indexes: ['staging_*'],
maxQueriesPerIPPerHour: 10000,
},
});
console.log(`Staging key: ${stagingKey}`);
// Dev key: can only access development_* indices
const { key: devKey } = await adminClient.addApiKey({
apiKey: {
acl: ['search', 'addObject', 'deleteObject', 'editSettings', 'browse'],
description: 'Development environment — full access to dev indices only',
indexes: ['development_*'],
maxQueriesPerIPPerHour: 5000,
},
});
console.log(`Dev key: ${devKey}`);
// Production search key: search only, restricted
const { key: prodSearchKey } = await adminClient.addApiKey({
apiKey: {
acl: ['search'],
description: 'Production search — read only',
indexes: ['products', 'articles', 'faq'],
maxQueriesPerIPPerHour: 50000,
maxHitsPerQuery: 100,
},
});
console.log(`Prod search key: ${prodSearchKey}`);
}
```
### Step 3: Environment Variables Per Platform
```bash
# .env.development
ALGOLIA_APP_ID=YourAppID
ALGOLIA_ADMIN_KEY=dev_scoped_key_here
ALGOLIA_SEARCH_KEY=dev_search_key_here
NODE_ENV=development
# .env.staging
ALGOLIA_APP_ID=YourAppID
ALGOLIA_ADMIN_KEY=staging_scoped_key_here
ALGOLIA_SEARCH_KEY=staging_search_key_here
NODE_ENV=staging
# Production: use secret manager, not env files
# GitHub Actions:
# ALGOLIA_ADMIN_KEY: ${{ secrets.ALGOLIA_ADMIN_KEY_PROD }}
# GCP Secret Manager:
# gcloud secrets versions access latest --secret=algolia-admin-key
# Vercel:
# vercel env add ALGOLIA_ADMIN_KEY production
```
### Step 4: Settings-as-Code with Environment Overrides
```typescript
// config/algolia-settings.ts
import type { IndexSettings } from 'algoliasearch';
const baseSettings: IndexSettings = {
searchableAttributes: ['name', 'brand', 'category', 'unordered(description)'],
attributesForFaceting: ['searchable(brand)', 'category', 'filterOnly(price)'],
customRanking: ['desc(review_count)', 'desc(rating)'],
};
const envOverrides: Partial<Record<string, Partial<IndexSettings>>> = {
development: {
// Faster iteration: no replicas in dev
replicas: [],
},
staging: {
// Mirror prod replicas for testing
replicas: ['virtual(staging_products_price_asc)'],
},
production: {
replicas: [
'virtual(products_price_asc)',
'virtual(products_price_desc)',
'virtual(products_newest)',
],
},
};
export function getSettings(env: string): IndexSettings {
return { ...baseSettings, ...envOverrides[env] };
}
```
### Step 5: Environment Isolation Guard
```typescript
// Prevent accidental cross-environment operations
export function guardEnvironment(operation: string, targetIndex: string) {
const env = process.env.NODE_ENV || 'development';
if (env === 'production') {
// In production, block access to dev/staging indices
if (targetIndex.startsWith('development_') || targetIndex.startsWith('staging_')) {
throw new Error(`Blocked: ${operation} on ${targetIndex} from production`);
}
} else {
// In dev/staging, block access to production indices (no prefix = production)
if (!targetIndex.startsWith(`${env}_`)) {
throw new Error(`Blocked: ${operation} on ${targetIndex} from ${env}. Use prefixed index.`);
}
}
}
// Usage in service layer
async function deleteIndex(name: string) {
guardEnvironment('deleteIndex', name);
await getClient().deleteIndex({ indexName: name });
}
```
### Step 6: Seed Script Per Environment
```typescript
// scripts/seed-environment.ts
import { getClient, indexName } from '../src/algolia/config';
import { getSettings } from '../config/algolia-settings';
async function seedEnvironment() {
const env = process.env.NODE_ENV || 'development';
const client = getClient();
const idx = indexName('products');
console.log(`Seeding ${env} environment → index: ${idx}`);
// Apply settings
await client.setSettings({ indexName: idx, indexSettings: getSettings(env) });
// Seed data (dev/staging only)
if (env !== 'production') {
const testData = await import('../fixtures/products.json');
const { taskID } = await client.replaceAllObjects({
indexName: idx,
objects: testData.default,
});
await client.waitForTask({ indexName: idx, taskID });
console.log(`Seeded ${testData.default.length} records`);
}
}
seedEnvironment().catch(console.error);
```
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Wrong index in production | Missing prefix logic | Use `indexName()` helper everywhere |
| Staging data leaking to prod | Shared API key | Use scoped keys restricted to index patterns |
| Settings drift between envs | Manual dashboard changes | Apply settings from code in CI |
| Dev index polluting record count | Old test indices | Scheduled cleanup job for `development_*` indices |
## Resources
- [API Key Index Restrictions](https://www.algolia.com/doc/guides/security/api-keys/in-depth/api-key-restrictions/)
- [Settings API](https://www.algolia.com/doc/api-reference/api-methods/set-settings/)
- [12-Factor App Config](https://12factor.net/config)
## Next Steps
For observability setup, see `algolia-observability`.Related Skills
windsurf-multi-env-setup
Configure Windsurf IDE and Cascade AI across team members and project environments. Use when onboarding teams to Windsurf, setting up per-project Cascade configuration, or managing Windsurf settings across development, staging, and production contexts. Trigger with phrases like "windsurf team setup", "windsurf environments", "windsurf multi-project", "windsurf team config", "cascade rules per env".
webflow-multi-env-setup
Configure Webflow across development, staging, and production environments with per-environment API tokens, site IDs, and secret management via Vault/AWS/GCP. Trigger with phrases like "webflow environments", "webflow staging", "webflow dev prod", "webflow environment setup", "webflow config by env".
vercel-multi-env-setup
Configure Vercel across development, preview, and production environments with scoped secrets. Use when setting up per-environment configuration, managing environment-specific variables, or implementing environment isolation on Vercel. Trigger with phrases like "vercel environments", "vercel staging", "vercel dev prod", "vercel environment setup", "vercel env scoping".
veeva-multi-env-setup
Veeva Vault multi env setup for enterprise operations. Use when implementing advanced Veeva Vault patterns. Trigger: "veeva multi env setup".
vastai-multi-env-setup
Configure Vast.ai GPU cloud across dev, staging, and production environments. Use when isolating GPU pools per team, managing API key separation by env, or implementing spending controls per deployment tier. Trigger with phrases like "vastai environments", "vastai staging", "vastai dev prod", "vastai multi-env".
supabase-multi-env-setup
Configure Supabase across development, staging, and production with separate projects, environment-specific secrets, and safe migration promotion. Use when setting up multi-environment deployments, isolating dev from prod data, configuring per-environment Supabase projects, or promoting migrations through environments. Trigger: "supabase environments", "supabase staging", "supabase dev prod", "supabase multi-project", "supabase env config", "database branching".
speak-multi-env-setup
Configure Speak across dev, staging, and production with separate API keys and mock modes. Use when implementing multi env setup, or managing Speak language learning platform operations. Trigger with phrases like "speak multi env setup", "speak multi env setup".
snowflake-multi-env-setup
Configure Snowflake across dev, staging, and production with account-level isolation, zero-copy clones, and environment-specific RBAC. Trigger with phrases like "snowflake environments", "snowflake staging", "snowflake dev prod", "snowflake clone", "snowflake environment setup".
windsurf-workspace-setup
Initialize Windsurf workspace with project-specific AI rules. Activate when users mention "create windsurfrules", "setup workspace", "configure project ai", "initialize windsurf workspace", or "migrate to windsurf". Handles workspace configuration and team standardization. Use when working with windsurf workspace setup functionality. Trigger with phrases like "windsurf workspace setup", "windsurf setup", "windsurf".
windsurf-multi-file-editing
Manage multi-file edits with Cascade coordination. Activate when users mention "multi-file edit", "edit multiple files", "cross-file changes", "refactor across files", or "batch modifications". Handles coordinated multi-file operations. Use when working with windsurf multi file editing functionality. Trigger with phrases like "windsurf multi file editing", "windsurf editing", "windsurf".
shopify-multi-env-setup
Configure Shopify apps across development, staging, and production environments with separate stores, API credentials, and app instances. Trigger with phrases like "shopify environments", "shopify staging", "shopify dev vs prod", "shopify multi-store", "shopify environment setup".
salesforce-multi-env-setup
Configure Salesforce across Developer, Sandbox, and Production environments with proper org management. Use when setting up multi-environment deployments, configuring per-environment credentials, or implementing sandbox-to-production promotion flows. Trigger with phrases like "salesforce environments", "salesforce sandbox", "salesforce dev prod", "salesforce org management", "salesforce sandbox types".