internationalization
Plan and run a multi-language or multi-region site. Use this skill when adding new locales, choosing URL structure for languages (subfolders vs subdomains vs ccTLDs), implementing hreflang, planning translation workflow, handling currency and date formats, designing for RTL languages, or auditing a stalled internationalization rollout. Triggers on internationalization, i18n, localization, l10n, hreflang, multi-language, translation workflow, RTL, locale, ccTLD, subfolder vs subdomain, language switcher. Also triggers when international audiences underperform or translations are stale.
Profile →npx skills add rampstackco/claude-skills --skill internationalization --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Internationalization Add languages and regions in a way that works for users, search engines, and the team maintaining the content. Stack-agnostic. --- ## When to use - Adding the first non-English (or non-default) language - Adding additional locales to an existing internationalized site - Choosing URL structure for languages - Implementing hreflang tags - Designing translation workflow - Handling currency, date, time, and number formats - Designing or fixing layout for RTL languages - Auditing an internationalization rollout that's underperforming ## When NOT to use - Single-language site (use other skills) - Domain strategy that's not language-driven (use `domain-strategy`) - Content strategy independent of locale (use `content-strategy`) - Marketing copy production (use `content-and-copy`) --- ## Required inputs - The locales in scope (language + region, e.g., `en-US`, `de-DE`, `fr-CA`) - Business reason per locale (priority, audience size) - Existing site architecture - Translation resources (in-house, agency, AI-assisted, community) - Content volume and update frequency --- ## The framework: 5 layers Internationalization touches everything. Five layers, each with their own
- When to use
- When NOT to use
- Required inputs
- The framework: 5 layers
- Layer 1: URL structure
- Layer 2: Content structure
- Layer 3: hreflang and canonicals
- Layer 4: Translation workflow
- Layer 5: Locale-aware UX
- Workflow
- Step 1: Decide which locales
- Step 2: Pick URL structure
- Step 3: Pick content structure
- Step 4: Set up hreflang and canonicals
What does the internationalization skill do?
Plan and run a multi-language or multi-region site. Use this skill when adding new locales, choosing URL structure for languages (subfolders vs subdomains vs ccTLDs), implementing hreflang, planning translation workflow, handling currency and date formats, designing for RTL languages, or auditing a stalled internationalization rollout. Triggers on internationalization, i18n, localization, l10n, hreflang, multi-language, translation workflow, RTL, locale, ccTLD, subfolder vs subdomain, language switcher. Also triggers when international audiences underperform or translations are stale.
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill internationalization --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.