Skills Internationalizing Websites

🌍

Internationalizing Websites

Name: Internationalizing Websites
Author: ZhanlinCui

Low Risk ⚙️ External commands🌐 Network access📁 Filesystem access⚡ Contains scripts

Add Multi-Language Support to Next.js

This skill automates adding multi-language support to Next.js websites, including hreflang tags, locale configuration, translation files, and SEO optimization for international markets.

Supports: Claude Codex Code(CC)

📊 70 Adequate

Download the skill ZIP

Upload in Claude

Go to Settings → Capabilities → Skills → Upload skill

Toggle on and start using

Test it

Using "Internationalizing Websites". Add Japanese language support to our Next.js site

Expected outcome:

Created i18n/messages/ja.json from English template. Updated i18n/locale.ts with ja locale and 日本語 display name. Configured zh-CN to zh mapping in i18n/request.ts. Added hreflang tags for Japanese pages in reference guide.

Using "Internationalizing Websites". Set up hreflang for English, German, and French

Expected outcome:

Generated hreflang implementation guide with x-default to English. Created language alternate tags for de-DE and fr-FR regional variants. Updated sitemap.xml structure for multi-language URLs.

Security Audit

Low Risk

v1 • 2/24/2026

Static scanner produced many false positives due to markdown documentation being misinterpreted. The skill contains legitimate i18n automation scripts that modify translation files and configuration - this is expected behavior for an internationalization tool. All detected patterns in markdown files are documentation content (code blocks, links, technical terms), not executable code. The JavaScript scripts perform standard file operations for adding language support.

Files scanned

3,244

Lines analyzed

findings

Total audits

Medium Risk Issues (1)

scripts/i18n-add-languages.mjs:1-403 scripts/i18n-add-schema.js:1-607

Script File Operations

The skill includes JavaScript scripts that perform file system operations (copy translation files, update configuration). This is expected behavior for an i18n automation skill - the scripts copy en.json templates to create new language files and update locale configurations.

Low Risk Issues (2)

SKILL.md:33-260 WORKFLOW.md:1-633

Markdown Code Blocks Flagged

Static scanner incorrectly flagged markdown code block syntax (backticks) as shell command execution. The backticks are used for markdown code formatting in documentation files.

reference/hreflang-guide.md:26-436

Documentation URLs Flagged

Static scanner flagged markdown hyperlinks as 'hardcoded URLs'. These are documentation links, not actual network requests made by any code.

Risk Factors

⚙️ External commands (5)

reference/hreflang-guide.md:15-17 reference/locale-codes.md:13-15 reference/seo-checklist.md:10-12 SKILL.md:33-41 WORKFLOW.md:8-11

🌐 Network access (4)

reference/hreflang-guide.md:26-36 reference/locale-codes.md:148-152 SKILL.md:147-149 WORKFLOW.md:236-241

📁 Filesystem access (3)

scripts/i18n-add-languages.mjs:60 scripts/i18n-add-languages.mjs:108 scripts/i18n-add-schema.js:571

⚡ Contains scripts (1)

scripts/i18n-add-languages.mjs:134

Audited by: claude

Quality Score

Architecture

100

Maintainability

Content

Community

Security

Spec Compliance

What You Can Build

Expanding to Japanese Market

Developer wants to add Japanese language support to their Next.js website for SEO in Japan. The skill sets up ja.json translation files, configures locale settings, and generates hreflang tags.

Setting Up Multi-Language SEO

SEO specialist needs proper hreflang implementation across English, German, and French versions to avoid duplicate content penalties and improve regional search rankings.

Building Translation Infrastructure

Development team preparing for translation workflow by setting up i18n file structure, locale configuration, and automated file generation scripts.

Try These Prompts

Add Basic Language Support

Use the Internationalizing Websites skill to add Japanese (ja) language support to our Next.js website. We have English translation files in i18n/messages/en.json that should be used as templates.

Configure Multi-Language SEO

Use the Internationalizing Websites skill to set up hreflang tags and SEO configuration for English, German (de), and French (fr) versions of our website. Make sure search engines can properly index each language version.

Expand to Multiple Asian Languages

Use the Internationalizing Websites skill to add support for Japanese (ja), Chinese (zh), Korean (ko), and Vietnamese (vi) to our Next.js application. Configure proper locale codes including zh-hk for Traditional Chinese.

Complete i18n Workflow

Follow the complete Internationalizing Websites workflow to add Spanish (es) and Portuguese (pt) support. Include setting up translation files, configuring locale.ts, updating request.ts language mappings, and generating the sitemap with new language URLs.

Best Practices

Always start with complete English translation files as templates before adding new languages
Use proper locale codes (en, ja, zh-CN) and configure regional variants (zh-HK, zh-TW) separately
Run the i18n-add-languages.mjs script after adding new language files to auto-update configurations
Verify hreflang tags render correctly and test with Google Rich Results Test tool

Avoid

Do not skip the configuration verification step - always check locale.ts and request.ts after running scripts
Avoid adding languages without having translation content ready - the skill creates file structure, not translations
Do not forget to update sitemap.xml with new language URLs for proper search engine indexing

Frequently Asked Questions

What languages does this skill support?

The skill supports all common languages including Japanese (ja), Chinese (zh, zh-hk), Korean (ko), Arabic (ar), Vietnamese (vi), and all European languages (en, de, es, fr, it, pt, ru).

Do I need translation files already?

Yes, you need English (en) translation files as templates. The skill copies these to create new language files, but does not provide actual translations - those must be added manually or via translation services.

Does this automatically translate my content?

No, this skill sets up the i18n infrastructure (files, configuration, SEO tags). Translation of actual content must be done separately using translation tools or services.

How do hreflang tags help SEO?

Hreflang tags tell search engines which language/region a page is for, preventing duplicate content penalties and helping your page rank in local search results for each target market.

Can this work with Next.js App Router?

The skill is designed for Next.js i18n folder structure with locale configuration. Some manual adjustment may be needed for App Router projects depending on your routing setup.

What files does the script modify?

The i18n-add-languages.mjs script modifies: translation files in i18n/messages and i18n/pages, locale.ts configuration, request.ts language mappings, and public/sitemap.xml.