chaffjs 0.15.0 → 0.16.0

package/rules/latin-spacing.yaml

@@ -7,15 +7,16 @@ severity: warning
 # 番号・識別子として書かれた数を見分けるのに、数の後ろの語の品詞を使う。無ければ全部数える。
 uses: [pos]
 # 番地（千代田区紀尾井町1-3）を、都道府県までの地名の後ろの範囲（東京都2-3 営業日）と分ける。
-extra_word_lists: [prefecture-unit]
+# 日付・時刻（9月、2026年、10時5分）を、長さ（3ヶ月、3 時間）と分ける。
+extra_word_lists: [prefecture-unit, date-time-unit, calendar-unit, calendar-year-unit]
 
 name:
   ja: 英数字の前後の空白がそろっていない
   en: Spacing around Latin text is inconsistent
 
 why:
-  ja: 日本語と英字・数字のあいだを空けるか詰めるかは、どちらでも読めます。困るのは一つの文書の中で混ざることで、読み手には違いに意味があるように見えます。chaff はどちらが正しいかを決めず、文書の中で少ないほうを指摘します。英字と、数字の前、数字の後ろは別々に数えます。「を 3回」のように、数字の前は空けて助数詞とは詰める書き方がふつうにあるからです。「3GBの」のように数字に続く単位は、英字ではなく数字の側として数えます。逆に「H30 等」「EC2 で」「Phase 1 は」のように英字で始まって数字で終わる名前は、英字の側として数えます。「073-489-5909」「2026-06-02」のような番号は数量ではないので数えません。題や注の番号として書かれた数（「3.1 リサーチの原則」の節番号、※1 の注番号、行の頭に続き番号で並べた注の番号）、0 で始まる組を含む番号（102-0094）、〒の後ろの郵便番号（〒100-8916）、市・区・町まで下りた地名のすぐ後ろの番地（千代田区紀尾井町1-3）も、後ろの空白が番号と題・項目の区切りなので数えません。鉤括弧（「」『』）で引いた題名や発言の中も、空け方は引いた元のものなので数えません。
-  en: Whether to put a space between Japanese and Latin letters or digits is a choice either way. What reads badly is mixing both in one document, which suggests the difference means something. chaff does not decide which is right; it points at whichever the document uses less. Letters, the space before a digit and the space after one are counted separately, since spacing before a number but not before its counter is common. A unit after a number (3GB) counts with the number; a name that starts with a letter and ends in a digit (H30, EC2, Phase 1) counts with the letters. A code such as a phone number or a date (073-489-5909, 2026-06-02) is not a quantity and is not counted. Neither is a number written as the label of a title or a note (a section number such as 3.1 before its title, a note number after ※, the numbers of notes listed one per line in sequence), a code with a part starting with 0 (102-0094), a postal code after 〒 (〒100-8916), or a hyphenated address number right after a city, ward or town (千代田区紀尾井町1-3), since the space after it separates the label from its title or the next item. Nor is the spacing inside a title or a quotation in 「」 or 『』, which is the source's, not the writer's.
+  ja: 日本語と英字・数字のあいだを空けるか詰めるかは、どちらでも読めます。困るのは一つの文書の中で混ざることで、読み手には違いに意味があるように見えます。chaff はどちらが正しいかを決めず、文書の中で少ないほうを指摘します。英字と、数字の前、数字の後ろは別々に数えます。「を 3回」のように、数字の前は空けて助数詞とは詰める書き方がふつうにあるからです。「3GBの」のように数字に続く単位は、英字ではなく数字の側として数えます。逆に「H30 等」「EC2 で」「Phase 1 は」のように英字で始まって数字で終わる名前は、英字の側として数えます。「073-489-5909」「2026-06-02」のような番号は数量ではないので数えません。日付・時刻（「9月」「2026年」「10月1日」「3時」「10時5分」）も、数と単位を詰めて書く決まりなので、その中の境目は数えません（日付の前の空白は数えます）。長さ（「3ヶ月」「3 時間」「5日で」「3年」）は数量として数えます。題や注の番号として書かれた数（「3.1 リサーチの原則」の節番号、※1 の注番号、行の頭に続き番号で並べた注の番号）、0 で始まる組を含む番号（102-0094）、〒の後ろの郵便番号（〒100-8916）、市・区・町まで下りた地名のすぐ後ろの番地（千代田区紀尾井町1-3）も、後ろの空白が番号と題・項目の区切りなので数えません。鉤括弧（「」『』）で引いた題名や発言の中も、空け方は引いた元のものなので数えません。
+  en: Whether to put a space between Japanese and Latin letters or digits is a choice either way. What reads badly is mixing both in one document, which suggests the difference means something. chaff does not decide which is right; it points at whichever the document uses less. Letters, the space before a digit and the space after one are counted separately, since spacing before a number but not before its counter is common. A unit after a number (3GB) counts with the number; a name that starts with a letter and ends in a digit (H30, EC2, Phase 1) counts with the letters. A code such as a phone number or a date (073-489-5909, 2026-06-02) is not a quantity and is not counted. Nor is the inside of a date or a time written with units (9月, 2026年, 10月1日, 3時, 10時5分), which is packed by convention; the space before it still counts. A length of time (3ヶ月, 3 時間, 5日で, 3年) is a quantity and counts. Neither is a number written as the label of a title or a note (a section number such as 3.1 before its title, a note number after ※, the numbers of notes listed one per line in sequence), a code with a part starting with 0 (102-0094), a postal code after 〒 (〒100-8916), or a hyphenated address number right after a city, ward or town (千代田区紀尾井町1-3), since the space after it separates the label from its title or the next item. Nor is the spacing inside a title or a quotation in 「」 or 『』, which is the source's, not the writer's.
 
 message:
   ja: "日本語と{kind}のあいだを{style}（この文書はふつう{usual}。{of} 箇所のうち {count} 箇所が違う）"
@@ -28,4 +29,4 @@ how_to_fix:
 # 何箇所違えば指摘するか。1 は「1 箇所でも混ざっていれば」。
 levels: { strict: 1, normal: 1, relaxed: 3 }
 
-use_for: [business, blog, technical]
+use_for: [business, blog, technical, legal, docs, academic, literature, speech]

package/rules/max-kanji-continuous.yaml

@@ -4,6 +4,7 @@ status: experimental
 how_to_find: kanji-run
 # 品詞があれば、住所（地名と数だけでできた連なり）と 1 つの名前（辞書の固有名詞 1 語、人の姓と名）を数えない。無くても文字だけで動く。
 uses: [pos]
+# chaff.yaml の names に並べた名前は連なりを切る。鉤括弧の中身がまるごと 1 つの連なりなら数えない（書き手が 1 つの名前と示している）。
 # 住所の先頭にしか来ない単位（都道府県）。地名の後ろに付けば、割られた町名ではなく地名の並び。
 extra_word_lists: [prefecture-unit]
 languages: [ja]
@@ -22,9 +23,9 @@ message:
   en: '"{word}" runs {count} kanji together (limit {limit})'
 
 how_to_fix:
-  ja: ひらがなを 1 つ挟むか、助詞で割ってください。「情報処理推進機構の認定試験」に。
-  en: Break it with a particle or kana.
+  ja: ひらがなを 1 つ挟むか、助詞で割ってください。「情報処理推進機構の認定試験」に。割れない正式名称なら、chaff.yaml の names に並べると数えません。鉤括弧でまるごとくくった名前（「英国大使館別荘記念公園」）も数えません。
+  en: Break it with a particle or kana. If it is an official name that cannot be broken, list it under names in chaff.yaml and it is not counted. A name that fills a 「」 quotation exactly is not counted either.
 
 levels: { strict: 6, normal: 8, relaxed: 12 }
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/max-paragraph-length.yaml

@@ -14,7 +14,7 @@ why:
 
 message:
   ja: この段落は {count} 文あります（{limit} 文まで）
-  en: This paragraph runs {count} sentences (limit {limit})
+  en: This paragraph runs {count} {count|sentence|sentences} (limit {limit})
 
 how_to_fix:
   ja: 話題の変わり目で段落を割ってください。
@@ -22,4 +22,11 @@ how_to_fix:
 
 levels: { strict: 3, normal: 5, relaxed: 8 }
 
-use_for: [blog, business, technical]
+# 条文・判決・論文の段落は、一つの規定や論点をまとめて書く。corpus のその種類の文書で、normal が最も長い一握りの段落だけを指すように測って置いた。
+by_genre:
+  legal: { strict: 5, normal: 8, relaxed: 12 }
+  legal/statute: { strict: 8, normal: 12, relaxed: 16 }
+  legal/judgment: { strict: 8, normal: 12, relaxed: 16 }
+  academic: { strict: 5, normal: 9, relaxed: 12 }
+
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/max-sentence-length.yaml

@@ -14,7 +14,7 @@ why:
 
 message:
   ja: この文は {count} 文字あります（{limit} 文字まで）
-  en: "This sentence runs {count} words (limit {limit})"
+  en: "This sentence runs {count} {count|word|words} (limit {limit})"
 
 how_to_fix:
   ja: 接続助詞のところで 2 文に割ってください。それだけで読めるようになります。
@@ -46,5 +46,17 @@ by_genre:
   blog/owned-media:
     ja: { strict: 65, normal: 90, relaxed: 125 }
     en: { strict: 16, normal: 22, relaxed: 30 }
+  # 法令・契約・判決・論文は、長い一文がその種類の書き方。corpus のその種類の文書で、normal が最も長い一握りの文だけを指すように測って置いた。
+  legal:
+    ja: { strict: 120, normal: 200, relaxed: 300 }
+    en: { strict: 40, normal: 60, relaxed: 80 }
+  legal/statute:
+    ja: { strict: 200, normal: 300, relaxed: 450 }
+    en: { strict: 80, normal: 130, relaxed: 180 }
+  legal/judgment:
+    ja: { strict: 250, normal: 350, relaxed: 450 }
+  academic:
+    ja: { strict: 100, normal: 140, relaxed: 180 }
+    en: { strict: 35, normal: 50, relaxed: 65 }
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/ngram-repetition.yaml

@@ -16,12 +16,12 @@ why:
 
 message:
   ja: 「{word}」が {count} 回出てきます（{limit} 回まで）
-  en: '"{word}" appears {count} times (limit {limit})'
+  en: '"{word}" appears {count} {count|time|times} (limit {limit})'
 
 how_to_fix:
-  ja: 2 回目以降を言い換えるか、まとめて 1 度にしてください。
-  en: Rephrase the repeats, or say it once.
+  ja: 2 回目以降を言い換えるか、まとめて 1 度にしてください。繰り返しているのが組織名や製品名なら、chaff.yaml の names に並べると数えません。
+  en: Rephrase the repeats, or say it once. If what repeats is an organisation or product name, list it under names in chaff.yaml and it is not counted.
 
 levels: { strict: 3, normal: 5, relaxed: 9 }
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/no-doubled-joshi.yaml

@@ -17,7 +17,7 @@ why:
 
 message:
   ja: 「{word}」が読点を挟まずに {count} 回続いています（{limit} 回まで）
-  en: '"{word}" repeats {count} times with no break (limit {limit})'
+  en: '"{word}" repeats {count} {count|time|times} with no break (limit {limit})'
 
 how_to_fix:
   ja: 文を割るか、係り先を言い換えてください。「弊社の新製品の販売の計画」を「弊社が新製品を販売する計画」に。
@@ -25,4 +25,4 @@ how_to_fix:
 
 levels: { strict: 1, normal: 2, relaxed: 3 }
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/no-em-dash.yaml

@@ -18,7 +18,7 @@ why:
 
 message:
   ja: 1000 字あたり {density} 個のダッシュがあります（{limit} 個まで）
-  en: "{density} dashes per 1000 words (limit {limit})"
+  en: "{density} {density|dash|dashes} per 1000 words (limit {limit})"
 
 how_to_fix:
   ja: 読点か括弧に置き換えてください。挟み込みなら括弧、言い換えなら読点が読みやすいです。
@@ -29,4 +29,4 @@ levels:
   ja: { strict: 1, normal: 3, relaxed: 8 }
   en: { strict: 3, normal: 8, relaxed: 20 }
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/no-mixed-desumasu.yaml

@@ -26,4 +26,4 @@ how_to_fix:
 # 少数派が何文までなら「混在」と見るか。これを超えたら、混在ではなく別の文体と判断して黙る。
 levels: { strict: 5, normal: 3, relaxed: 1 }
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/no-nakaguro-parallel.yaml

@@ -15,7 +15,7 @@ why:
 
 message:
   ja: この文に中黒が {count} 個あります（{limit} 個まで）
-  en: "{count} middle dots in this sentence (limit {limit})"
+  en: "{count} middle {count|dot|dots} in this sentence (limit {limit})"
 
 how_to_fix:
   ja: 文を割るか、箇条書きにしてください。組の切れ目がはっきりします。
@@ -24,4 +24,4 @@ how_to_fix:
 # 実文書の分布から。1 文 4 個までは読める。
 levels: { strict: 3, normal: 5, relaxed: 8 }
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/numbering-gap.yaml

@@ -23,4 +23,4 @@ how_to_fix:
 
 levels: { strict: 1, normal: 1, relaxed: 1 }
 
-use_for: [business, technical, blog]
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]

package/rules/oxford-comma-consistency.yaml

@@ -3,6 +3,7 @@ layer: L3
 status: experimental
 how_to_find: oxford-comma
 languages: [en]
+extra_word_lists: [participle-word]
 severity: info
 
 name:
@@ -23,4 +24,4 @@ how_to_fix:
 
 levels: { strict: 3, normal: 2, relaxed: 1 }
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/padded-intro.yaml

@@ -28,4 +28,5 @@ levels:
   normal: 1
   relaxed: 2
 
-use_for: [blog]
+# プレスリリース・メール・議事録の冒頭は理由や用件を言う所で、つかみではない。
+use_for: [blog, business/report, business/proposal, legal, docs, academic, literature, speech]

package/rules/paragraph-length-variance.yaml

@@ -22,4 +22,4 @@ how_to_fix:
 
 levels: { strict: 40, normal: 30, relaxed: 20 }
 
-use_for: [blog]
+use_for: [blog, legal, docs, academic, literature, speech]

package/rules/preamble-length.yaml

@@ -14,7 +14,7 @@ why:
 
 message:
   ja: 最初の見出しまでに {count} 段落あります（{limit} 段落まで）
-  en: "{count} paragraphs before the first heading (limit {limit})"
+  en: "{count} {count|paragraph|paragraphs} before the first heading (limit {limit})"
 
 how_to_fix:
   ja: 結論を先に書くか、前置きを見出しの下へ移してください。
@@ -22,4 +22,4 @@ how_to_fix:
 
 levels: { strict: 1, normal: 2, relaxed: 4 }
 
-use_for: [business]
+use_for: [business, legal, docs, academic, literature, speech]

package/rules/preferred-term.yaml

@@ -24,4 +24,4 @@ how_to_fix:
 # チームが並べた書き方なので、1 つでも指摘する。並べた時点で「使わない」と決めている。
 levels: { strict: 1, normal: 1, relaxed: 3 }
 
-use_for: [business, blog, technical]
+use_for: [business, blog, technical, legal, docs, academic, literature, speech]

package/rules/proper-noun-density.yaml

@@ -3,6 +3,7 @@ layer: L3
 status: experimental
 how_to_find: proper-noun-density
 requires: [pos]
+# chaff.yaml の names に並べた名前は、何語に割れても 1 つと数える。名前そのものは数える（読み手が知らないことは変わらない）。
 severity: info
 
 name:
@@ -15,7 +16,7 @@ why:
 
 message:
   ja: 1000 語あたり {density} 個の固有名詞があります（{limit} 個まで）
-  en: "{density} proper nouns per 1000 words (limit {limit})"
+  en: "{density} proper {density|noun|nouns} per 1000 words (limit {limit})"
 
 how_to_fix:
   ja: 2 度目からは「その製品」「そのチーム」のように受けてください。初出で何者かを一言添えると、知らない人も読めます。
@@ -23,4 +24,4 @@ how_to_fix:
 
 levels: { strict: 20, normal: 40, relaxed: 80 }
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/repeated-conjunction.yaml

@@ -16,7 +16,7 @@ why:
 
 message:
   ja: 接続詞で始まる段落が {count} 続いています（{limit} まで）
-  en: "{count} paragraphs in a row open with a conjunction (limit {limit})"
+  en: "{count} {count|paragraph|paragraphs} in a row {count|opens|open} with a conjunction (limit {limit})"
 
 how_to_fix:
   ja: どれか 1 つを残して、他は言いたいことから始めてください。
@@ -24,4 +24,4 @@ how_to_fix:
 
 levels: { strict: 1, normal: 2, relaxed: 4 }
 
-use_for: [business, blog, technical]
+use_for: [business, blog, technical, legal, docs, academic, literature, speech]

package/rules/repeated-sentence-head.yaml

@@ -14,7 +14,7 @@ why:
 
 message:
   ja: 「{head}」で始まる文が {count} 続いています（{limit} まで）
-  en: '{count} sentences in a row open with "{head}" (limit {limit})'
+  en: '{count} {count|sentence|sentences} in a row {count|opens|open} with "{head}" (limit {limit})'
 
 how_to_fix:
   ja: 語順を変えるか、1 文を前の文に繋げてください。
@@ -25,4 +25,4 @@ levels:
   normal: 3
   relaxed: 4
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/required-sections.yaml

@@ -23,4 +23,4 @@ how_to_fix:
 # 何個足りなければ指摘するか。1 は「1 つでも足りなければ」。
 levels: { strict: 1, normal: 1, relaxed: 2 }
 
-use_for: [business, blog, technical]
+use_for: [business, blog, technical, legal, docs, academic, literature, speech]

package/rules/rule-of-three.yaml

@@ -14,7 +14,7 @@ why:
 
 message:
   ja: 箇条書き {total} 個のうち {count} 個が 3 項目です（{limit}% まで）
-  en: "{count} of {total} lists have exactly three items ({limit}% allowed)"
+  en: "{count} of {total} {total|list|lists} {count|has|have} exactly three items ({limit}% allowed)"
 
 how_to_fix:
   ja: 数を合わせるために足した項目を消してください。2 つで足りるなら 2 つで。
@@ -22,4 +22,4 @@ how_to_fix:
 
 levels: { strict: 50, normal: 70, relaxed: 90 }
 
-use_for: [blog]
+use_for: [blog, legal, docs, academic, literature, speech]

package/rules/sasete-itadaku.yaml

@@ -1,7 +1,7 @@
 id: sasete-itadaku
 layer: L3
 status: experimental
-how_to_find: phrase-match
+how_to_find: phrase-count
 word_list: sasete-itadaku
 uses: [pos]
 languages: [ja]
@@ -17,7 +17,7 @@ why:
 
 message:
   ja: 「{matched}」が文書内に {count} 回あります（{limit} 回まで）
-  en: '"{matched}" appears {count} times in this document (limit {limit})'
+  en: '"{matched}" appears {count} {count|time|times} in this document (limit {limit})'
 
 how_to_fix:
   ja: 主語を立てて言い切ってください。「検討させていただきます」を「来週までに結論を出します」に。
@@ -25,4 +25,4 @@ how_to_fix:
 
 levels: { strict: 1, normal: 3, relaxed: 6 }
 
-use_for: [business, blog]
+use_for: [business, blog, legal, docs, academic, literature, speech]

package/rules/section-length-uniformity.yaml

@@ -22,4 +22,4 @@ how_to_fix:
 
 levels: { strict: 45, normal: 35, relaxed: 25 }
 
-use_for: [blog]
+use_for: [blog, legal, docs, academic, literature, speech]

package/rules/sentence-initial-conjunction-run.yaml

@@ -16,7 +16,7 @@ why:
 
 message:
   ja: 接続詞で始まる文が {count} 文続いています（{limit} 文まで）
-  en: "{count} sentences in a row open with a conjunction (limit {limit})"
+  en: "{count} {count|sentence|sentences} in a row {count|opens|open} with a conjunction (limit {limit})"
 
 how_to_fix:
   ja: どれか 1 つを残して、他は前の文に繋ぐか独立させてください。
@@ -24,4 +24,4 @@ how_to_fix:
 
 levels: { strict: 1, normal: 2, relaxed: 4 }
 
-use_for: [blog, business]
+use_for: [blog, business, legal, docs, academic, literature, speech]

package/rules/sentence-rhythm.yaml

@@ -27,4 +27,4 @@ levels:
   normal: 30
   relaxed: 20
 
-use_for: [blog]
+use_for: [blog, legal, docs, academic, literature, speech]

package/rules/taigen-dome-in-prose.yaml

@@ -16,7 +16,7 @@ why:
 
 message:
   ja: 本文に体言止めが {count} 文あります（{limit} 文まで）
-  en: "{count} sentences end on a noun in the body text (limit {limit})"
+  en: "{count} {count|sentence|sentences} {count|ends|end} on a noun in the body text (limit {limit})"
 
 how_to_fix:
   ja: 述語を足してください。「〜が課題。」を「〜が課題です。」に。
@@ -24,4 +24,4 @@ how_to_fix:
 
 levels: { strict: 2, normal: 4, relaxed: 8 }
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/title-case-consistency.yaml

@@ -23,4 +23,4 @@ how_to_fix:
 
 levels: { strict: 3, normal: 2, relaxed: 1 }
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/total-mismatch.yaml

@@ -23,4 +23,4 @@ how_to_fix:
 
 levels: { strict: 1, normal: 1, relaxed: 1 }
 
-use_for: [business, technical, blog]
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]

package/rules/undefined-acronym.yaml

@@ -30,12 +30,12 @@ why:
 
 message:
   ja: 「{word}」が説明なしで使われています（説明のない略語 {count} 個）
-  en: '"{word}" is used without an expansion ({count} such acronyms)'
+  en: '"{word}" is used without an expansion ({count} such {count|acronym|acronyms})'
 
 how_to_fix:
-  ja: 初出のところで括弧に入れて展開してください。「CI（継続的インテグレーション）」のように。
-  en: Expand it in brackets at first use.
+  ja: 初出のところで括弧に入れて展開してください。「CI（継続的インテグレーション）」のように。読み手が名前として知っている略語（社名など）なら、chaff.yaml の names に並べると求めません。
+  en: Expand it in brackets at first use. If your readers know it as a name (a company, say), list it under names in chaff.yaml and it is not asked for.
 
 levels: { strict: 1, normal: 3, relaxed: 6 }
 
-use_for: [business, technical]
+use_for: [business, technical, legal, docs, academic, literature, speech]

package/rules/unqualified-superlative.yaml

@@ -17,7 +17,7 @@ why:
 
 message:
   ja: 「{matched}」に比べる相手がありません（そういう言い方が {count} 箇所）
-  en: '"{matched}" has nothing to compare against ({count} such claims)'
+  en: '"{matched}" has nothing to compare against ({count} such {count|claim|claims})'
 
 how_to_fix:
   ja: 比較対象か条件を添えてください。「社内の 3 案のうち最も速い」のように。
@@ -25,4 +25,4 @@ how_to_fix:
 
 levels: { strict: 1, normal: 2, relaxed: 4 }
 
-use_for: [business, blog]
+use_for: [business, blog, legal, docs, academic, literature, speech]

package/skills/chaff/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: chaff
-description: "Check prose with chaff (npx chaffjs): run it on Markdown or text, read each finding, fix the text or record why not, and tune chaff.yaml with rules --json and relax --why. Use when asked to lint, proofread or tighten documents, or to set up a team's writing rules."
+description: "Check prose with chaff (npx chaffjs): pick the genre preset for the kind of document (contract, statute, manual, FAQ, paper, fiction, transcript…), run it on Markdown or text, read each finding, fix the text or record why not, and tune chaff.yaml with rules --json and relax --why. Use when asked to lint, proofread or tighten documents, or to set up a team's writing rules."
 ---
 
 # Checking writing with chaff
@@ -9,12 +9,30 @@ chaff finds what makes writing hard to read — long sentences, padding, mixed s
 contract — and never rewrites anything. Reading the findings and changing the text is your part. Japanese and
 English documents both work; the language is detected per file.
 
+## Pick the genre first
+
+A genre is a preset for one kind of document: which rules run, where their limits are, and how the document is
+read. A contract checked as a blog post gets wrong findings, so choose the genre before reading any finding.
+
+1. Name the kind from the document itself. `npx chaffjs genres` lists every genre with what it is for:
+   `legal/contract`, `legal/statute`, `docs/manual`, `docs/faq`, `academic/paper`, `literature/fiction`,
+   `speech/transcript`, `business/report`, `technical/spec`, …
+2. Unsure? Run once without `--genre`. When the file looks like another kind, the line under the header says so
+   (`Looks like: Contract and terms. Try --genre legal/contract`); use that genre if it fits.
+3. Run with it: `npx chaffjs --genre legal/contract contract.md`. For a folder of one kind,
+   `npx chaffjs init --genre legal/contract` writes it into `chaff.yaml` (always pass `--genre`: without it,
+   `init` asks at a terminal).
+4. The header's first line shows the genre used and where it came from. Check it before trusting the findings.
+
+A rule the genre turns off is listed under "did not run" with the genre as the reason. That is the preset's
+choice, not a gap; turn it back on (`rules:` in `chaff.yaml`) only when the person asks.
+
 ## Run it
 
 ```sh
-npx chaffjs <file|dir|glob>...     # human-readable, one block per finding (a folder or glob picks up .md / .markdown / .mdx; name a .txt file directly)
-npx chaffjs . --compact            # two lines per finding: line:col severity message, then the rule id
-npx chaffjs <file> --experimental  # also the experimental rules
+npx chaffjs --genre <genre> <file|dir|glob>...   # human-readable, one block per finding (a folder or glob picks up .md / .markdown / .mdx; name a .txt file directly)
+npx chaffjs . --compact                          # two lines per finding: line:col severity message, then the rule id
+npx chaffjs <file> --experimental                # also the experimental rules
 ```
 
 A run exits 1 when a finding is an `error`. It also exits 1 when it could not check anything: no file to
@@ -39,15 +57,16 @@ relaxing a rule.
 
 ## Tune chaff.yaml
 
-- `npx chaffjs init` writes a commented `chaff.yaml` when there is none (an existing one is left as it is), and
-  adds `.chaff-cache/` and `.env*` to `.gitignore`.
-- `npx chaffjs rules --json` prints every rule with its levels, the setting in effect (`now`) and why a rule is
-  off. Read it instead of guessing rule names or limits.
+- `npx chaffjs init --genre <genre>` writes a commented `chaff.yaml` for that genre when there is none (an
+  existing one is left as it is), and adds `.chaff-cache/` and `.env*` to `.gitignore`.
+- `npx chaffjs rules --json [--genre <genre>]` prints every rule with its levels, the setting in effect (`now`,
+  the genre's preset included) and why a rule is off. Read it instead of guessing rule names or limits.
 - A level is `strict` / `normal` / `relaxed` / `off`; when even `relaxed` is too tight, a positive number is the
   limit itself (`max-sentence-length: 260`).
 - `prefer:` maps spellings to the team's (`e-mail: email`); `preferred-term: normal` turns the rule on.
 - Unknown rule names and unreadable values are reported on stderr — read stderr after editing `chaff.yaml`.
-- `genre:` sets the kind of document (`npx chaffjs genres` lists them); `--genre` overrides it for one run.
+- `genre:` sets the kind of document; `by_path` sets one per folder; `--genre` overrides both for one run.
+  `rules:` wins over the genre's preset.
 
 ## Structured documents
 

package/src/address-chain.ts

@@ -78,7 +78,7 @@ const chainAt = (patterns: Compiled, text: string, start: number): { readonly sp
   const firstEnd = matchEnd(patterns.address, text, start);
   if (firstEnd === undefined) return undefined;
   const { spans, cuts } = readChain(patterns, text, { start, end: firstEnd });
-  const cut = [...cuts].reverse().find((candidate) => endsHere(patterns, text, candidate.end));
+  const cut = cuts.findLast((candidate) => endsHere(patterns, text, candidate.end));
   return cut === undefined ? undefined : { spans: spans.slice(0, cut.addresses), end: cut.end };
 };
 

package/src/backends/anthropic.ts

@@ -4,6 +4,7 @@ import { join } from "node:path";
 import Anthropic from "@anthropic-ai/sdk";
 import { toFailure } from "./types.ts";
 import type { Failure, Judge, Prompt } from "./types.ts";
+import type { Texts } from "../ui.ts";
 
 type AnthropicResponse = { readonly content: readonly { readonly type: string; readonly text?: string | undefined }[] };
 
@@ -58,4 +59,7 @@ export const judge =
   };
 
 /** 認証が無いときに人へ見せる案内。 */
-export const SETUP_HINT = "ANTHROPIC_API_KEY を設定するか、ant auth login を実行してください。";
+export const SETUP_HINT: Texts<string> = {
+  ja: "ANTHROPIC_API_KEY を設定するか、ant auth login を実行してください。",
+  en: "Set ANTHROPIC_API_KEY, or run ant auth login.",
+};

package/src/backends/openai.ts

@@ -1,6 +1,7 @@
 import OpenAI from "openai";
 import { toFailure } from "./types.ts";
 import type { Failure, Judge, Prompt } from "./types.ts";
+import type { Texts } from "../ui.ts";
 
 type OpenAIResponse = { readonly choices: readonly { readonly message: { readonly content: string | null } }[] };
 
@@ -43,4 +44,4 @@ export const judge =
     return body;
   };
 
-export const SETUP_HINT = "OPENAI_API_KEY を設定してください。";
+export const SETUP_HINT: Texts<string> = { ja: "OPENAI_API_KEY を設定してください。", en: "Set OPENAI_API_KEY." };

package/src/backends/types.ts

@@ -17,11 +17,12 @@ const BACKENDS: readonly BackendName[] = ["anthropic", "openai"];
 export const isBackend = (value: unknown): value is BackendName => BACKENDS.some((name) => name === value);
 
 /** API が返した失敗。生のスタックトレースを人に見せないための、最小の分類。 */
-export type Failure = { readonly kind: "auth" | "quota" | "api"; readonly status: number | undefined; readonly message: string };
+/** message is the provider's own words, undefined when it gave none: the screen says so in the reader's language. */
+export type Failure = { readonly kind: "auth" | "quota" | "api"; readonly status: number | undefined; readonly message: string | undefined };
 
 const statusOf = (value: unknown): number | undefined => (typeof value === "number" ? value : undefined);
 
-const messageOf = (value: unknown): string => (typeof value === "string" && value.length > 0 ? value : "原因は返ってきませんでした");
+const messageOf = (value: unknown): string | undefined => (typeof value === "string" && value.length > 0 ? value : undefined);
 
 const kindOf = (status: number | undefined): Failure["kind"] => {
   if (status === 401 || status === 403) return "auth";

package/src/baseline.ts

@@ -29,7 +29,7 @@ export const readBaseline = (path: string): Baseline | undefined => {
 };
 
 export const writeBaseline = (path: string, entries: readonly string[]): void => {
-  const sorted = [...entries].sort((left, right) => left.localeCompare(right, "en"));
+  const sorted = entries.toSorted((left, right) => left.localeCompare(right, "en"));
   const body = { version: 1, created: new Date().toISOString().slice(0, 10), entries: sorted };
   writeFileSync(path, `${JSON.stringify(body, null, 2)}\n`, "utf8");
 };