skills.rest
gaogg521
gaogg521COMMUNITY
Explore all skills by this author →
GitHub

i18n

Enforce i18n compliance across locales using i18n-config.json.

33|6|Updated Apr 8, 2026
Search Tags:#workflow#localization#translation#config#i18n#internationalization#locales
One-click install
npx skills add https://github.com/gaogg521/1ONE-ClaudeCode --skill i18n-gaogg521
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: i18n
Source: https://github.com/gaogg521/1ONE-ClaudeCode/tree/main/.claude/skills/i18n
Command: npx skills add https://github.com/gaogg521/1ONE-ClaudeCode --skill i18n-gaogg521

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Internationalization (i18n) workflow and standards for managing translations helps keep user-facing text consistent across languages and modules, reducing duplication and errors.

Core Features & Use Cases

  • Centralized source of truth for languages and modules via i18n-config.json
  • Uniform key usage and automated propagation of translations across locales
  • Workflow for adding new text, validating locales, and regenerating type definitions

Quick Start

Read the i18n-config.json to understand current languages and modules, then add and propagate a new translation key across all locales and regenerate type definitions.

Frequently Asked Questions about i18n

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

FAQPage Schema
How do I standardize internationalization across my software project?▼

To standardize internationalization, this Skill enforces all user-visible text to use i18n by reading the i18n-config.json source of truth and propagating translation keys across every defined locale.

What's the best way to automate adding new UI text translations across all locales?▼

Automate adding new UI text by defining the translation key once, then the workflow propagates it across all locales defined in i18n-config.json and regenerates type definitions via i18n:types validation.

How do I validate code for i18n compliance and ensure all text is translated?▼

Validate i18n compliance by reviewing code against the i18n-config.json configuration to ensure all user-facing text uses i18n, then regenerate type definitions and validate locales to catch missing translations.

Do I need a centralized config file to manage app-wide internationalization?▼

Yes, a centralized config file is required; the workflow uses src/common/config/i18n-config.json as the single source of truth for languages and modules to ensure consistent localization.

When do I need to regenerate type definitions for my translation workflow?▼

Regenerate type definitions whenever you add new UI text or introduce new components, ensuring the i18n:types command updates the schema and validates locales against the i18n-config.json.

Related Skills

Explore More Software Engineering Skills→
HankanmanHankanman
1

nextjs-intl-translation-structure-consistency

Validate translation-key structures across Next.js locale JSON files.

Community
Intermediate
liwooliwoo
16

inertia-form-review

Audit Inertia.js forms for i18n compliance, typing, and create/edit parity.

Community
Advanced
tarrragontarrragon
1

style-guardian

Detect hardcoded UI styles and text in Flutter/Dart projects.

Community
Basic
AstrumonAstrumon

commit

Create standardized Git commits with validated type: description messages.

Community
Intermediate