What problem does it solve?
Maintaining a documentation set across four locales (ko, en, ja, zh) often leads to drift: translations diverge from the canonical source, versions get hardcoded inconsistently, and formatting rules like Mermaid direction or emoji usage are applied unevenly. This Skill gives documentation specialists a single digest of the hard i18n rules that must be checked before any edit to the moai-adk README set or the adk.mo.ai.kr docs-site.
Core Features & Use Cases
- Canonical-locale enforcement: Defines Korean as the canonical source for both the README set and the docs-site, with a strict derivation chain (ko → en → ja/zh) that must land in the same PR.
- Formatting and content rules: Covers Mermaid TD-only diagrams, the no-emoji icon-shortcode rule, emphasis-marker spacing, the docs-domain URL blacklist, and version single-source-of-truth in hugo.toml.
- Redirect and deployment constraints: Requires locale-aware vercel.json redirects for moved pages and treats the Vercel production binding as immutable, keeping publishing human-gated.
- Use Case: Before editing README.ko.md, a specialist loads this Skill, learns that all four locale files must be updated in the same PR, and avoids committing a canonical-only change that would fail the locale-parity gate.
Quick Start
Load the i18n rules digest and list every hard rule I must follow before editing the Korean README and its three derived locales.
