i18n

Name: i18n
Availability: InStock
Author: mateo

Automate React i18n tasks by extracting hardcoded strings and replacing them with translation keys.

Updated Feb 14, 2026

Search Tags:#automation #i18n #translations #lint #i18next #locales #react-i18next

Ready to run

npx skills add https://github.com/mateo19182/i18n-skill --skill i18n-mateo19182

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: i18n
Source: https://github.com/mateo19182/i18n-skill/tree/main
Command: npx skills add https://github.com/mateo19182/i18n-skill --skill i18n-mateo19182

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires prompts, fs-extra, lodash.set, and includes scripts (resource) components.

What problem does it solve?

Detects and manages hardcoded strings, mapping them to translation keys to simplify i18n workflows in React projects.

Core Features & Use Cases

Extract translation keys from source code using i18next-cli.
Auto-replace hardcoded strings with t("key") calls and inject useTranslation when needed.
Sync translations across locales and validate consistency in locale files.

Quick Start

Initialize the i18n workflow in your project by running the automated translation sequence.

Frequently Asked Questions about i18n

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

FAQPage Schema

How do I automatically replace hardcoded strings with i18next translation keys?▼

You can automate hardcoded string replacement by detecting text in React components and mapping it to translation keys using i18next-cli. The workflow modifies source files to inject useTranslation and apply proper t("...") usage.

How do I extract translation keys from React source code?▼

Translation key extraction is handled by i18next-cli, which scans your React source code to identify hardcoded strings. It generates a translation map from nested JSON structures to synchronize locales and validate consistency across locale files.

Does this i18n workflow work with react-i18next and TypeScript?▼

Yes, this i18n workflow specifically supports projects using react-i18next and TypeScript. It requires i18next-cli, React, and TypeScript scripts to parse lint results, generate translation maps, and modify source files.

How do I sync translations across multiple locale files?▼

Translation synchronization validates consistency across locale files by generating translation maps from nested JSON. The workflow uses i18next-cli to ensure all locales remain aligned during the automated translation sequence.

What is the best way to lint hardcoded strings for i18next?▼

The best way to lint hardcoded strings is using i18next-cli to parse lint results and detect untranslated text. TypeScript scripts then process these results to generate translation maps and automate code replacement in frontend components.

Why does my React component still show hardcoded text after running i18next-cli?▼

Hardcoded text may remain if the lint results were not parsed correctly or the automated code replacement failed to inject useTranslation. The workflow relies on TypeScript scripts to properly modify source files and apply t("...") usage.