add-locale

Add interface locales and verify translation parity in webview internationalization systems.

75|21|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/yhk1038/claude-code-gui-jetbrains --skill add-locale-yhk1038
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-locale
Source: https://github.com/yhk1038/claude-code-gui-jetbrains/tree/main/.claude/skills/add-locale
Command: npx skills add https://github.com/yhk1038/claude-code-gui-jetbrains --skill add-locale-yhk1038

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps contributors add or extend UI languages without missing required translation files, registrations, or verification steps in the webview internationalization system.

Core Features & Use Cases

  • Locale Creation Guidance: Guides the creation of complete namespace-based translation catalogs that match the English source structure.
  • Locale Registration Support: Explains how to register new languages in the application settings and language mapping systems.
  • Translation Verification Workflow: Provides parity checks, type checks, tests, and UI validation steps for reliable localization contributions.

Quick Start

Use the add-locale skill to add a new interface language to the webview i18n system and verify that all translations match the existing locale structure.

Frequently Asked Questions about add-locale

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new UI language to a webview internationalization system?

Adding a new UI language requires creating namespace-based translation catalogs matching the English source structure, registering the language in application settings, and validating locale parity with automated checks.

What is locale parity in webview translation verification?

Locale parity in translation verification ensures new interface languages match the English source structure by validating matching translation keys, preserving placeholders, and running automated type checks and tests.

Does react-i18next require namespace catalogs for locale creation?

React-i18next locale creation requires building complete namespace-based translation catalogs that exactly match the existing English source structure to maintain translation consistency across the webview.

How do I register a new locale in application settings and language mapping?

Registering a new locale involves adding the language to application settings and language mapping systems, which integrates the new interface language into the webview internationalization configuration.

Why are my translation placeholders missing after adding a new locale?

Missing translation placeholders occur when new locale files fail to preserve the exact placeholders from the English source, an issue identified during the translation verification workflow's parity checks.