oma-translator

Translates UI strings, documentation, and marketing copy with context-aware register and terminology preservation.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/javiruu/viru-air --skill oma-translator-javiruu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oma-translator
Source: https://github.com/javiruu/viru-air/tree/main/.agents/skills/oma-translator
Command: npx skills add https://github.com/javiruu/viru-air --skill oma-translator-javiruu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Machine-style translation often produces literal word-for-word output that breaks placeholders, mixes registers, and reads unnaturally in the target language. This Skill performs context-aware translation that infers register, domain, and style from the source text and surrounding codebase, then verifies output against mechanical checks and a quality rubric. ## Core Features & Use Cases - Context-Aware Translation: Infers register, domain terminology, and style from existing locale files, sibling translations, and surrounding code before translating. - Multi-Stage Verification: Runs mechanical checks (placeholder integrity, structure parity, CJK em-dash restructuring, sibling-pattern matching) plus a 50-point translation rubric and anti-AI-pattern scan before emitting output. - Batch and Diff-Sync Modes: Translates batches of i18n keys with terminology consistency, or patches existing translations against an English source diff while leaving untouched sections byte-identical. - Use Case: You updated your English README and need the Korean and Japanese versions brought back in sync. Provide the source diff and target file paths, and the Skill localizes only the changed sections while matching each file's existing voice and terminology. ## Quick Start Translate this UI string file into Korean, preserving all placeholders and matching the register of the existing locale files.

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 without breaking placeholders?▼

The Skill preserves every placeholder such as {name}, {{count}}, %s, and inline code spans exactly as-is during translation. A mechanical verification gate blocks output until placeholder integrity and structure parity with the source are confirmed.

How to keep terminology consistent across i18n locale files?▼

The Skill scans existing locale files and sibling translations before translating to align terminology, register, and style with project conventions. For batches, it reads all strings first and maintains consistent term choices across the entire batch.

Can I sync an existing translation after the English source changed?▼

Yes, diff-sync mode takes a unified diff of the English source plus target-language file paths, then localizes only the added, modified, or removed sections. Untouched sections remain byte-identical, and navigation uses heading anchors rather than line numbers.

Does it handle Korean, Japanese, and Chinese translation naturally?▼

Yes, the Skill restructures source syntax into natural CJK word order, restructures em dashes rather than substituting punctuation, omits contextually clear subjects, and avoids Europeanized patterns like passive voice abuse and noun pile-up.

When should I not use this translation Skill?▼

Do not use it for i18n infrastructure setup such as key extraction, routing, or build configuration, nor for adding new locales to framework config. Those tasks belong to development workflow tooling rather than translation.