Muvon/octomind-tap / skills/content-locale-humanize-ja
content-locale-humanize-ja
VerifiedCalibration anchors for AI-slop and translationese in Japanese (ja) text. Use alongside content-locale-humanize when the target is Japanese.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.4 KB |
SKILL.md
View on GitHub---
name: content-locale-humanize-ja
title: "Japanese Native-Fluency Calibration"
description: "Calibration anchors for AI-slop and translationese in Japanese (ja) text. Use alongside content-locale-humanize when the target is Japanese."
license: Apache-2.0
compatibility: "Calibration data only; no tools required. Network access helps for usage checks."
domains: content
rules:
- content(japanese)
- match(\bja-JP\b)
- match(\bJapanese\b)
- match(日本語)
- semantic(check if this Japanese translation sounds native)
- semantic(eliminate translationese from this Japanese text)
---
## Overview
Calibration anchors and current norms for Japanese (ja-JP), feeding content-locale-humanize's dimensions. A calibration aid, not the checklist; reason natively beyond it.
## Rules
### AI tells
Sourcing confidence: anecdotal blog discourse, not quantitative research.
- Katakana loanwords where a native term exists: インサイト, アウトプット, スケーラビリティ.
- Hedge endings such as「〜ではないでしょうか」; SEO-blog closers such as「いかがでしたか」.
- Uniformly formal, emotionally flat register; the same phrase repeated within a passage instead of natural rephrasing.
### Translationese (翻訳調)
- Pronouns Japanese would drop: 彼, 彼女, それ, あなた.
- 「〜することができる」for every "can", 「〜によって」passives, 「〜を持っている」for "have".
- Long noun-modifying chains copied from English relative clauses; 「〜しましょう」for every "let's".
### Current norms
- Style: です・ます for most product, marketing, and help content; だ・である for reference or academic text. Never mix them in body text.
- Keigo: avoid double honorifics (おっしゃられる, ご覧になられる) and reflexive 「させていただく」; machine output tends to over-polish.
- Notation: full-width 、。 (the 2022 公用文作成の考え方 made 、 the default even in horizontal official text); half-width alphanumerics; follow the house rule for long-vowel katakana (コンピューター vs コンピュータ) and for spacing between Japanese and Latin text (the JTF translation style guide uses none). Hold each choice throughout.
## References
Reviewed 2026-10-12. AI tells: note.com and Zenn blog discourse; ai-souken.com. Norms: 文化審議会「公用文作成の考え方」(建議, 2022), JTF日本語標準スタイルガイド.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |