Agent skill · software engineering · jeremylongshore
lokalise-local-dev-loop
Configure Lokalise local development with file sync and hot reload.
Why this skill is useful
Adds executable scripts for Lokalise file synchronization and hot reloading that enhance the AI's capability to manage localization workflows.
What it needs
Requires git, lokalise2, 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 Local Dev Loop Overview Set up a complete local development workflow with Lokalise: project structure for i18n files, CLI push/pull commands, file watching for auto-upload, mock translations for offline development, framework integration (React i18next, Vue i18n), and a pre-commit hook to keep translations synced. Prerequisites Lokalise API token exported as LOKALISEAPITOKEN Lokalise project ID exported as LOKALISEPROJECTID Node.js 18+ with npm or pnpm lokalise2 CLI installed Git (for pre-commit hook) Instructions 1. Set up the project directory structure for i18n files, compatible with Lokalise's bundlestructure and most i18n frameworks. Barrel export with type safety (src/locales/index.ts): 1. Create CLI push/pull scripts for the upload-translate-download cycle. Push script (scripts/i18n-push.sh): Pull script (scripts/i18n-pull.sh): Package.json scripts: Typical workflow: 1. Set up watch mode to auto-upload source strings when en.json changes during development. Add to package.json: 1. Generate mock translations for offline development and layout testing. Use in development: 1. Integrate with React i18next (or skip to step 6 for Vue i18n). 1. Integrate with Vue i18n (alternative to step 5). 1. Add a pre-commit hook to prevent committing stale translations. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lokalise-local-dev-loop