How does globalize.now work?
One command. Your agent handles the rest.
npx globalize-skills detects your stack, picks the right preset, and installs the skills your agent needs — Cursor, Claude Code, or Codex. No decisions to make.
It reads your stack before it touches your code.
Globalize detects your framework, picks the best i18n library for it (next-intl, lingui, react-intl), and counts every hardcoded string — scoped to components your users actually see.
Next.js 15 with App Router. I'll set up next-intl — best fit for your stack.Found 47 hardcoded strings across 12 components.
Which languages do you need?
Keys, locale files, and 50+ languages — generated.
Every string becomes a translation key. Every key gets a glossary entry. Every locale file is written in the format your framework expects — including RTL for Arabic and Hebrew.
✓
es.json — 47 translatable strings✓
ar.json — 47 translatable stringsAll entries consistent with your glossary.
New copy? Translated before the PR merges.
Connect your repo once. Every push triggers a diff, new strings get translated, and a pull request lands with locale files updated. No review queues. No dashboards to babysit.
globalize-now-website on globalize.✓ Connected GitHub repo
✓ 3 locales configured (en, es, ar)
✓ Auto-translate on push enabled
New strings translated automatically on push to main.