globalize.now makes your app multilingual in three steps.
Already have i18n set up? If your codebase already has locale files and an i18n library configured, the agent detects that and connects your existing setup to auto-translate on push instead of rebuilding anything. See "I already have i18n. What does globalize.now do?"
Free to start. Setup is free. You get a €5 translation credit when you sign up, enough to translate a small-to-medium app across multiple languages before you need to add billing.
Step 1 — Install the skills
Run one command in your terminal from your project root:
npx skills add --all globalize-now/globalize-skills
This installs the globalize.now skills into your AI coding agent. It auto-detects your agent (Claude Code, Cursor, Codex, and others). To target one explicitly, add -a, for example -a claude-code, -a cursor, or -a codex.
The skills are a localization playbook your agent reads. Nothing in your codebase changes yet.
Step 2 — Ask your agent to set it up
Use a strong model for this step. Claude Opus handles messy, vibe-coded codebases reliably. Smaller models tend to miss strings or generate inconsistent key names.
Open your agent and ask it to set up localization:
Set up i18n for my project
The globalize-guide skill takes over. It inspects your stack, recommends a library (Lingui for React and Vite, next-intl for Next.js App Router), and shows you a short plan before it changes a single file. You review the plan and give the go-ahead. Then it installs the library, wraps your hardcoded strings in translation keys, and generates locale files for the languages you chose.
It runs in stages with progress you can follow, and it resumes where it left off if a session is interrupted. A small-to-medium app takes roughly 30 minutes. Don't cancel mid-run.
Step 3 — Connect your repo for translation
Ask your agent to connect the project:
Connect globalize.now to my repo
The globalize-now-cli-setup skill installs the Globalize CLI, signs you in, creates your translation project, and connects your GitHub or GitLab repo. From this point on, every time you push new code, globalize.now detects new strings, translates them, and opens a pull request with updated locale files. You review and merge. No other manual steps, ever.
What you get at the end
-
All UI strings extracted and translated into your chosen languages
-
Locale files committed to your repo (you own the files, no vendor lock-in)
-
A language switcher in your app
-
Automatic sync on every future push
Verify it worked
After setup, confirm the output looks right before you call it done. See the verify setup article.
Where to go next
-
Before you start — what to expect
-
What does globalize.now actually do to your code?
-
What project types and frameworks are supported?