Using globalize.now with Cursor
Extract strings and generate locale files from Cursor-built apps with one command.
Cursor generates working UI fast, but typically hardcodes English directly in JSX. globalize.now extracts those hardcoded strings, generates translation keys, and creates locale files — turning a Cursor-built app into a translation-ready codebase. The setup takes one command and syncs on every Git push afterward.
Prerequisites
- A project built with Cursor
- A Git repository
- Node.js 18+
- Any JavaScript i18n library installed (i18next, next-intl, and similar), or none if you are starting fresh
How to set up globalize.now with Cursor
Open your Cursor project and confirm Git
Open the repository in Cursor and make sure your codebase is committed and pushed to a Git remote so later pushes can trigger sync.
Run the skills installer in the project root
In a terminal at the repository root, install the Globalize agent skills so your assistant can scaffold i18n and scan the tree.
npx globalize-skillsLet the agent analyze the codebase
Follow the agent prompts so it can locate hardcoded user-visible strings across your components and routes.
Review the proposed translation key layout
Inspect the suggested key structure and naming before any refactors land in your branch.
Confirm extraction and locale files
Approve the changes so keys are generated, components call your runtime i18n API instead of literals, and locale files are written into the repo.
Commit and push
Commit the changes and push to your default branch so globalize.now can keep new strings aligned on future Git pushes.
Common issues
Cursor keeps adding new hardcoded strings
Resolution: globalize.now runs on every Git push, so new literals are picked up automatically instead of accumulating silently between releases.
Translation keys conflict with an existing i18n setup
Resolution: globalize.now detects existing i18n libraries and follows their conventions so new keys extend your current catalog instead of fighting it.
Frequently asked questions
Does globalize.now work with any Cursor-generated project?
Yes, as long as the stack is one globalize.now supports through its agent skills (modern JavaScript frameworks such as Next.js, React, or Vue). globalize.now focuses on extracting hardcoded UI strings and producing keys plus locale files, not on which editor produced the JSX. You still run npx globalize-skills from the project root and follow the guided prompts so the agent can scan the repo and open mergeable diffs.
Do I need to configure globalize.now to detect Cursor-specific patterns?
No separate Cursor integration is required. globalize.now analyzes the repository the same way regardless of whether files were authored manually or by Cursor. The skills look for user-visible literals and routing structure, then propose keys that match the i18n library you adopt. You review the plan in Git like any other change.
Can I use globalize.now on a Cursor project that already has partial i18n?
Yes. The tooling is designed to extend existing catalogs when keys and locale files are already present. globalize.now detects the runtime library you use and proposes additions instead of discarding prior work, so you can finish migrating literals incrementally. Keep using Git pushes so new UI stays covered.
What i18n libraries does globalize.now output work with in a Cursor project?
globalize.now is library-agnostic: it produces structured keys and locale files that pair with common runtimes such as i18next, next-intl, react-intl, Lingui, and vue-i18n. Your Cursor project keeps whichever stack you choose; globalize.now supplies the extraction and sync layer. The agent skills help wire the provider or middleware your framework expects.
Does globalize.now change my Cursor-generated components?
globalize.now rewrites call sites so literals flow through your i18n API (for example t() or message components) while preserving behavior. You review diffs in Git before merging, just like any Cursor-generated change. After the first merge, future pushes continue to sync new strings automatically without a separate export step.
Where do I run globalize.now inside Cursor?
Always run npx globalize-skills from the repository root in Cursor’s integrated terminal (or any shell pointed at that root). The skills scope to the current project, install the localization skill bundle, and hand control back to your agent for the follow-up prompts. Staying at the root keeps path detection aligned with how the CLI scans the tree.
Try globalize.now with Cursor
Start from your project root:
npx globalize-skills