oh-my-agent-commandcode 0.0.0-stage → 20.38.3

package/skills/oma-translation/resources/lang/_template.md

@@ -0,0 +1,73 @@
+# `<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.

package/skills/oma-translation/resources/lang/en.md

@@ -0,0 +1,123 @@
+# English Target-Language Profile (`en`)
+
+Load this profile when the **target** primary language subtag is `en`, including
+`en-US` and `en-GB`. Read it with `../translation-rubric.md` for substantive
+content or review. For substantive prose style, follow
+`../style-skills.md`.
+
+This profile owns source-to-English grammar and project conventions.
+
+---
+
+## Register
+
+| Voice | Effect |
+|---|---|
+| `formal` | full sentences, no contractions, third person, no fragments |
+| `balanced` | contractions allowed, second person for instructions, fragments in labels and cells |
+| `interpreter` | short sentences, direct address, fragments allowed where natural |
+
+Documentation defaults to second-person imperative for instructions ("Run the
+migration") and third person for descriptions. Do not drift into first-person
+plural ("we recommend") unless the source has an authorial voice.
+
+---
+
+## English-only rules
+
+### EN-1. Articles
+
+CJK sources do not supply English articles. Choose the article from the noun's
+meaning and context.
+
+```
+Bad:  Run migration before starting server.
+Good: Run the migration before starting the server.
+
+Bad:  This is the useful tool for the developers.
+Good: This is a useful tool for developers.
+```
+
+Rules of thumb: a specific, previously-mentioned, or uniquely-identified thing
+takes `the`; a first mention of a countable thing takes `a`/`an`; generic plurals
+and uncountables take no article.
+
+### EN-2. Number marking
+
+CJK does not inflect for number. Decide singular or plural for every countable
+noun, and make the verb agree.
+
+```
+Bad:  The config file are loaded from three location.
+Good: The config files are loaded from three locations.
+```
+
+### EN-3. Topic-comment to subject-predicate
+
+Korean and Japanese front the topic with `은/는` or `は` and leave the subject
+implicit. English needs an explicit subject in the right slot.
+
+```
+KO:   이 기능은 캐시를 쓰기 때문에 첫 실행이 느립니다
+Bad:  This feature, because it uses cache, first run is slow.
+Good: Because this feature uses a cache, the first run is slow.
+```
+
+### EN-4. Split long CJK sentences
+
+A single Korean or Japanese sentence often carries three clauses joined by
+`~므로`, `~는데`, `〜ため`. Rendering that as one English sentence produces a
+run-on. Split at the clause boundaries.
+
+```
+Bad:  The scan reads the manifest and because the manifest may be stale it
+      re-hashes each file and then reports the drift.
+Good: The scan reads the manifest. Because the manifest may be stale, it
+      re-hashes each file, then reports the drift.
+```
+
+### EN-5. Drop politeness padding
+
+Korean and Japanese business register carries deference that becomes servile or
+odd in English.
+
+```
+확인 부탁드립니다        → Please review.        (not "I humbly request your kind review")
+~해 주시기 바랍니다      → Run ... / Please run ...
+ご確認いただけますと幸いです → Please confirm.
+参考にしてください       → See ... / For reference, see ...
+```
+
+Do not add "kindly", "please be informed", "as per", or "do the needful".
+
+### EN-6. Unpack Sino-Korean and 漢語 nominalizations into verbs
+
+```
+검증을 수행합니다      → validates      (not "performs validation")
+개선을 진행했습니다    → improved       (not "carried out an improvement")
+最適化を実施する       → optimize       (not "implement optimization")
+```
+
+### EN-8. Typography
+
+- **Quotes**: straight `"` and `'` in code-adjacent docs and Markdown source.
+  Curly quotes only when the publishing pipeline requires them.
+- **Headings**: match the case used by sibling headings.
+- **Serial comma**: follow sibling files; be consistent within a document.
+- **Dates**: `2026-08-20` in tables and logs, `August 20, 2026` in US-audience
+  prose, `20 August 2026` for international audiences. Follow siblings.
+- **Units**: space between number and unit (`10 MB`, `200 ms`); no space before
+  `%` (`40%`).
+- **Spelling**: match the project's existing variety (US vs UK); do not mix.
+
+---
+
+## English self-check
+
+- [ ] Every countable noun has a correct article or a deliberate zero article (`EN-1`)
+- [ ] Number and subject-verb agreement are correct throughout (`EN-2`)
+- [ ] No topic-comment structure left untranslated (`EN-3`)
+- [ ] No run-on carried over from a multi-clause CJK sentence (`EN-4`)
+- [ ] No politeness padding, "kindly", or "do the needful" (`EN-5`)
+- [ ] Nominalizations unpacked into verbs (`EN-6`)
+- [ ] Heading case, serial comma, date format, and spelling variety match siblings (`EN-8`)

package/skills/oma-translation/resources/lang/ja.md

@@ -0,0 +1,274 @@
+# Japanese Target-Language Profile (`ja`)
+
+Load this file whenever the **target** language is Japanese. It is read together
+with `../translation-rubric.md` for substantive content or review. For prose style
+review, also load `../../../_shared/core/anti-ai-prose.md` (common taxonomy) and
+`../anti-ai-patterns.md` (translation exceptions and grammar diagnostics).
+
+- **Localizations** of shared anti-AI patterns.
+- **Japanese-only rules** (`JA-1`–`JA-9`).
+
+---
+
+## Register
+
+| Style | Ending | Use for |
+|---|---|---|
+| です・ます体 (敬体) | `です` / `ます` | user-facing docs, READMEs, release notes, agent reports |
+| だ・である体 (常体) | `だ` / `である` | specs, reference docs, academic prose, changelog bodies |
+
+Resolution order:
+
+1. Match the dominant style of sibling files in the same directory.
+2. Otherwise map from `translation_voice`: `formal` → です・ます体 with fully
+   expanded sentences, `balanced` → です・ます体 for prose and である体 for
+   reference tables, `interpreter` → です・ます体 with shorter sentences and
+   permitted 体言止め in label positions.
+
+Never mix the two inside one document. Headings and table cells are exempt.
+
+**Honorifics**: use 尊敬語 / 謙譲語 only where the source addresses a person or the
+project already does. Avoid 二重敬語 (`お伺いいたします` → `伺います`,
+`ご覧になられる` → `ご覧になる`).
+
+---
+
+## Japanese-only rules
+
+### JA-1. 一文一義 — one proposition per sentence
+
+Japanese tolerates long sentences grammatically but reads poorly when a single
+sentence carries three or more clauses joined by `〜が`, `〜ため`, `〜ので`. English
+compound sentences should be split rather than chained.
+
+```
+Bad:  この機能はキャッシュを使用しますが、初回実行時にはキャッシュがないため
+      レイテンシが増加しますので、事前にウォームアップを実行してください。
+Good: この機能はキャッシュを使用します。初回実行時はキャッシュがないため
+      レイテンシが増加します。事前にウォームアップを実行してください。
+```
+
+### JA-2. Trim redundant potential and progressive forms
+
+```
+〜することができます  → 〜できます
+〜を行います          → 〜します
+〜という形になります  → 〜です / 〜になります
+〜させていただきます  → 〜します   (unless the source is genuinely deferential)
+```
+
+### JA-3. 体言止め is positional
+
+Noun-ending sentences are natural in headings, bullet labels, and table cells,
+and unnatural in narrative body text. This is the same boundary as Korean
+`KO-3`, but Japanese tolerates 体言止め in more list positions.
+
+```
+Bad (body):  `ANTHROPIC_API_KEY` の未設定。
+Good (body): `ANTHROPIC_API_KEY` は設定されておらず、OAuth で認証します。
+Good (cell): 結果: lint 失敗
+```
+
+### JA-4. Suffix abstraction overuse (`〜性` / `〜化` / `〜的`)
+
+AI output stacks abstract suffixes where a verb or adjective is natural.
+
+```
+可用性の向上を実施します   → より安定して使えるようにします
+自動化を行います           → 自動で処理します
+構造的な問題               → 構造の問題
+```
+
+Keep the suffix when it is established terminology (`可用性`, `冪等性`,
+`後方互換性` in technical specs).
+
+### JA-5. Punctuation and script
+
+- **句読点**: `、` and `。` (fullwidth). Never `，` `．` unless the project already
+  uses them.
+- **Brackets**: `「」` for quotation, `『』` for titles and nested quotation,
+  fullwidth `（）` for asides in Japanese text, halfwidth `()` around ASCII-only
+  content such as `(CLI)`.
+- **Em dash**: `—` is not Japanese typography. Restructure, or use `。` to split.
+  Do not swap it for `：` and stop there (the mechanical punctuation swaps guidance).
+- **中黒**: `・` for coordinating loanword nouns (`インストール・設定`).
+- **Spacing**: follow the project convention for a space between Japanese and
+  ASCII runs. Read three sibling files before choosing; do not switch mid-file.
+- **波ダッシュ**: `〜` for ranges (`3〜5 件`), not `~`.
+
+### JA-6. 長音符 policy
+
+`サーバー` vs `サーバ`, `コンピューター` vs `コンピュータ`. Both conventions are in
+active use. Match the project's existing files; if none exist, use the JIS-style
+long form (`サーバー`) for user-facing docs.
+
+### JA-7. カタカナ vs 漢語
+
+Do not romanize a concept the project already writes in 漢語, and do not force a
+kanji compound where the loanword is the industry standard.
+
+```
+デプロイ  keep (not 配備)
+ロールバック keep (not 巻き戻し)
+認証 keep (not オーセンティケーション)
+検証 keep (not バリデーション) — unless the codebase uses バリデーション
+```
+
+Consistency with the project's existing translations decides.
+
+### JA-8. Avoid 二重否定 and hedge stacking
+
+```
+Bad:  対応していないわけではありません
+Good: 対応しています / 一部だけ対応しています
+
+Bad:  可能性があるかもしれません
+Good: 可能性があります
+```
+
+### JA-9. Numbers, dates, units
+
+- Dates: `2026年8月20日` in prose, `2026-08-20` in tables and logs.
+- Numerals: halfwidth (`5 件`, `12,000`), not `５件`.
+- Percent: `40%` with no space.
+- Counters must match the noun (`件`, `個`, `台`, `回`, `つ`).
+
+---
+
+## Localizations of shared rules
+
+### `-ing` participle phrases
+
+See [Superficial analysis](../../../_shared/core/anti-ai-prose.md#superficial-analysis).
+
+```
+EN:   The update improves performance, ensuring a seamless experience
+Bad:  このアップデートはパフォーマンスを向上させ、シームレスな体験を保証します
+Good: このアップデートでパフォーマンスが改善され、より快適に使えます
+```
+
+### AI vocabulary overuse
+
+See [Vocabulary clustering](../../../_shared/core/anti-ai-prose.md#vocabulary-clustering).
+
+| Watch | Prefer |
+|---|---|
+| また (sentence-initial, repeated) | restructure or drop |
+| 重要な / 不可欠な | only when the source emphasizes |
+| 活用する | 使う, 利用する |
+| さまざまな | usually delete |
+| 〜を通じて | restructure the clause |
+| 最適化する / 最大化する | match the source's intensity |
+
+### rule of three
+
+See [Mechanical triples](../../../_shared/core/anti-ai-prose.md#mechanical-triples).
+
+```
+EN:   a fast, reliable, and intuitive experience
+Bad:  高速で、信頼性が高く、直感的な体験
+Good: 速く、信頼性が高く、直感的な体験
+```
+
+Preserve every source quality. A real three-item list is valid when all three carry meaning.
+
+### synonym cycling
+
+See [Synonym cycling](../../../_shared/core/anti-ai-prose.md#synonym-cycling).
+
+If `ユーザー` is right, use `ユーザー` throughout. Do not rotate through
+`利用者`, `使用者`, `エンドユーザー`.
+
+### compound stacking
+
+See [Compound adjective stacking](../../../_shared/core/anti-ai-prose.md#compound-adjective-stacking) and [Abstract noun and adjective stacking](../../../_shared/core/anti-ai-prose.md#abstract-noun-and-adjective-stacking).
+
+```
+Bad:  AI 搭載のクラウドベースのエンタープライズグレードのソリューション
+Good: クラウド上で動くエンタープライズグレードの AI ソリューション
+```
+
+### mechanical punctuation swap
+
+See [Mechanical punctuation swaps](../../../_shared/core/anti-ai-prose.md#mechanical-punctuation-swaps).
+
+```
+Source: Documentation drift checks — broken refs and diff-affected docs
+Lazy:   ドキュメントドリフトチェック：壊れた参照と diff 影響ドキュメント
+Better: 参照の整合性チェックと、変更の影響を受けるドキュメントの特定
+```
+
+### unnecessary connectives
+
+See [Unnecessary Connectives](../anti-ai-patterns.md#unnecessary-connectives).
+
+```
+Bad:  パフォーマンスが向上しました。したがって、ユーザー体験が良くなりました。
+Good: パフォーマンスが向上し、ユーザー体験も良くなりました。
+```
+
+Watch したがって, しかしながら, さらに, また, その結果.
+
+### passive voice
+
+See [Passive Voice Abuse](../anti-ai-patterns.md#passive-voice-abuse).
+
+```
+Bad:  この機能はチームによって開発されました
+Good: チームがこの機能を開発しました
+```
+
+### noun pile-up
+
+See [Noun Pile-up (Long Modifier Chains)](../anti-ai-patterns.md#noun-pile-up-long-modifier-chains).
+
+```
+Bad:  AI ベースのクラウド対応リアルタイムデータ監視システム
+Good: AI を使ってクラウド上でデータをリアルタイムに監視するシステム
+```
+
+### over-nominalization
+
+See [Over-nominalization](../anti-ai-patterns.md#over-nominalization).
+
+```
+議論を行いました → 議論しました
+改善を実施する   → 改善する
+検討を進める     → 検討する
+```
+
+### forced pronouns
+
+See [Awkward Pronoun Insertion](../anti-ai-patterns.md#awkward-pronoun-insertion).
+
+```
+Bad:  私たちはこの機能をリリースし、私たちは良い反応を得ました
+Good: この機能をリリースしたところ、反応は良好でした
+```
+
+Japanese omits subjects freely. Insert `私たち` only when the actor genuinely
+changes or contrast requires it.
+
+### cleft calques
+
+See [Cleft Sentence Calques](../anti-ai-patterns.md#cleft-sentence-calques).
+
+```
+Bad:  重要なのはユーザー体験であるということです
+Good: ユーザー体験が重要です
+```
+
+---
+
+## Japanese self-check
+
+- [ ] One style throughout; no です・ます / である mixing
+- [ ] No sentence chaining three or more clauses (`JA-1`)
+- [ ] No `〜することができます` / `〜を行います` redundancy (`JA-2`)
+- [ ] No 体言止め in narrative body text (`JA-3`)
+- [ ] No stacked `〜性` / `〜化` / `〜的` where a verb works (`JA-4`)
+- [ ] `、` `。` used; no `—`; no curly quotes (`JA-5`)
+- [ ] 長音符 and カタカナ / 漢語 choices match sibling files (`JA-6`, `JA-7`)
+- [ ] No 二重否定 or stacked hedges (`JA-8`)
+- [ ] No 二重敬語
+- [ ] Halfwidth numerals with correct counters (`JA-9`)