oma-translator

Translate UI strings, documentation, and marketing copy while preserving placeholders and structure.

46|2|Updated Mar 23, 2025
One-click install
npx skills add https://github.com/gracefullight/krds --skill oma-translator-gracefullight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oma-translator
Source: https://github.com/gracefullight/krds/tree/main/.agents/skills/oma-translator
Command: npx skills add https://github.com/gracefullight/krds --skill oma-translator-gracefullight

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you translate multilingual content naturally while preserving meaning, tone, and formatting details like placeholders, links, and structure.

Core Features & Use Cases

  • Context-aware localization: Infers register, domain terminology, and style from the source text and surrounding project context.
  • Placeholder and structure preservation: Keeps interpolation variables, tags, and markup intact while ensuring headings, lists, and links remain equivalent.
  • Quality verification workflow: Uses mechanical checks and rubric/anti-pattern rules to avoid translationese, tone drift, and format breakage.
  • Use cases: Translating UI microcopy, error messages, documentation, and marketing text; reviewing existing translations; creating glossaries or style guides.

Quick Start

Translate the provided source text into Korean, preserving placeholders and matching the project’s existing tone and terminology.

Frequently Asked Questions about oma-translator

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

FAQPage Schema
How do I translate UI strings while preserving placeholders and formatting tags?

Context-aware translation preserves interpolation variables, tags, and markup by enforcing mechanical placeholder and format integrity checks, ensuring headings, lists, and links remain structurally equivalent across single or batch UI string translations.

What's the best way to avoid translationese and tone drift in localization?

Avoid translationese and tone drift by using a quality verification workflow that applies rubric-based naturalness checks, register consistency, and anti-AI pattern avoidance rules to your translated content.

Can I batch translate documentation and marketing copy with glossary constraints?

Yes, batch translation supports locale files, glossary constraints, and formatting rules, applying consistent domain terminology and style inference across documentation and marketing copy while maintaining document structure.

Does context-aware translation work for reviewing existing translations against a style guide?

Translation review verifies existing translations by checking terminology alignment, register consistency, and naturalness against rubric rules, ensuring the text meets project glossary and style guide requirements without introducing tone drift.

When should I not use automated translation for locale files?

Automated translation may be insufficient when source text lacks surrounding project context or when strict locale-specific legal requirements demand human review beyond mechanical placeholder integrity and rubric-based naturalness checks.