Agent skill · software engineering · jeremylongshore
lokalise-reference-architecture
Implement Lokalise reference architecture with best-practice project
Why this skill is useful
Provides a detailed project structure and integration patterns for Lokalise that the AI wouldn't reliably generate on its own.
What it needs
Requires @lokalise/node-api, node installed locally. About 8k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Lokalise Reference Architecture Overview A production-ready architecture for integrating Lokalise into web applications. Covers the end-to-end translation flow from source code through CI/CD and Lokalise to deployed translations, recommended project structure for i18n, file organization conventions, multi-app translation sharing, and the tradeoffs between OTA (over-the-air) and build-time translation loading. Prerequisites Node.js 18+ with TypeScript @lokalise/node-api SDK installed (npm install @lokalise/node-api) An i18n framework selected (i18next, react-intl, vue-i18n, or equivalent) Lokalise project created with at least one source language configured Basic understanding of CI/CD pipelines (GitHub Actions, GitLab CI, or equivalent) Instructions Step 1: Architecture Diagram The translation lifecycle follows this flow: Two delivery paths: 1. Build-time (solid arrows): Translations downloaded during CI build, bundled into the application. Changes require a new deployment. 2. OTA (dashed arrow): Translations fetched from Lokalise CDN at runtime. Changes appear without redeployment. Adds a network dependency. Step 2: Project Structure for i18n Organize your codebase to separate translation concerns from business logic: Step 3: Core Configuration Step 4: Lokalise API Client Wrapper Step 5: File Organization Conventions Follow these conventions for translation file organization: Flat keys (recommended for most projects — simpler grep, no nesting ambiguity): Nested keys work better for large projects with clear module boundaries, where each top-level key maps to a feature area. Both formats are supported by Lokalise and i18next. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lokalise-reference-architecture--bbe056