The Claude Code Skill for localization
npx globalize-skills installs a Claude Code Skill that extracts hardcoded strings, generates locale files, and syncs translations on every Git push. No dashboard, no manual review.
Claude Code is an agentic coding tool that edits files autonomously. globalize.now integrates cleanly with that workflow: one command, the agent extracts strings and generates the locale files, Claude Code commits the changes. Every future Git push keeps translations in sync. No manual steps.
Prerequisites
- A project Claude Code has worked on (Next.js, React, Vue, or similar)
- A Git repository
- Node.js 18+
- Claude Code installed and authenticated
How to set up globalize.now with Claude Code
Open the Claude Code project directory
cd into the repository where Claude Code has been making edits so paths line up with the Git root.
Run the skills installer
From the project root, install Globalize skills so the agent can scaffold i18n and scan for literals.
npx globalize-skillsScan for hardcoded UI strings
Let globalize.now walk the tree to list user-visible English still embedded in components.
Confirm the proposed translation key structure
Review namespaces, naming, and pluralization hooks before refactors apply.
Apply refactors and locale files
Approve the work so components call your runtime helpers and JSON catalogs land in Git.
Commit with Claude Code and push
Let Claude Code stage the mergeable diff, commit, and push so future pushes continue automatic sync.
Common issues
Claude Code and globalize.now both want to edit components
Resolution: Run globalize.now first to establish keys and locale files; afterward Claude Code should touch translation entries instead of reintroducing raw literals everywhere.
How do I re-run extraction if Claude Code adds new strings?
Resolution: globalize.now runs automatically on every Git push, so new literals are detected without a manual re-run of the installer for each tweak.
Frequently asked questions
Does globalize.now work with Claude Code specifically?
Yes. globalize.now ships as agent skills and a CLI you run from the repo; Claude Code can execute the same commands and commit the resulting diffs. The integration is Git-native: once locale files exist, every push keeps translations aligned. You do not need a separate dashboard outside your editor and version control.
Do I need to configure Claude Code to know about globalize.now?
You only need to run npx globalize-skills so the skills are available to whichever agent is driving the session. There is no proprietary Claude Code plugin beyond that bootstrap step. After installation, prompt Claude Code using the same localization phrases you would use in any AI coding environment.
Can Claude Code and globalize.now share the same Git workflow?
They should share one repository history. globalize.now writes keys and locale JSON; Claude Code continues feature work on branches that already contain those files. Merge through pull requests as usual so reviewers see both product code and translation updates together. globalize.now then watches pushes to keep downstream locales fresh.
What happens when Claude Code generates new UI with hardcoded text?
The next Git push triggers globalize.now to diff new literals, propose keys, and update catalogs automatically. That prevents drift between English JSX and locale files. You still review PRs, but you are not manually exporting bundles or re-running one-off scripts for every feature branch.
Does globalize.now affect Claude Code's ability to edit the codebase?
No. After the initial extraction, Claude Code keeps full access to components; they simply reference translation helpers instead of raw strings. globalize.now does not lock files or require a different editor workflow. Both tools cooperate as long as commits flow through Git, which is already how Claude Code projects ship.
Which repositories benefit most from pairing Claude Code with globalize.now?
Any AI-edited JavaScript or TypeScript app where UI text still lives inline benefits most: agents ship screens quickly, and globalize.now converts that velocity into structured i18n without a big-bang rewrite. If you already store every string in locale files, you need fewer extractions, but most Claude Code prototypes still need the first pass globalize.now automates.
Try globalize.now with Claude Code
Start from your project root:
npx globalize-skills