How does globalize.now work?
Two paths. One outcome. Pick whichever describes your codebase today.
NO i18n YET
Full setup.
No translations wired up yet? We install everything, find your English text, and translate it. Then we keep new content in sync.
- Step 01
Install in your terminal
One command. Nothing in your codebase changes. It just gives your agent a playbook to read.
$npx globalize-skills - Step 02
Tell your agent to set up multilingual
In Cursor, Claude Code, or Codex. The agent detects your framework, installs the right translation library, and wires up every piece of English text in your UI.
Your promptSet up localization for my project - Step 03
Your text becomes translatable
Every piece of English text gets wired to a translation file. Spanish, German, Arabic. Whichever languages you need are ready to fill in.
- Step 04
Translations land on every push
Open a PR with new text? Translations land in the same PR before you merge. Push straight to main? We open a follow-up PR with translations. Either way, translations ship with your code, not behind it.
ALREADY HAVE i18n
Connect it.
If your repo already has next-intl, react-i18next, i18next, or @lingui, you only need three steps.
- Step 01
Install the CLI skill
npx globalize-skills installs the playbook your agent needs. No codebase changes.
$npx globalize-skills - Step 02
Ask your agent to connect
In Claude Code, Cursor, or Codex, tell the agent to set up the globalize project. The agent reads the installed skill and walks you through the GitHub connection.
Your promptSet up the globalize project for my repo - Step 03
Sync on every push
Every PR gets translations added before merge. Every push to main triggers a follow-up translation PR. No manual exports. No review queues.
Both paths end at the same loop: a PR you review, you merge. We never push to main directly. No manual exports, no review queues.
Was this helpful?