translation

Translate Tale UI, marketing copy, and docs across locales using per-locale governance files.

20|5|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/tale-project/tale --skill translation-tale-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: translation
Source: https://github.com/tale-project/tale/tree/main/.claude/skills/translation
Command: npx skills add https://github.com/tale-project/tale --skill translation-tale-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate Tale's UI, marketing copy, and docs across locales while preserving a native voice per language. This cross-locale contract ensures that per-locale voice doctrine lives in locales/<locale>/AGENTS.md; the loanword buckets in BUCKETS.md, the conventions in CONVENTIONS.md, and the glossary workflow in GLOSSARY_GUIDE.md guide translation quality and governance. The frontmatter binding in SKILL.md defines the contractual expectations for contributors editing non-English content.

Core Features & Use Cases

  • Enforces a unified narrative across locales so readers experience consistent tone and terminology.
  • References locale-specific drift patterns, glossary rules, and stylistic conventions to guide edits in services/*/messages/, packages/ui/src/i18n/messages/, and docs/<locale>/.
  • Supports governance for translations by aligning with per-locale AGENTS.md and companion docs to reduce drift and improve localization quality.

Quick Start

Open locales/<locale>/AGENTS.md and read BUCKETS.md, CONVENTIONS.md, and GLOSSARY_GUIDE.md before editing any non-English files under services/*/messages/, packages/ui/src/i18n/messages/, or docs/<locale>/.

Frequently Asked Questions about translation

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

FAQPage Schema
How do I maintain consistent voice across multiple locales during translation?

Maintaining consistent voice across locales requires per-locale AGENTS.md files and companion docs like CONVENTIONS.md to govern tone and stylistic rules. This translation approach applies these references across UI messages and docs to enforce a unified narrative and reduce drift.

How do I prevent terminology drift in i18n message files when editing translations?

Preventing terminology drift in i18n message files involves referencing locale-specific BUCKETS.md for loanword rules and GLOSSARY_GUIDE.md for term governance. These files constrain edits in services/*/messages/ and packages/ui/src/i18n/messages/ to maintain translation consistency.

What is locale-specific voice doctrine and how does it guide multilingual copy translation?

Locale-specific voice doctrine is a set of per-locale rules defined in AGENTS.md, CONVENTIONS.md, and glossary guides. It governs how translations preserve a native voice per language, ensuring that UI, marketing copy, and docs experience consistent tone across target locales.

How do I start translating UI messages and docs while following locale conventions?

To start translating UI messages and docs, first read the locale-specific AGENTS.md, BUCKETS.md, CONVENTIONS.md, and GLOSSARY_GUIDE.md files. These governance references guide edits across services/*/messages/, packages/ui/src/i18n/messages/, and docs/<locale>/ directories.

Can I use glossary workflows to enforce translation quality in non-English docs?

Yes, glossary workflows defined in GLOSSARY_GUIDE.md enforce translation quality in non-English docs by providing term governance. Combined with the SKILL.md frontmatter contract and locale-specific tests, these workflows guide contributors in maintaining voice integrity.

Why does my localized UI copy lose its native tone across different locales?

Localized UI copy loses its native tone when translations drift from established voice doctrine. Applying per-locale AGENTS.md, loanword buckets, and stylistic conventions ensures that translation edits in i18n message files preserve a consistent, native voice.