skills.rest
jammindev
jammindevOFFICIAL
Explore all skills by this author →
GitHub

translate

Add or update i18next translation keys across four locale JSON files.

Updated Sep 21, 2025
Search Tags:#react#localization#translation#json#multilingual#i18next
One-click install
npx skills add https://github.com/jammindev/house --skill translate-jammindev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: translate
Source: https://github.com/jammindev/house/tree/main/.claude/skills/translate
Command: npx skills add https://github.com/jammindev/house --skill translate-jammindev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain consistent UI translations across the project whenever new interface text is added or existing translation keys are missing.

Core Features & Use Cases

  • Multilingual key management: Add or update i18next keys in English, French, German, and Spanish at the same time.
  • Namespace-aware updates: Place new strings in the correct translation namespace by checking the source of truth in the English locale file.
  • Project consistency: Keep the four locale files aligned so the UI does not fall back to missing or mismatched strings.
  • Use Case: A developer adds a new modal or button label and needs matching translations everywhere before shipping.

Quick Start

Add or update the missing translation keys for this new UI feature in all four locale files and keep the JSON structure valid.

Frequently Asked Questions about translate

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

FAQPage Schema
How do I add i18next translation keys across multiple locale files at once?▼

To add i18next translation keys across multiple locale files, define the new strings in your English source of truth and apply synchronized updates to the French, German, and Spanish JSON files to keep the structure valid.

How do I fix missing translation strings in a multilingual React application?▼

Fix missing translation strings by identifying the absent i18next keys in your English locale file, then applying synchronized updates across the French, German, and Spanish JSON files to prevent UI fallback errors.

Does this approach handle i18next namespace placement for feature-specific copy?▼

Yes, namespace placement is handled by checking the English locale file as the source of truth to correctly place new strings in shared or feature-specific translation namespaces within the JSON structure.

Can I update React localization JSON files with interpolation and pluralization patterns?▼

You can update React localization JSON files by applying valid interpolation and pluralization patterns to the i18next translation keys simultaneously across the English, French, German, and Spanish locale files.

What is the best way to keep four locale files aligned when adding new UI text?▼

The best way to keep four locale files aligned is to apply synchronized edits to the English, French, German, and Spanish translation JSON files whenever new interface text or buttons are added to the React application.

Related Skills

Explore More Software Engineering Skills→
lobehublobehub
81.4k

i18n

Manage react-i18next translations and locale data in React applications.

Official
Intermediate
capaas2capaas2

i18n-localization

Detect hardcoded user-facing strings and missing translation keys in React, Vue, and Python projects.

Community
Intermediate
learningmatter-mitlearningmatter-mit
144

general-property-units

Define ASE-standard energy, force, and stress units across MLIP and DFT toolchains.

Official
Basic
daffy0208daffy0208
34

localization-engineer

Implement i18n for Next.js apps with next-intl and JSON catalogs.

Community
Intermediate