Agent skill · software engineering · jeremylongshore
lokalise-multi-env-setup
Configure Lokalise across development, staging, and production environments.
Why this skill is useful
Provides specific environment configuration patterns and API integration strategies for Lokalise that the AI wouldn't reliably generate on its own.
What it needs
Requires node installed locally. Requires lokalise account access. About 6k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Lokalise Multi-Environment Setup Overview Configure Lokalise for isolated development, staging, and production environments. Two strategies are covered: separate Lokalise projects per environment (strongest isolation) and Lokalise branching within a single project (simpler management). Both approaches include secret management, environment-aware configuration, and a promotion workflow that moves translations through the pipeline from dev to production without cross-contamination. Prerequisites Lokalise Team or Enterprise plan (branching requires Team plan or higher) One Lokalise API token per environment, each scoped to minimum required permissions Secret management system: GitHub Secrets, AWS Secrets Manager, GCP Secret Manager, or HashiCorp Vault Node.js 18+ with @lokalise/node-api SDK installed Environment variable NODEENV (or equivalent) set in each deployment target Instructions Step 1: Choose Your Strategy Option A — Separate projects per environment (recommended for teams > 5 translators or strict compliance): Environment Lokalise Project Purpose ------------- ----------------- --------- Development MyApp (Dev) Rapid iteration, machine translations OK Staging MyApp (Staging) QA review, translator proofing Production MyApp (Prod) Approved translations only Option B — Single project with Lokalise branching (simpler for small teams): Branch Purpose -------- --------- main Production translations staging QA translations under review dev Work-in-progress translations Step 2: Environment-Aware Configuration Create a configuration module that selects the correct Lokalise project and credentials based on the runtime environment: Step 3: Secret Management Store API tokens securely in each environment. Never commit tokens to source control. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lokalise-multi-env-setup--892a06