skills.rest
massCodeIO
massCodeIOOFFICIAL
Explore all skills by this author →
WebsiteGitHub

i18n

Manage translation keys across en_US and ru_RU locales in massCode.

6.9k|262|Updated Mar 29, 2022
Search Tags:#localization#pnpm#i18n#translations#locales#en_US#ru_RU
One-click install
npx skills add https://github.com/massCodeIO/massCode --skill i18n-masscodeio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: i18n
Source: https://github.com/massCodeIO/massCode/tree/main/.agents/skills/i18n
Command: npx skills add https://github.com/massCodeIO/massCode --skill i18n-masscodeio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

massCode's localization system requires structured workflows to add and sync translation keys across locales, preventing divergent translations and missing keys.

Core Features & Use Cases

  • Centralized management of translation keys across en_US and ru_RU
  • Automatic syncing and propagation of new keys to all locales
  • Guidance on adding and wiring text through the i18n system for UI strings

Quick Start

Add a new key to en_US and run pnpm i18n:copy to propagate translations to ru_RU and other locales.

Frequently Asked Questions about i18n

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

FAQPage Schema
How do I add new translation keys for en_US and ru_RU locales?▼

To add new translation keys, insert the new strings into the en_US locale file first, then run pnpm i18n:copy to automatically synchronize and propagate those keys to ru_RU and other locales.

What is the best way to keep localization files from diverging when updating UI strings?▼

Maintaining en_US as the source of truth and updating ru_RU in tandem prevents divergent translations. Running pnpm i18n:copy synchronizes locales, ensuring no translation keys are missing across files.

Do I need pnpm to synchronize translations across locales?▼

Yes, pnpm is required to execute the i18n:copy script. This command handles the automatic syncing and propagation of new translation keys from the en_US source locale to ru_RU.

How does the i18n system handle missing translation keys?▼

The i18n system prevents missing keys by enforcing a structured workflow where en_US acts as the source of truth. The pnpm i18n:copy command automatically propagates any added keys to ru_RU.

Can I update ru_RU translations without modifying en_US first?▼

No, en_US must be maintained as the source of truth for localization. You must update en_US first, then run pnpm i18n:copy to sync the changes to ru_RU, ensuring structured translation workflows.

Why are my ru_RU translations missing new UI strings after adding them?▼

Missing ru_RU translations occur when locales are not synchronized. After adding new strings to en_US, you must run pnpm i18n:copy to propagate the translation keys and prevent missing keys.

Related Skills

Explore More Software Engineering Skills→
cosmixcosmix
53

i18n

Implement internationalization with locale-aware formatting, pluralization, and RTL support.

Community
Intermediate
Nick777-PixelNick777-Pixel

i18n

Manage localized text in React apps using react-i18next and pnpm i18n.

Community
Intermediate
Jason-hub-starJason-hub-star

i18n-string-add

Add bilingual UI strings to Next.js i18n JSON files.

Community
Intermediate
wanghaishengwanghaisheng

1k-i18n

Manage locale keys and translations for react-intl and ETranslations workflows.

Community
Intermediate