translation-guide

Run the skill in generate mode, which reads your source and target language files, detects formality levels, terminology patterns, and punctuation conventions, then writes a .translation-guide.md file documenting the rules per language.

Use the check mode, which loads .translation-guide.md and validates every translation against its rules. It reports deviations per language, such as informal pronouns where formal ones are required or non-standard terminology choices.

It detects formality mismatches (formal vs informal pronouns), terminology drift where the same English term has multiple translations, grammatical pattern breaks like noun forms instead of infinitives on buttons, and punctuation or quotation mark style violations.

Yes. After generating the guide, the skill proposes adding structured tone and glossary fields to .translation-sync.json. The translation-sync skill then enforces these rules programmatically, which is stronger than free-form custom instructions.

Terms consistently left untranslated across all sampled languages, such as product names, brand names, and technical terms, are flagged as do-not-translate candidates. The skill proposes adding them to the glossary configuration automatically.