skills.rest
xiayu519
xiayu519COMMUNITY
Explore all skills by this author →
GitHub

localization-dev

Route zh_cn and en_us localization text changes through Luban-dev Excel export.

63|6|Updated Mar 2, 2026
Search Tags:#localization#excel#i18n#localization-workflow#luban-dev#tablelocalizationtext#tyou
One-click install
npx skills add https://github.com/xiayu519/Tyou --skill localization-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: localization-dev
Source: https://github.com/xiayu519/Tyou/tree/main/.agents/skills/localization-dev
Command: npx skills add https://github.com/xiayu519/Tyou --skill localization-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tyou 多语言文案/本地化/i18n 工作流 skill，专注于新增或修改多语言文本的统一处理。它确保文本变更通过 Luban-dev 的导表流程进行，从源表到运行时的本地化文本生成，避免直接改生成代码或手写字典导致的不一致。

Core Features & Use Cases

  • 集中管理多语言文本：通过 TableLocalizationText 和相关表格完成语言文本的增删改查与版本控制。
  • 审核与安全：对 key 的稳定性与唯一性进行校验，确保导表前的重复项与语义重复的文本被正确处理。
  • 运行时访问：生成后文本通过 tyou.i18n.get(key, ...) 或 LocalizeLabel 在运行时正确显示。

Quick Start

Add or update localization text through Luban-dev by editing the source Excel at Design/config/#TableLocalizationText.xlsx and then verify runtime access via tyou.i18n.get.

Frequently Asked Questions about localization-dev

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

FAQPage Schema
How do I add new localization text keys for zh_cn and en_us using the Luban Excel workflow?▼

To add localization text, edit the source Excel at Design/config/#TableLocalizationText.xlsx via Luban-dev to insert or update zh_cn and en_us keys, ensuring id and key uniqueness before exporting through the Luban Excel flow.

How does the Tyou localization workflow prevent duplicate i18n keys?▼

The Tyou localization workflow enforces uniqueness by validating key stability and checking for duplicate or semantically overlapping text entries before exporting through Luban-dev, ensuring import safety and preventing runtime conflicts.

Do I need Luban-dev to modify TableLocalizationText source tables?▼

Yes, you need Luban-dev to modify the source Excel files for TableLocalizationText, as the workflow requires routing all text changes through the Luban Excel flow to avoid direct modifications to generated code or manually written dictionaries.

How do I retrieve localized text at runtime after exporting through the Luban Excel flow?▼

After exporting localization text through the Luban Excel flow, retrieve the generated strings at runtime by calling tyou.i18n.get(key, ...) or by using the LocalizeLabel component to display the correct language text.

What is the best way to manage multi-language text changes without causing runtime inconsistencies?▼

The best way to manage multi-language text changes is routing all zh_cn and en_us additions and updates through the centralized TableLocalizationText structure and Luban-dev export flow, ensuring proper governance and preventing direct code edits.

Why does my Tyou i18n text display incorrectly after manually editing the generated localization code?▼

Tyou i18n text displays incorrectly when bypassing the Luban-dev Excel workflow because manual edits to generated code or hand-written dictionaries cause mismatches with the source TableLocalizationText structure, breaking the validated localization text workflow.

Related Skills

Explore More Content & Communication Skills→
xiayu519xiayu519
63

luban-dev

Automates Luban configuration table creation, validation, and export workflows from Design/config Excel files and Defines.

Community
Advanced
sorodriguezzsorodriguezz

String Localization and Message Dictionaries

Manage application string localization via message dictionaries and XML exchange.

Community
Intermediate
massCodeIOmassCodeIO
6.9k

i18n

Manage translation keys across en_US and ru_RU locales in massCode.

Official
Intermediate
lpjhelderlpjhelder

ai-slop-cleaner

Remove dead code, duplication, and needless abstractions from scoped files.

Community
Intermediate