skills.rest
gerald-ica
gerald-icaCOMMUNITY
Explore all skills by this author →
GitHub

i18n

Validate i18n consistency across locale files and translation modules.

Updated Apr 14, 2026
Search Tags:#workflow#consistency#localization#i18n#translations#multilingual#locales
One-click install
npx skills add https://github.com/gerald-ica/opencode-config-snapshot --skill i18n-gerald-ica
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: i18n
Source: https://github.com/gerald-ica/opencode-config-snapshot/tree/main/opencode/skills/i18n
Command: npx skills add https://github.com/gerald-ica/opencode-config-snapshot --skill i18n-gerald-ica

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Internationalization workflow and standards for managing translations. Use when: (1) Adding new user-facing text, (2) Creating new components with user-facing text, (3) Reviewing code for i18n compliance, (4) Adding a new translation module.

Core Features & Use Cases

  • Defines a single source of truth in src/common/config/i18n-config.json for languages and modules.
  • Structures locale files under src/renderer/i18n/locales and uses namespaced keys like t('module.key').
  • Provides guidelines for adding new translations, modules, and validating consistency across all locales.

Quick Start

Use the pdf skill to extract all text from the attached file 'invoice-q3.pdf'.

Frequently Asked Questions about i18n

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

FAQPage Schema
How do I ensure consistent translations across multiple locale files in a multilingual project?▼

To ensure consistent translations, structure locale files under dedicated directories and use namespaced keys like t('module.key') to maintain a single source of truth for all modules.

What is the best way to add a new translation module for user-facing text?▼

Adding a new translation module requires defining it in a central i18n-config.json file, structuring the new locale files, and applying namespaced keys to validate consistency across all configured languages.

How do I review code for internationalization compliance when adding new UI text?▼

Reviewing code for i18n compliance involves checking that all new user-facing text uses structured locale files and namespaced translation keys instead of hardcoded strings, ensuring end-to-end correctness.

Do I need a specific configuration file to manage internationalization workflows?▼

Yes, internationalization workflows require reading a central configuration file, typically named i18n-config.json, to define available languages, modules, and conventions for the entire codebase.

When should I implement locale-wide validation for my application's UI text?▼

Implement locale-wide validation when adding new user-facing text or components, ensuring structured translations remain consistent and correct across all configured languages and modules.

Related Skills

Explore More Content & Communication Skills→
HankanmanHankanman
1

nextjs-intl-translation-structure-consistency

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

Community
Intermediate
Dinhpham04Dinhpham04

translate-japanese-ui

Detect Japanese UI strings in source code and replace them with translation keys.

Community
Intermediate
Fr-e-dFr-e-d
157

i18n-extract

Scan React/TypeScript codebases to extract hardcoded user-facing strings.

Community
Intermediate
danilomartinellidanilomartinelli
1

i18n-localization

Detect hardcoded strings and manage translation files for software applications.

Community
Intermediate