oma-translation

Translates UI strings, documentation, and marketing copy with language-specific quality rules and verification gates.

1.3k|146|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/first-fluke/oh-my-agent --skill oma-translation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oma-translation
Source: https://github.com/first-fluke/oh-my-agent/tree/main/.agents/skills/oma-translation
Command: npx skills add https://github.com/first-fluke/oh-my-agent --skill oma-translation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Machine translation often produces stiff, unnatural output that leaks source-language word order, breaks placeholders, and drifts in register. This Skill enforces a structured translation workflow with per-language profiles, mechanical verification checks, and a scoring rubric so translated content reads as natively written.

Core Features & Use Cases

  • Context-aware translation: Infers register, domain, and terminology from existing locale files, sibling translations, and surrounding code before drafting.
  • Per-language quality profiles: Ships rule sets for Korean, Japanese, Chinese, and English covering typography, register systems, and translation-ese patterns, with a template for adding new languages.
  • Blocking verification gate: Runs mechanical checks (placeholder integrity, structure parity, em-dash and quote rules) plus a 5-criterion rubric before any output is emitted.
  • Use Case: Translate a README into Korean and Japanese in parallel, then run diff-sync mode to patch only the sections that changed after the English source is updated.

Quick Start

Translate this README section into Korean, preserving all placeholders and matching the register of the existing locale files.

Frequently Asked Questions about oma-translation

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

FAQPage Schema
How do I translate UI strings without breaking placeholders?

The Skill preserves every placeholder such as {name}, {{count}}, %s, and HTML tags exactly as-is during translation. A blocking verification gate checks placeholder integrity and structure parity before any output is emitted.

How to keep translation terminology consistent across a project?

It scans existing locale files and sibling translations first to align terminology and register with what the project already uses. One term per concept is enforced, and glossary violations are flagged during the rubric scoring stage.

Which target languages have dedicated quality profiles?

Dedicated profiles exist for Korean, Japanese, Chinese, and English, each with language-specific grammar, typography, and register rules. Other languages fall back to the shared anti-AI-pattern rules, and new profiles can be added from the provided template.

Can it update translations when the source document changes?

Yes, diff-sync mode takes a unified diff of the changed source and patches only the affected sections in each target file. Untouched sections remain byte-identical, and multiple locales can be processed in parallel.

When should I not use this translation workflow?

It is not intended for i18n infrastructure setup such as key extraction, routing, or framework locale configuration. Those tasks belong to a development workflow skill rather than a translation quality skill.