en-ru-translator-adv

To translate technical documentation into Russian while preserving code snippets and UI labels, this Skill enforces mixed-language handling rules that leave CLI commands, code samples, and product names in English. It applies a three-step workflow to ensure consistent terminology and natural phrasing.

The best way to localize marketing copy into natural Russian is using a three-step agentic workflow that drafts, self-reflects with editorial checks, and applies a final edit. This process removes machine-translation artifacts and enforces Maxim Ilyahov’s informational style for publication-ready text.

Yes, you can use this for translating UI strings with length constraints and specific glossary terminology. The Skill enforces glossary consistency, exact modality, and concise wording during its self-reflection and final editing phases to ensure the localized UI text fits constraints.

Yes, English to Russian translation here handles correct typography and special characters like ё. The Skill's editorial checklist explicitly enforces Russian typography rules, including the mandatory use of the ё character and correct dash usage throughout the final text.

To ensure consistent terminology across long technical materials translated into Russian, the Skill applies a translate-reflect-refine workflow with strict glossary consistency checks. This maintains uniform terminology and list parallelism throughout extensive educational or technical documents.

When using automated English to Russian translation for educational exam questions, the limitation is avoiding altered meaning or modality. This Skill mitigates this by enforcing exact modality and concise wording during its self-reflection step, ensuring the translated questions preserve their original intent.