Skip to content

oliverv/caro / .agents/skills/oma-translation

oma-translation

Verified

Translate or revise localized UI strings and prose while preserving meaning, terminology, placeholders, and structure.

FileKindSize
SKILL.mdskill md11.2 KB
resources/anti-ai-patterns.mdmarkdown4.6 KB
resources/lang/_template.mdmarkdown3.0 KB
resources/lang/en.mdmarkdown8.2 KB
resources/lang/ja.mdmarkdown9.9 KB
resources/lang/ko.mdmarkdown15.1 KB
resources/lang/zh.mdmarkdown9.1 KB
resources/translation-rubric.mdmarkdown4.8 KB

resources/lang/_template.md

View on GitHub
# `<Language>` Target-Language Profile (`<code>`)

Copy this file to `<code>.md` (BCP 47 primary subtag, e.g. `de.md`, `pt.md`,
`vi.md`) to add a profile. Register the code in the routing table in
`../../SKILL.md` under "Language Profile Loading".

A profile exists to hold what the shared files must not: anything that is true
of one target language and false of another. If a rule would apply equally to
every target, put translation-specific guidance in `../anti-ai-patterns.md`.
Put prose diagnostics that also apply to academic writing in
`../../../_shared/core/anti-ai-prose.md`; refer to patterns by heading name.

Delete every section you have nothing grounded to say about. An empty profile
is better than an invented one, because a wrong rule is followed as confidently
as a right one.

---

## Variant resolution

Only if the language has variants that change script, vocabulary, or
orthography (`pt-BR` vs `pt-PT`, `zh-CN` vs `zh-TW`, `es-ES` vs `es-419`).
State the resolution order and the default, and say what must never be mixed.

## Register

How formality is encoded in this language, and how it maps to `translation_voice`
(`formal` / `balanced` / `interpreter`) from `.agents/oma-config.yaml`.

Cover whatever the language actually forces a choice on: sentence endings,
T-V distinction (`du`/`Sie`, `tu`/`vous`, `tú`/`usted`), honorifics, or
formal/informal verb paradigms. State that the choice is made once per document
and never drifts, and name the exempt positions (headings, table cells).

## `<CODE>`-only rules

Number them `<CODE>-1`, `<CODE>-2`, ... so the self-check and `SKILL.md` can
cite local requirements unambiguously.

Typical categories worth a rule, when the language has one:

- Grammatical agreement the source language lacks (gender, case, number,
  animacy, definiteness)
- Word order constraints (V2, verb-final, clitic placement)
- Constructions that only appear as calques from English
- Typography: quotation marks, dashes, decimal and thousands separators,
  spacing before punctuation, capitalization of headings and nouns
- Date, number, and unit formats
- Orthography standards and the loanword forms machine output gets wrong

Give every rule at least one `bad → good` pair. The examples do more work than
the rule text.

## Localizations of shared rules

Include only patterns that manifest distinctly in this language. Use a descriptive
heading and link to the corresponding heading in the common prose diagnostics or
translation resource. Show the language-specific example beneath that reference.

Common topics include participle phrases, vocabulary, synonym cycling, compound
stacking, dash handling, and translation-ese.

Say explicitly when a shared rule **does not** apply. `en.md` does this for the
em-dash rule, which exists only for CJK targets. Silence gets read as agreement.

## `<Language>` self-check

A flat checklist, one line per rule, each citing its rule ID. It runs after the
shared self-check, before emitting.

## References

Cite sources for adopted rules, with the license when the source is a repository.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall