chaffjs 0.19.0 → 0.20.0

package/rules/unit-mismatch.yaml

@@ -0,0 +1,110 @@
+id: unit-mismatch
+layer: L3
+status: experimental
+how_to_find: unit-mismatch
+requires: [quantities]
+uses: [pos]
+severity: warning
+
+name:
+  ja: 同じ項目の量を違う単位で書いて、換算すると合わない
+  en: One item given in two units that do not convert
+
+why:
+  ja: 「距離：5 km」と「距離：3000 m」のように、同じ項目の量を違う単位で書くと、読み手は換算してどちらが正しいかを確かめることになります。片方の単位を書き換えたときに、数を直し忘れると起きます。「項目：量」「項目は量です」と書いた所と表の升を読み、同じ節の同じ項目で単位の違う量（長さ、重さ、時間、体積、データの量）を換算して比べます。丸めた書き方（1 mile と 1.6 km）は、2% までの差なら合っているとみなします。
+  en: 'When one item is given as "Distance: 5 km" and later "Distance: 3000 m", the reader has to convert to find out which is right. It happens when the unit of one is rewritten and its number is not. Values written as "Item: value" or "The item is value", and table cells, are read; within one section, the same item in two different units (of length, mass, time, volume or data) is converted and compared. A rounded figure (1 mile and 1.6 km) agrees when the difference is within 2%.'
+
+message:
+  ja: "「{label}」が {value} と書かれていますが、同じ節の前の所では {other} で、換算すると合いません"
+  en: '"{label}" is {value} here, but {other} earlier in the same section, and they do not convert'
+
+how_to_fix:
+  ja: どちらの量が正しいかを確かめて、もう一方を換算して直してください。一つの文書では、同じ項目の単位を揃えると読み手が比べやすくなります。
+  en: Check which value is right and convert the other to match. Using one unit for an item throughout a document makes it easier to compare.
+
+levels: { normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: facts
+summary:
+  ja: 同じ項目の量を、違う単位で書いて換算すると合わない所（距離：5 km と 3000 m）
+  en: 'The same item given in two units that do not convert ("Distance: 5 km" and "3000 m")'
+example:
+  ja:
+    before: |
+      距離：5 km
+
+      - 集合：駅前
+      - 距離：3000 m
+    after: |
+      距離：5 km
+
+      - 集合：駅前
+      - 距離：5000 m
+  en:
+    before: |
+      Distance: 5 km
+
+      - Start: the station
+      - Distance: 3000 m
+    after: |
+      Distance: 5 km
+
+      - Start: the station
+      - Distance: 5000 m
+
+not_flagged:
+  ja: 単位が同じ量（食い違いは fact-conflict が見ます）、種類の違う量（長さと重さ）、違う見出しや違う親の項目の下の量、2% までの差は見ません。GB や MB は 1000 倍でも 1024 倍でも合えば合うとみなします。
+  en: Values in the same unit (fact-conflict looks at those), of different kinds (a length and a mass), under different headings or parent items, and differences within 2% are left alone. GB and MB agree when they match at either 1000 or 1024.
+rewrite:
+  ja:
+    direction: 二つの量のどちらが正しいかを書き手に確かめ、もう一方を換算して直してください。どちらが正しいか文書から決まらないときは、推測で選ばずに書き手に聞いてください。
+    pairs:
+      - before: |
+          距離：5 km
+          （中略）
+          距離：3000 m
+        after: |
+          距離：5 km
+          （中略）
+          距離：5000 m
+      - before: |
+          所要時間は90分です。
+          （中略）
+          所要時間は2時間です。
+        after: |
+          所要時間は90分です。
+          （中略）
+          所要時間は1.5時間です。
+    keep:
+      - 確かめた量
+      - 単位の揃え方
+    avoid:
+      - どちらが正しいかを推測で決める
+      - 換算した数を、元の量より細かい桁で書く
+  en:
+    direction: Ask the writer which value is right, and convert the other to match. If the document does not settle it, ask rather than guess.
+    pairs:
+      - before: |
+          Distance: 5 km
+          (…)
+          Distance: 3000 m
+        after: |
+          Distance: 5 km
+          (…)
+          Distance: 5000 m
+      - before: |
+          The session is 90 minutes.
+          (…)
+          The session is 2 hours.
+        after: |
+          The session is 90 minutes.
+          (…)
+          The session is 1.5 hours.
+    keep:
+      - the value confirmed as right
+      - one unit for the item
+    avoid:
+      - guessing which value is right
+      - writing the converted value with more precision than the original

package/rules/unknown-word.yaml

@@ -0,0 +1,62 @@
+id: unknown-word
+layer: L2
+status: experimental
+how_to_find: unknown-word
+languages: [en]
+severity: info
+
+name:
+  ja: 辞書に無い語（綴りの誤りの候補）
+  en: Word not in the dictionary
+
+why:
+  ja: 英語の語のうち辞書に無く、一字違いの辞書の語があるもの（attched と attached）は、打ち間違いのことが多いです。chaff は英語のアダプタが持つ辞書（wink-lexicon と WordNet から作った語の一覧）で語を引き、語尾（-ed、-ing）と接頭辞（un-、re-）を外しても辞書に無い語だけを候補にします。大文字を含む語（固有名詞・略語）、コードと URL の中の語、文書で二度以上使う語（その文書の用語のことが多い）、一字違いの辞書の語が無い語は指しません。チームの言葉は chaff.yaml の names に足すと指さなくなります。
+  en: An English word that is not in the dictionary but is one letter away from a word that is ("attched" and "attached") is usually a typo. chaff looks words up in the English adapter's dictionary (a word list built from wink-lexicon and WordNet), after taking off endings (-ed, -ing) and prefixes (un-, re-). Words with a capital letter (names, acronyms), words in code and URLs, words used twice or more in the document (usually its own terms), and words with no dictionary word one letter away are not reported. Add a team's own words to names in chaff.yaml.
+
+message:
+  ja: 「{word}」は辞書にありません。「{suggestion}」の打ち間違いではありませんか
+  en: '"{word}" is not in the dictionary; did you mean "{suggestion}"?'
+
+how_to_fix:
+  ja: 打ち間違いなら直してください。正しい語なら、chaff.yaml の names に足してください。
+  en: If it is a typo, correct it. If the word is right, add it to names in chaff.yaml.
+
+placeholders:
+  word:
+    ja: 語
+    en: the word
+  suggestion:
+    ja: 辞書の語
+    en: a dictionary word
+
+levels: { strict: warning, normal: info, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: slips
+summary:
+  en: An English word that is not in the dictionary and is one letter away from one that is, such as "attched"
+  ja: 辞書に無く、一字違いの辞書の語がある英語の語（attched）
+example:
+  en:
+    before: |
+      The report is attched to this email.
+    after: |
+      The report is attached to this email.
+
+not_flagged:
+  ja: 大文字を含む語、四字より短い語、コード・URL・メールアドレスの中の語、文書で二度以上使う語、一字違いの辞書の語が無い語、chaff.yaml の names に並べた語、語彙表 known-misspelling が別に言う語は指しません。
+  en: Words with a capital letter, words shorter than four letters, words in code, URLs and email addresses, words used twice or more in the document, words with no dictionary word one letter away, words listed under names in chaff.yaml, and the misspellings known-misspelling reports are not reported.
+rewrite:
+  en:
+    direction: If the flagged word is a typo, replace it with the suggested dictionary word, or another word the sentence means. If it is a real word or a name, leave it and add it to names in chaff.yaml.
+    pairs:
+      - before: The thresholds were recalibrated and the pipline restarted.
+        after: The thresholds were recalibrated and the pipeline restarted.
+      - before: The report is attched to this email.
+        after: The report is attached to this email.
+    keep:
+      - the wording around the word
+      - names and terms that are spelled that way on purpose
+    avoid:
+      - replacing a correct technical term with the dictionary's nearest word

package/rules/vague-link-text.yaml

@@ -0,0 +1,77 @@
+id: vague-link-text
+layer: L1
+status: experimental
+how_to_find: vague-link-text
+word_list: vague-link-text
+requires: [markdown]
+severity: warning
+
+name:
+  ja: 行き先を言わないリンクの言葉
+  en: Link text that does not say where it goes
+
+why:
+  ja: 「[こちら](…)」「[ここをクリック](…)」のように、リンクの言葉がそれだけでは行き先を言わないと、読み手はリンクの前後を読み直して行き先を推し量ることになります。画面読み上げはリンクだけを並べて読み上げるので、「こちら、こちら、こちら」と聞こえ、どれがどこへ行くのか分かりません（WCAG 2.4.4 リンクの目的）。言葉全体が語彙表の語（こちら、ここ、詳細、click here、read more）のときだけを指し、行き先を言っている言葉（「料金表はこちら」）は指しません。
+  en: Link text such as "click here" or "read more" says nothing about where the link goes, so the reader has to reread the sentence around it. A screen reader can list the links on their own, and then hears "here, here, here" with no way to tell them apart (WCAG 2.4.4, link purpose). Only link text that is wholly a word from the lexicon (here, click here, read more, こちら) is reported; text that names the target ("the pricing page") is not.
+
+message:
+  ja: リンクの言葉「{text}」は、行き先を言っていません
+  en: 'The link text "{text}" does not say where it goes'
+
+how_to_fix:
+  ja: 行き先の名前をリンクの言葉にしてください（「料金は[こちら](…)」→「[料金表](…)を見てください」）。
+  en: Make the name of the target the link text ("click [here](…) for pricing" → "see the [pricing page](…)").
+
+placeholders:
+  text:
+    ja: リンクの言葉
+    en: the link text
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: structure
+summary:
+  ja: 「[こちら](…)」「[ここをクリック](…)」のように、言葉だけでは行き先の分からないリンク
+  en: A link whose whole text is "here", "click here" or "read more"
+example:
+  ja:
+    before: |
+      料金の一覧は[こちら](https://example.com/pricing)です。
+    after: |
+      料金は[料金表](https://example.com/pricing)にあります。
+  en:
+    before: |
+      For prices, click [here](https://example.com/pricing).
+    after: |
+      Prices are on the [pricing page](https://example.com/pricing).
+
+not_flagged:
+  ja: 言葉の一部に「こちら」を含むだけのリンク（「料金表はこちら」）、URL をそのまま書いたリンク、参照の形のリンク（[こちら][1]）は指しません。Markdown でない文書と、引用（>）とコードの中のリンクも見ません。
+  en: Link text that only contains such a word ("pricing here"), a bare or angle-bracket URL, and reference-style links ([here][1]) are not reported, nor are links in a quotation (>), in code, or in a document that is not Markdown.
+rewrite:
+  ja:
+    direction: リンクの言葉を、行き先の名前（ページの題、資料の名前）に変えてください。「こちら」「ここ」は文から外し、文は行き先の名前を言う形に組み直します。行き先の URL は変えません。
+    pairs:
+      - before: 料金の一覧は[こちら](https://example.com/pricing)です。
+        after: 料金は[料金表](https://example.com/pricing)にあります。
+      - before: 申請の手順は[ここをクリック](https://example.com/apply)してください。
+        after: 申請の手順は[申請の手引き](https://example.com/apply)にあります。
+    keep:
+      - リンクの行き先（URL）
+      - 文の言っていること
+    avoid:
+      - 行き先の名前を推し量って、URL の中身と違う名前を付ける
+  en:
+    direction: Make the name of the target (the page title or the document's name) the link text. Drop "here" and "click", and recast the sentence around the name. Keep the URL.
+    pairs:
+      - before: For prices, click [here](https://example.com/pricing).
+        after: Prices are on the [pricing page](https://example.com/pricing).
+      - before: To apply, [read more](https://example.com/apply).
+        after: To apply, follow the [application guide](https://example.com/apply).
+    keep:
+      - the link target (the URL)
+      - what the sentence says
+    avoid:
+      - guessing a name the target page does not have

package/rules/vague-word-density.yaml

@@ -0,0 +1,89 @@
+id: vague-word-density
+layer: L2
+status: experimental
+how_to_find: vague-density
+word_list: vague-word
+uses: [pos]
+severity: info
+
+name:
+  ja: あいまいな語が多い
+  en: Too many vague words
+
+why:
+  ja: 「適宜」「適切に」「必要に応じて」「なるべく」は、どこまで・いつまで・何をしたら済むのかを読み手に決めさせます。一つ二つは普通の言い方ですが、重なると、文書の言っていることの多くを読み手が埋めることになり、人によって読み方が変わります。ISO/IEC/IEEE 29148 が要求の文で避ける語として挙げる言い方と同じ種類です。文書の長さに対して多いときだけ指します。語の一覧は言語ごとの語彙表にあります。
+  en: '"As appropriate", "as needed", "reasonable" and "in a timely manner" leave the reader to decide how far, how soon and what counts as done. One or two are ordinary; many leave much of the document to the reader, and two readers will fill it in differently. ISO/IEC/IEEE 29148 lists the same kind of word among those a requirement avoids. chaff speaks only when they are dense for the document''s length. The words are listed in each language''s lexicon.'
+
+message:
+  ja: 「{matched}」など、あいまいな語が 1000 字あたり {density} 個あります（{limit} 個まで）
+  en: '"{matched}" and other vague words: {density} per 1000 words (limit {limit})'
+
+how_to_fix:
+  ja: 大事なところから、何を・どこまで・いつまでを書いてください。「適宜報告する」は「毎週金曜に報告する」、「必要に応じて」は、どんなときに必要なのかを書きます。
+  en: 'Where it matters, say what, how far and by when: "report as needed" becomes "report every Friday", and "as appropriate" names the case.'
+
+placeholders:
+  matched:
+    ja: 見つけたあいまいな語の一つ
+    en: one of the vague words found
+
+# 日本語は 1000 字、英語は 1000 語あたり。英語の 1000 語は日本語の 1000 字よりずっと長い。
+levels:
+  ja: { strict: 1, normal: 2, relaxed: 4 }
+  en: { strict: 2, normal: 4, relaxed: 8 }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: wording
+summary:
+  ja: 「適宜」「適切に」「必要に応じて」のように、どこまで・いつまでを読み手に決めさせる語が、文書の長さに対して多い所
+  en: Vague words ("as appropriate", "as needed", "in a timely manner"), many for the document's length
+example:
+  ja:
+    pad: true
+    before: |
+      障害が起きたら適宜報告し、必要に応じて関係者に連絡してください。復旧後は適切に記録を残し、なるべく早めに再発防止策をまとめます。
+    after: |
+      障害が起きたら 30 分以内に報告し、影響のある部署に連絡してください。復旧後は障害票に記録を残し、翌営業日までに再発防止策をまとめます。
+  en:
+    pad: true
+    before: |
+      Report incidents as needed and notify the appropriate people in a timely manner. Keep adequate records and fix the cause where possible.
+    after: |
+      Report an incident within 30 minutes and notify the affected teams. Record it in the incident log and fix the cause by the next working day.
+
+not_flagged:
+  ja: 文書の長さに対して少ないものは指しません。短すぎる文書も測りません。要求の文の中の「可能な限り」「必要に応じて」は、要求の書き方として requirement-smell も見ます。
+  en: A few vague words for the document's length are not reported, and very short documents are not measured. Inside a requirement, requirement-smell also reads "where possible" and "as needed".
+level_meaning:
+  ja: 1000 字あたりあいまいな語 {limit} 個まで
+  en: up to {limit} vague words per 1000 words
+rewrite:
+  ja:
+    direction: あいまいな語を、何を・どこまで・いつまでに置き換えてください。決まっていないなら、決まっていないことと、誰が決めるのかを書きます。
+    pairs:
+      - before: 障害が起きたら適宜報告してください。
+        after: 障害が起きたら 30 分以内に報告してください。
+      - before: 必要に応じて関係者に連絡します。
+        after: 顧客に影響があるときは、営業部に連絡します。
+      - before: なるべく早めに対応します。
+        after: 今週中に対応します。
+    keep:
+      - 書き手が約束している範囲（約束していない期限を足さない）
+      - 依頼の相手と中身
+    avoid:
+      - 書き手の知らない数字や期限を作る
+      - あいまいな語を別のあいまいな語（随時、しかるべく）に替える
+  en:
+    direction: Replace each vague word with what, how far or by when. If it is not decided, say so and say who decides.
+    pairs:
+      - before: Report incidents as needed.
+        after: Report every incident within 30 minutes.
+      - before: Notify the appropriate people in a timely manner.
+        after: Notify the on-call engineer within an hour.
+    keep:
+      - what the writer actually commits to (do not invent a deadline)
+      - who is asked and what
+    avoid:
+      - making up numbers or deadlines the writer does not know
+      - swapping one vague word for another ("promptly", "as required")

package/rules/very-adjective.yaml

@@ -0,0 +1,61 @@
+id: very-adjective
+layer: L2
+status: experimental
+how_to_find: intensified-adjective
+word_list: very-intensifier
+extra_word_lists: [very-exception]
+requires: [pos]
+languages: [en]
+severity: info
+
+name:
+  ja: 「very + 形容詞」の多用
+  en: Too many "very" + adjective
+
+why:
+  ja: 英語の「very important」「very good」は、強い一語（critical、excellent）か、何がどうなのかを言えば要らない語です。一つ二つなら普通ですが、文書の長さのわりに多いと、どの「very」も効かなくなります。「the very first」「very few」のように意味の決まった言い方は語彙表で除いています。
+  en: '"Very important" and "very good" lean on "very" where a stronger word (critical, excellent), or saying what and how much, would do. One or two are ordinary; many for the length make every "very" weightless. Set phrases such as "the very first" and "very few" are excepted in the lexicon.'
+
+message:
+  ja: 「{matched}」など、very + 形容詞が 1000 語あたり {density} 個あります（{limit} 個まで）
+  en: '"{matched}" and other "very" + adjective: {density} per 1000 words (limit {limit})'
+
+how_to_fix:
+  ja: 強い一語に替えるか、何がどの程度なのかを書いてください（very important → critical、very fast → under a second）。
+  en: Use a stronger word, or say what and how much ("very important" → "critical", "very fast" → "under a second").
+
+levels: { strict: 1, normal: 2, relaxed: 4 }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: wording
+summary:
+  ja: 英語で、「very important」「very good」のような very + 形容詞が、文書の長さのわりに多い所
+  en: '"Very" + adjective, such as "very important", dense for the document''s length'
+example:
+  en:
+    pad: true
+    before: |
+      The launch was very important. The team was very busy, and the plan was very good.
+    after: |
+      The launch was critical. The team was stretched, and the plan held.
+
+not_flagged:
+  ja: 「very」の後ろが形容詞のときだけ数えます（very well は数えない）。「the very first」「very few」「very much」は数えません。短い文書は密度を測りません。小説と話し言葉では既定で止めています（会話の言葉のため）。
+  en: Only "very" before an adjective ("very well" is not counted), and not "the very first", "very few" or "very much". Short documents are not measured. The fiction and speech presets turn it off, since dialogue speaks that way.
+level_meaning:
+  ja: very + 形容詞が 1000 語あたり {limit} 個まで
+  en: up to {limit} "very" + adjective per 1000 words
+rewrite:
+  en:
+    direction: Replace "very" + adjective with a stronger single word, or with what the text says about how much. If the text says nothing more, a plain adjective without "very" will do.
+    pairs:
+      - before: The launch was very important.
+        after: The launch was critical.
+      - before: The new build is very fast.
+        after: The new build starts in under a second.
+    keep:
+      - the claim each sentence makes
+    avoid:
+      - swapping "very" for another intensifier ("really", "extremely")
+      - inventing figures the text does not give

package/rules/weasel-word.yaml

@@ -0,0 +1,60 @@
+id: weasel-word
+layer: L2
+status: experimental
+how_to_find: phrase-match
+word_list: weasel-word
+requires: [pos]
+languages: [en]
+severity: info
+
+name:
+  ja: 出所を言わない「多くの専門家」
+  en: Weasel words
+
+why:
+  ja: 英語の「many experts say」「it is widely believed」「studies show」は、主張を名前の無い大勢や、どれとも言わない研究に預けます。読み手は誰がそう言ったのかを確かめられず、書き手は主張に責任を持たずに済みます。言い回しは言語ごとの語彙表にあります。
+  en: '"Many experts say", "it is widely believed" and "studies show" lend a claim to an unnamed crowd or to research no one names. The reader cannot check who said it, and the writer need not stand behind it. The phrases are listed in the lexicon.'
+
+message:
+  ja: 「{matched}」は、誰が言ったのかを言っていません
+  en: '"{matched}" does not say who'
+
+how_to_fix:
+  ja: 誰が・どの研究がそう言ったのかを書いてください（名前、年、出典）。書けないなら、書き手自身の主張として書くか、その文を落としてください。
+  en: Name who said it or which study shows it (a name, a year, a source). If you cannot, state it as your own claim, or drop it.
+
+levels: { strict: 1, normal: 1, relaxed: 2 }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: wording
+summary:
+  ja: 英語で、「many experts say」「studies show」のように、主張を名前の無い誰かに預ける言い回し
+  en: Phrases such as "many experts say" and "studies show" that credit a claim to no one in particular
+example:
+  en:
+    before: |
+      Many experts say remote work raises output.
+    after: |
+      A 2023 Stanford study of 1,600 staff found remote work raised output by 4%.
+
+not_flagged:
+  ja: 一覧にある言い回しだけを見ます。英語の文書だけで動きます。すぐ後ろに出典が書いてあっても指摘します（文の中で研究の名前を言えるため）。
+  en: Only the phrases on chaff's list are checked, and only in English documents. A citation right after the phrase does not silence it, since the sentence can name the study itself.
+level_meaning:
+  ja: 当てはまる言い回しが {limit} 箇所あれば指摘
+  en: reported once there are {limit}
+rewrite:
+  en:
+    direction: Replace the unnamed crowd ("many experts", "studies") with the person or study the text or its sources name. If they name none, do not invent one; ask the writer, or state the claim as the writer's own.
+    pairs:
+      - before: Studies show that short meetings save time [3].
+        after: Smith (2021) found that 15-minute meetings saved each team two hours a week [3].
+      - before: It is widely believed that the old API is slower.
+        after: Our load test in May found the old API 30% slower.
+    keep:
+      - the citation number or link
+      - the claim itself
+    avoid:
+      - inventing a study or a name the text does not give
+      - swapping one unnamed crowd for another ("some researchers")

package/rules/wordy-phrase.yaml

@@ -0,0 +1,61 @@
+id: wordy-phrase
+layer: L2
+status: experimental
+how_to_find: phrase-match
+word_list: wordy-phrase
+requires: [pos]
+languages: [en]
+severity: info
+
+name:
+  ja: 回りくどい言い回し
+  en: Wordy phrase
+
+why:
+  ja: 英語の「in order to」「due to the fact that」「at this point in time」は、「to」「because」「now」と同じことを何語もかけて言います。読み手は語を多く読むだけで、得るものは増えません。言い回しと短い形の組は言語ごとの語彙表にあります。契約や法令がわざと使う言い方（with regard to、prior to）は入れていません。
+  en: '"In order to", "due to the fact that" and "at this point in time" say in several words what "to", "because" and "now" say in one. The reader reads more and learns nothing more. The phrases and their short forms are listed in the lexicon. Phrases that contracts and statutes use on purpose ("with regard to", "prior to") are left out.'
+
+message:
+  ja: 「{matched}」は、もっと短く言えます
+  en: '"{matched}" can be said in fewer words'
+
+how_to_fix:
+  ja: 短い形に置き換えてください（in order to → to、due to the fact that → because、in the event that → if）。
+  en: Use the short form ("in order to" → "to", "due to the fact that" → "because", "in the event that" → "if").
+
+# 指摘に要る文の数。1 つなら書き手の癖とは言えないので、2 つから。
+levels: { strict: 1, normal: 2, relaxed: 4 }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: wording
+summary:
+  ja: 英語で、「in order to」「due to the fact that」のように、一語で言えることを何語もかけて言う所
+  en: Phrases such as "in order to" and "due to the fact that" that take several words to say what one says
+example:
+  en:
+    before: |
+      In order to save time, we met online. Due to the fact that the room was booked, we stayed home.
+    after: |
+      To save time, we met online. Because the room was booked, we stayed home.
+
+not_flagged:
+  ja: 一覧にある言い回しだけを見ます。英語の文書だけで動きます。契約や法令がわざと使う言い方（with regard to、prior to、in accordance with）は一覧に入れていません。
+  en: Only the phrases on chaff's list are checked, and only in English documents. Phrases that contracts and statutes use on purpose ("with regard to", "prior to", "in accordance with") are not on it.
+level_meaning:
+  ja: 回りくどい言い回しを含む文が {limit} 文あれば指摘
+  en: reported once {limit} sentences hold one
+rewrite:
+  en:
+    direction: Replace the wordy phrase with its short form from the lexicon. Leave the rest of the sentence alone.
+    pairs:
+      - before: In order to ship on Friday, we froze the code on Monday.
+        after: To ship on Friday, we froze the code on Monday.
+      - before: The launch slipped due to the fact that the vendor was late.
+        after: The launch slipped because the vendor was late.
+      - before: In the event that the server fails, the job retries.
+        after: If the server fails, the job retries.
+    keep:
+      - the rest of the sentence and what it says
+    avoid:
+      - rewriting the rest of the sentence while shortening the phrase

package/skills/chaff/SKILL.md

@@ -115,6 +115,8 @@ read it as data). It prints, in the document's language:
 - the constraints: keep facts, numbers, conditions and names; add no fact; ask the writer instead of inventing a
   specific; two passes at most;
 - the recommended mode and why, and the document-level signals with the outline's numbers;
+- the structure targets: the structure score (how many structure measures lie past 90% of human articles) and, for
+  each measure past that line, a target from the human baseline ("fewer headings: N now, M at most for this length");
 - for each rule that fired: its rewrite direction, what to keep, what to avoid, one before/after pair, hints for the
   `ai-tell` phrases found, and the spots (line and sentence);
 - the check commands to run on the rewrite.
@@ -130,7 +132,7 @@ Pick one of three modes and say which.
 | --- | --- | --- |
 | **Light** | only the flagged spots | the content and the structure are fine and only some phrasing is off |
 | **Bold** | each section's prose, keeping the outline | the outline is fixed (a report template, a manual, required sections) |
-| **Full** | the whole document, from scratch | the request says 「全面的に」「一から」「全部書き直して」 / "from scratch" / "rewrite the whole thing"; or the genre is `blog/*` or an essay (`literature/essay`); or `ai-generated-composite` fires |
+| **Full** | the whole document, from scratch | the request says 「全面的に」「一から」「全部書き直して」 / "from scratch" / "rewrite the whole thing"; or the genre is `blog/*` or an essay (`literature/essay`); or `ai-generated-composite` fires; or the plan's structure score reaches its limit |
 
 For a blog or an essay, and whenever `ai-generated-composite` fires, recommend Full. A Light or Bold pass leaves the
 skeleton of generated text: a heading every few paragraphs, bold lead-ins, symmetric sections, a closing まとめ that
@@ -161,7 +163,8 @@ repeats the body. The writer usually wants the structure changed, not only the s
 
 1. **Take inventory before writing.** `npx chaffjs facts <file> --json` lists every fact `compare` will hold you to
    (numbers, dates, times, URLs, code, names, quotations, headings, references, footnotes). `npx chaffjs outline <file>`
-   gives the old outline and its shape. Then write down, one line each, the writer's actual claims and every concrete
+   gives the old outline, its shape and its structure block: each structure measure against human articles, with ✗ on
+   those past 90% of them. Then write down, one line each, the writer's actual claims and every concrete
    experience, example and opinion in the original. This inventory is what you write from; the old sentences are not.
 2. **Throw away the structure.** Decide what the piece is for and who reads it. Choose one angle or story for the
    whole piece, and outline it the way a person would. Do these before writing:
@@ -173,6 +176,9 @@ repeats the body. The writer usually wants the structure changed, not only the s
    - no symmetric three-point sections unless the content really has three parts;
    - move the writer's concrete experience to where it carries the argument;
    - open with the point or a concrete scene, not a generic opener.
+
+   Size the new outline by the plan's structure targets: as many headings as the target allows for this length, no
+   heading split into three unless the content has three parts, no bold-label lists, no closing that restates.
 3. **Show the new outline first.** Put the old outline (headings from `chaff outline`) next to the proposed one:
    headings, and one line per section on what it says. The writer then sees the structural change at a glance. Wait
    for a yes, unless the person asked for it to be done without asking; then go straight on.
@@ -199,8 +205,8 @@ repeats the body. The writer usually wants the structure changed, not only the s
      this one is yours to keep.
 5. **Check.**
    - `npx chaffjs <old> --experimental` and `npx chaffjs <new> --experimental`: the AI signals before and after.
-   - `npx chaffjs outline <old> <new>`: headings, average section length, text in lists, bold, before and after. A
-     restructure shows up here, not only in rule counts.
+   - `npx chaffjs outline <old> <new>`: headings, average section length, text in lists, bold, and the structure score
+     and each structure measure, before and after. A restructure shows up here, not only in rule counts.
    - `npx chaffjs compare <old> <new> --distinct --allow-dropped heading --allow-added heading`: the headings are the
      structure you rebuilt on purpose; every other dropped fact is restored and no other fact is added. A cut まとめ
      restates facts the body still holds, so `--distinct` counts a fact as kept when the new text states it at least
@@ -208,6 +214,8 @@ repeats the body. The writer usually wants the structure changed, not only the s
 6. **Stop** when all of these hold, or after two full passes, whichever comes first:
    - `ai-generated-composite` does not fire;
    - the density rules (`bold-density`, `contrast-framing`, `stock-transition`, `colon-lead-in`) are under their limits;
+   - `chaff outline <old> <new>` shows the new structure score under the plan's limit, with no ✗ left on the measures
+     the plan listed as targets;
    - `compare` is clean, or every exclusion has a stated reason.
 7. **Show** the new text, a short "what changed and why" list, then a table of the signals and the shape before and
    after, taken from chaff's output.
@@ -216,14 +224,14 @@ repeats the body. The writer usually wants the structure changed, not only the s
 
 - a generic opener or closer ("本記事では〜解説します", "いかがでしたでしょうか", "In today's fast-paced world");
 - explaining what every reader already knows;
-- every section the same length and the same shape;
+- every section the same shape (chaff measures the lengths and the heading forms, not what each section does);
 - a list of benefits with no cost or trade-off;
 - no first-hand detail: nothing the writer saw, measured or did;
 - the same enthusiasm everywhere, so nothing stands out;
 - politeness piled on politeness;
 - a definition nobody asked for;
 - headings that are full sentences or slogans;
-- a まとめ / "Conclusion" that repeats the body.
+- a まとめ / "Conclusion" that repeats the body in other words (chaff counts only the repeated wording).
 
 In every mode:
 

package/src/baseline.ts

@@ -1,5 +1,6 @@
 import { createHash } from "node:crypto";
 import { existsSync, readFileSync, writeFileSync } from "node:fs";
+import { posix, relative, resolve, sep } from "node:path";
 import type { Finding } from "./plugin.ts";
 
 export const BASELINE_FILE = ".chaff-baseline.json";
@@ -13,16 +14,28 @@ export const fingerprint = (path: string, finding: Finding): string => {
   return createHash("sha256").update(body).digest("hex").slice(0, 16);
 };
 
+type PathRules = Pick<typeof posix, "relative" | "resolve" | "sep">;
+const NATIVE: PathRules = { relative, resolve, sep };
+
+/**
+ * baseline が覚えるパス。baseline のフォルダからの相対で、区切りはどの OS でも「/」。
+ * OS の区切りのまま覚えると、macOS で書いた baseline が Windows では何も棚上げしない。
+ */
+export const baselinePath = (path: string, folder: string, rules: PathRules = NATIVE): string =>
+  rules.relative(folder, rules.resolve(folder, path)).split(rules.sep).join("/");
+
 /**
  * findings の fingerprint を順に。一つの文から出た指摘は同じ文を引くので、文と rule の組ごとに一度だけ計算する。
  * 長い文に指摘が多いと、指摘ごとに文を読み直すのでは指摘数と文の長さの積になる。
+ * folder は baseline を置くフォルダ。パスはそこからの相対にしてから数える。
  */
-export const fingerprints = (path: string, findings: readonly Finding[]): string[] => {
+export const fingerprints = (path: string, findings: readonly Finding[], folder: string): string[] => {
+  const key = baselinePath(path, folder);
   const known = new Map<string, Map<string, string>>();
   return findings.map((finding) => {
     const byRule = known.get(finding.quote) ?? new Map<string, string>();
     known.set(finding.quote, byRule);
-    const found = byRule.get(finding.rule) ?? fingerprint(path, finding);
+    const found = byRule.get(finding.rule) ?? fingerprint(key, finding);
     byRule.set(finding.rule, found);
     return found;
   });
@@ -52,10 +65,10 @@ export const writeBaseline = (path: string, entries: readonly string[]): void =>
 export type Split = { readonly fresh: readonly Finding[]; readonly shelved: number };
 
 /** baseline にあるものは報告しない。新しく増えたものだけを出す。 */
-export const splitByBaseline = (path: string, findings: readonly Finding[], baseline: Baseline | undefined): Split => {
+export const splitByBaseline = (path: string, findings: readonly Finding[], baseline: Baseline | undefined, folder: string): Split => {
   if (baseline === undefined) return { fresh: findings, shelved: 0 };
   const known = new Set(baseline.entries);
-  const prints = fingerprints(path, findings);
+  const prints = fingerprints(path, findings, folder);
   const fresh = findings.filter((_, index) => !known.has(prints[index] ?? ""));
   return { fresh, shelved: findings.length - fresh.length };
 };