skills.rest
eaglhuang
eaglhuangCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ui-i18n-localize

Expand zh-TW UI strings to zh-CN, en, and ja while preserving placeholders.

3|Updated Mar 6, 2026
Search Tags:#consistency#validation#localization#translation#i18n#ui-strings
One-click install
npx skills add https://github.com/eaglhuang/cocos_new --skill ui-i18n-localize
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ui-i18n-localize
Source: https://github.com/eaglhuang/cocos_new/tree/main/.github/skills/ui-i18n-localize
Command: npx skills add https://github.com/eaglhuang/cocos_new --skill ui-i18n-localize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill accelerates UI localization by expanding from zh-TW as the base language to zh-CN, en, and ja, while preserving placeholders and formatting.

Core Features & Use Cases

  • Consistent cross-language UI text by deriving locales from zh-TW.json and updating corresponding locale files.
  • Validate and preserve placeholders like {0}, {1} to avoid runtime errors.
  • Generate a width-risk overflow report to surface layout constraints before deployment.

Quick Start

Provide zh-TW base keys and target locales, then run the workflow to generate zh-CN, en, and ja resources and an overflow risk report.

Frequently Asked Questions about ui-i18n-localize

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

FAQPage Schema
How do I translate UI strings from Traditional Chinese to English, Simplified Chinese, and Japanese?▼

UI localization from a zh-TW base to zh-CN, en, and ja is handled by expanding base keys into target locale JSON files, preserving placeholders and formatting to ensure consistent cross-language text.

How do I preserve placeholders like {0} when batch updating translations for a screen?▼

Preserving placeholders like {0} during batch updates is achieved by validating and retaining formatting tokens within the translated UI strings, preventing runtime errors and maintaining structural consistency across all locales.

What is a width-risk overflow report in UI localization?▼

A width-risk overflow report surfaces layout constraints by auditing string length risk across locales before deployment, allowing developers to identify and address potential UI truncation issues caused by translated text expansion.

Can I audit string length risk across zh-CN, en, and ja simultaneously?▼

Auditing string length risk across zh-CN, en, and ja simultaneously is supported by generating a width-risk report that compares expanded translations against the base zh-TW strings to highlight overflow constraints.

Where should generated locale JSON files be stored for internationalization?▼

Generated locale JSON files for internationalization should be placed under the assets/resources/i18n directory, ensuring the application can correctly load and reference the localized UI strings across different languages.

Do I need to manually format translations when adding new UI keys?▼

Manual formatting is unnecessary when adding new UI keys; the workflow automatically expands zh-TW base keys into target locales, preserving placeholders and generating the required locale JSON files without manual intervention.

Related Skills

Explore More Design & Creative Skills→
tegniketegnike
1.1k

sync-translations

Sync missing translation keys across locale files from a Japanese master.

Community
Basic
rafaelminatto1rafaelminatto1

i18n-localization

Detect hardcoded strings and missing translations across React, Next.js, Vue, and Python projects.

Community
Intermediate
StarrySerendipityStarrySerendipity

i18n

Detect hardcoded Chinese text in HTML/JS and replace it with i18n markers.

Community
Intermediate
dreamtidesdreamtides

rlf-localization

Define, translate, and validate RLF strings using the rlf! macro.

Official
Intermediate