oma-translation

# Translation - Context-Aware Localization ## Scheduling ### Goal Translate, review, or adapt multilingual content faithfully and naturally while preserving the parts that must remain exact: placeholders, code, links, formatting, terminology, and file structure. ### Intent signature - Translate, localize, review a translation, adapt copy, or create a glossary/style guide. - Update target-language files after the source changed. ### When to use - UI strings, error messages, locale files, documentation, reports, marketing copy, and prose. - Review of existing translations for accuracy, register, terminology, or naturalness. ### When NOT to use - i18n infrastructure, locale registration, or key extraction -> use the relevant development skill. - Date/pluralization APIs or other code-level localization -> use the owning code-domain skill. ### Expected inputs - Source text, target language or locale, content type, and requested output mode. - Existing locale files, glossary, surrounding context, and optional author sample. - Placeholder and formatting constraints when the source is structured. ### Expected outputs - Natural target-language text or evidence-backed review findings. - Exact preservation of placeholders, code spans, links, headings, list structure, and locale keys. - Translator notes only for meaningful ambiguity or necessary cultural explanation. ### Dependencies - Target profile: `resources/lang/{code}.md`, if one exists. - `resources/translation-rubric.md` ...