localize

Extract hardcoded strings and replace them with translation keys in ryOS apps.

1.2k|183|Updated Jan 28, 2025
One-click install
npx skills add https://github.com/ryokun6/ryos --skill localize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localize
Source: https://github.com/ryokun6/ryos/tree/main/.cursor/skills/localize
Command: npx skills add https://github.com/ryokun6/ryos --skill localize

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill automates localization workflows for ryOS apps by extracting hardcoded strings, generating translation keys, and coordinating translations across languages to ensure consistent, scalable UI text.

Core Features & Use Cases

  • Extract hardcoded strings from source files to generate translation keys.
  • Replace strings with t() calls to integrate with the i18n framework (e.g., react-i18next).
  • Maintain English translations in en/translation.json and synchronize translations across locales.
  • Support incremental localization for new apps and components, enabling rapid UI updates and feature rollouts.

Quick Start

Use the localization workflow to scan project files, generate translation keys, update source files with t() references, and refresh en/translation.json for the app you are localizing.

Frequently Asked Questions about localize

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

FAQPage Schema
How do I extract hardcoded strings and replace them with translation keys?

To extract hardcoded strings and replace them with translation keys, this skill scans your source files, generates the appropriate keys, and substitutes the text with t() calls for react-i18next integration.

How do I synchronize translation files across multiple locales?

You synchronize translation files across multiple locales by maintaining your base strings in en/translation.json, which the workflow uses to coordinate and refresh translations across all other language files.

Can I use this i18n workflow to incrementally localize new components?

Yes, you can use this i18n workflow to incrementally localize new apps and components, allowing you to extract strings and update translation files for specific UI sections without touching the entire project.

Does this string extraction tool require external installation?

No, this string extraction tool does not require external installation because it relies entirely on existing project tooling and file locations, specifically using the scripts/ directory and en/translation.json.

What is the best way to manage translation keys for ryOS apps?

The best way to manage translation keys for ryOS apps is to automate the localization workflow, scanning project files to generate keys, update source files with t() references, and refresh en/translation.json.

Why does translation sync require a specific file location?

Translation sync requires the specific en/translation.json file location because the workflow depends on existing project tooling and file structures to correctly map, store, and synchronize extracted translation keys.