If your codebase already has next-intl, react-i18next, i18next, or @lingui/* wired up, globalize.now skips the setup scaffold and goes straight to sync mode. No language switcher injection. No locale file restructure. No destructive changes.
The short version: install the skills, ask your agent to connect the project, and on every push to main globalize.now diffs your source-language file against the other locales. New keys get translated. A PR lands with updated locale files. You review and merge.
How it runs
- Install the skills:
npx skills add globalize-now/globalize-skills
- Ask your agent to connect:
Connect globalize.now to my repo
The i18n-guide skill inspects your repo first. When it sees an existing i18n setup, it proposes connect-only (sync) mode and shows you the plan before doing anything. You confirm, and the globalize-now-cli-setup skill connects your GitHub or GitLab repo. Your existing locale structure is read, not rewritten.
This is auto-detected from signals in your repo (an i18n library in package.json, a messages/ or locales/ folder, an existing source-locale file). If at least two are present, you're treated as already-internationalized.
If the agent's plan looks like a full from-scratch setup instead of connect-only, don't approve it. Tell it the project already has i18n, and it switches to sync mode. See the article below.
Where to go next
- Detection signals + what we skip — the full list of dependencies and folders we read, and exactly what we don't touch in sync mode.
- The setup plan looks bigger than expected — what to do if the agent proposes a full setup on an already-internationalized repo.
- How globalize.now fits into your stack — globalize.now plus your i18n library, who does what.