mulmoterminal 8.6.0 → 8.8.0

package/blueprints/adopt/hearing.json

@@ -4,6 +4,7 @@
       "id": "places",
       "label": "chaff に見させる文書（このフォルダの中のフォルダかファイルを 1 行に 1 つ）",
       "why": "ここにある文書の今の指摘を棚に上げ、以後はここの新しい指摘だけが出る",
+      "placeholder": "例:\ndocs/\nREADME.md",
       "kind": "text",
       "lines": true,
       "pick": "files"

package/blueprints/adopt/locales/en.json

@@ -6,7 +6,8 @@
   "hearing": {
     "places": {
       "label": "The documents for chaff to watch (one folder or file in this folder per line)",
-      "why": "Today's findings in these documents are shelved, and from then on only new findings here appear"
+      "why": "Today's findings in these documents are shelved, and from then on only new findings here appear",
+      "placeholder": "e.g.\ndocs/\nREADME.md"
     },
     "kind": {
       "label": "What kind of documents are they?",
@@ -60,7 +61,7 @@
   "presets": {
     "help-pages": {
       "title": "Bring chaff into help pages",
-      "description": "Measures the sample help pages (login.md and export.md) as \"Procedure, help or manual\", shelves today's findings of sentences that are too long, and from then on only new findings appear. It also makes a workflow that shows findings on GitHub PRs. The originals do not change."
+      "description": "Measures the sample help pages (login.md and export.md) as \"Procedure, help or manual\", shelves today's findings (a dropped-ら verb form and a \"here\" link that does not say where it goes), and from then on only new findings appear. It also makes a workflow that shows findings on GitHub PRs. The originals do not change."
     }
   }
 }

package/blueprints/adopt/presets/help-pages/export.md

@@ -6,4 +6,4 @@
 
 ## 書き出せないとき
 
-一度に書き出せるのは 10,000 行までです。それより多いときは、期間を分けて書き出してください。
+一度に書き出せるのは 10,000 行までです。それより多いときは、期間を分けて書き出してください。書き出したファイルは、Excel でも見れます。

package/blueprints/adopt/presets/help-pages/login.md

@@ -6,4 +6,4 @@
 
 ## アカウントがロックされたとき
 
-パスワードを5回続けて間違えると、アカウントが30分ロックされます。30分たってから、もう一度ログインしてください。
+パスワードを5回続けて間違えると、アカウントが30分ロックされます。30分たってから、もう一度ログインしてください。急ぎのときは[こちら](https://example.com/support)から問い合わせてください。

package/blueprints/adopt/presets.json

@@ -3,7 +3,7 @@
     {
       "id": "help-pages",
       "title": "ヘルプのページに chaff を入れる",
-      "description": "見本のヘルプ（login.md と export.md）を「手順書・ヘルプ・マニュアル」として測り、今ある長すぎる文の指摘を棚に上げて、以後は新しい指摘だけが出るようにする。GitHub の PR に指摘を出すワークフローも作る。原本は変えない。",
+      "description": "見本のヘルプ（login.md と export.md）を「手順書・ヘルプ・マニュアル」として測り、今ある指摘（ら抜き言葉や、行き先の分からない「こちら」のリンク）を棚に上げて、以後は新しい指摘だけが出るようにする。GitHub の PR に指摘を出すワークフローも作る。原本は変えない。",
       "base": "docs",
       "answers": {
         "places": "login.md\nexport.md",

package/blueprints/adopt/templates/chaff.yml

@@ -21,7 +21,7 @@ jobs:
       - uses: actions/setup-node@v7
         with:
           node-version: 24
-      - run: npx -y chaffjs@0.18 {{PATHS}} --sarif chaff.sarif
+      - run: npx -y chaffjs@0.21 {{PATHS}} --sarif chaff.sarif
         continue-on-error: true
       - uses: github/codeql-action/upload-sarif@1c5b675653bb5c22dbe9b12b556ec555138e09fd # v4.38.1
         with:

package/blueprints/ask/hearing.json

@@ -4,6 +4,7 @@
       "id": "documents",
       "label": "質問する相手の文書（このフォルダの中のファイルを 1 行に 1 つ）",
       "why": "答えはこの文書だけから出し、どこに書いてあるかを示す",
+      "placeholder": "例:\ndocs/就業規則.md\ndocs/経費精算の手引き.md",
       "kind": "text",
       "lines": true,
       "pick": "files"
@@ -12,6 +13,7 @@
       "id": "questions",
       "label": "質問（1 行に 1 つ）",
       "why": "質問ごとに一つ答える",
+      "placeholder": "例:\n出張の日当はいくらですか\n経費の申請はいつまでに出しますか",
       "kind": "text",
       "lines": true
     },

package/blueprints/ask/locales/en.json

@@ -6,11 +6,13 @@
   "hearing": {
     "documents": {
       "label": "The documents to ask (one file in this folder per line)",
-      "why": "Answers come only from these documents, with where each is written"
+      "why": "Answers come only from these documents, with where each is written",
+      "placeholder": "e.g.\ndocs/employee-handbook.md\ndocs/expenses-guide.md"
     },
     "questions": {
       "label": "Questions (one per line)",
-      "why": "One answer for each question"
+      "why": "One answer for each question",
+      "placeholder": "e.g.\nWhat is the daily allowance for a business trip?\nBy when must an expense claim be filed?"
     },
     "keep": {
       "label": "Keep the answers?",

package/blueprints/compare/hearing.json

@@ -4,6 +4,7 @@
       "id": "old",
       "label": "旧版の文書（このフォルダの中のファイル 1 つ）",
       "why": "比べる元。条ごとに新版と対応づける",
+      "placeholder": "例: contracts/業務委託契約_2025.md",
       "kind": "text",
       "pick": "files",
       "lines": true
@@ -12,6 +13,7 @@
       "id": "new",
       "label": "新版の文書（このフォルダの中のファイル 1 つ）",
       "why": "比べる先",
+      "placeholder": "例: contracts/業務委託契約_2026.md",
       "kind": "text",
       "pick": "files",
       "lines": true
@@ -20,6 +22,7 @@
       "id": "focus",
       "label": "特に見てほしいこと（任意）",
       "why": "その点に関わる変更を先に、詳しく書く",
+      "placeholder": "例: 支払い条件と解約の条件が変わっていないか",
       "kind": "text",
       "required": false
     }

package/blueprints/compare/locales/en.json

@@ -6,15 +6,18 @@
   "hearing": {
     "old": {
       "label": "The old version (one file in this folder)",
-      "why": "What to compare from. Each article is matched to the new version"
+      "why": "What to compare from. Each article is matched to the new version",
+      "placeholder": "e.g. contracts/service-agreement-2025.md"
     },
     "new": {
       "label": "The new version (one file in this folder)",
-      "why": "What to compare to"
+      "why": "What to compare to",
+      "placeholder": "e.g. contracts/service-agreement-2026.md"
     },
     "focus": {
       "label": "Anything to look at especially",
-      "why": "Changes about that point are written first and in more detail"
+      "why": "Changes about that point are written first and in more detail",
+      "placeholder": "e.g. whether the payment and termination terms changed"
     }
   },
   "steps": {

package/blueprints/docs/checks/chaff.sh

@@ -4,4 +4,4 @@
 if [ -n "${CHAFF_BIN:-}" ]; then
   exec sh -c "$CHAFF_BIN \"\$@\"" chaff "$@"
 fi
-exec npx -y chaffjs@0.18 "$@"
+exec npx -y chaffjs@0.21 "$@"

package/blueprints/docs/skills/workspace/SKILL.md

@@ -12,7 +12,7 @@ repository, `.git/info/exclude`) until the person has approved the models.
 1. `.blueprint/` already exists (the build created it). Everything this build records goes there.
 2. Run chaff once through the base pack's wrapper, so its first download happens now and not in the
    middle of a later step: `sh <base pack>/checks/chaff.sh rules --json > /dev/null`. The wrapper runs the
-   pinned chaff (`npx -y chaffjs@0.18`) unless `CHAFF_BIN` names another. If it fails, show the person the
+   pinned chaff (`npx -y chaffjs@0.21`) unless `CHAFF_BIN` names another. If it fails, show the person the
    error and stop — do not work around it.
 3. If the folder is a git repository, add `.blueprint/` to `.git/info/exclude`. That keeps the build's
    working files out of commits without touching `.gitignore`, which belongs to the person.

package/blueprints/from-collection/hearing.json

@@ -18,13 +18,16 @@
       "id": "appName",
       "label": "アプリの名前（空ならコレクションの名前）",
       "why": "画面と説明書に出す",
+      "placeholder": "例: 蔵書メモ",
       "kind": "text",
+      "short": true,
       "required": false
     },
     {
       "id": "whyApp",
       "label": "なぜアプリにしますか（コレクションでは何が足りませんか）",
       "why": "必須の機能を選ぶ基準になる。コレクションにあるものを写すだけなら、そう書く",
+      "placeholder": "例: 家族もスマホから本を登録できるようにしたい。コレクションのままだと、このパソコンからしか触れない",
       "kind": "text"
     },
     {
@@ -38,6 +41,7 @@
       "id": "mustHaves",
       "label": "これだけは最初から必要、という機能（空ならコレクションでできることすべて）",
       "why": "最後に一つずつ動くことを試験で確かめる",
+      "placeholder": "例: 本を登録する、題名で探す、貸し出し中かどうかを付ける",
       "kind": "text",
       "required": false
     },
@@ -45,6 +49,7 @@
       "id": "later",
       "label": "あとでよい機能",
       "why": "最初の版から外しておく",
+      "placeholder": "例: 読書の記録をグラフで見る、バーコードで登録する",
       "kind": "text",
       "required": false
     },
@@ -59,6 +64,7 @@
       "id": "roles",
       "label": "役割は分けますか（例: 管理者と一般）",
       "why": "だれが何をできるかの規則になる",
+      "placeholder": "例: 管理者は全部の本を直せる。家族は自分が登録した本だけ直せる",
       "kind": "text",
       "showIf": {
         "id": "signIn",

package/blueprints/from-collection/locales/en.json

@@ -14,11 +14,13 @@
     },
     "appName": {
       "label": "The app's name (empty: the collection's name)",
-      "why": "Shown on the screens and in the instructions"
+      "why": "Shown on the screens and in the instructions",
+      "placeholder": "e.g. Book Notes"
     },
     "whyApp": {
       "label": "Why make it an app? (What does the collection not do?)",
-      "why": "This is how the must-haves are chosen. If you only want to copy what the collection has, say so"
+      "why": "This is how the must-haves are chosen. If you only want to copy what the collection has, say so",
+      "placeholder": "e.g. My family should be able to add books from their phones. As a collection, it only works on this computer"
     },
     "audience": {
       "label": "Who will use it?",
@@ -32,11 +34,13 @@
     },
     "mustHaves": {
       "label": "Features it must have from the start (empty: everything the collection can do)",
-      "why": "At the end, each one is proved to work by a test"
+      "why": "At the end, each one is proved to work by a test",
+      "placeholder": "e.g. add a book, search by title, mark whether it is lent out"
     },
     "later": {
       "label": "Features that can wait",
-      "why": "They are left out of the first version"
+      "why": "They are left out of the first version",
+      "placeholder": "e.g. reading charts, adding a book by its barcode"
     },
     "signIn": {
       "label": "How should people sign in?",
@@ -49,7 +53,8 @@
     },
     "roles": {
       "label": "Should there be roles? (for example, admin and regular user)",
-      "why": "These become the rules for who can do what"
+      "why": "These become the rules for who can do what",
+      "placeholder": "e.g. An admin can edit every book; family members can edit only the books they added"
     },
     "dataSensitivity": {
       "label": "The most sensitive information it handles",

package/blueprints/glossary/hearing.json

@@ -4,6 +4,7 @@
       "id": "documents",
       "label": "用語を集める文書（このフォルダの中のファイルを 1 行に 1 つ）",
       "why": "定義された語と書き方をこの文書から集め、原文の引用で裏付ける",
+      "placeholder": "例:\ndocs/仕様書.md\ndocs/用語メモ.md",
       "kind": "text",
       "lines": true,
       "pick": "files"

package/blueprints/glossary/locales/en.json

@@ -6,7 +6,8 @@
   "hearing": {
     "documents": {
       "label": "The documents to collect terms from (one file per line, inside this folder)",
-      "why": "Defined terms and spellings are collected from these documents and backed by quotes from the original"
+      "why": "Defined terms and spellings are collected from these documents and backed by quotes from the original",
+      "placeholder": "e.g.\ndocs/spec.md\ndocs/terms.md"
     },
     "write": {
       "label": "Put how to align the spellings it found into chaff.yaml?",

package/blueprints/internal/hearing.json

@@ -4,19 +4,24 @@
       "id": "appName",
       "label": "アプリの名前",
       "why": "画面とプロジェクト名に使う",
-      "kind": "text"
+      "placeholder": "例: 備品貸し出し",
+      "kind": "text",
+      "short": true
     },
     {
       "id": "appPurpose",
       "label": "何をするアプリですか（誰が、何を、どうする）",
       "why": "データの形と画面の数が決まる",
+      "placeholder": "例: 社員が会議室のプロジェクターなどの備品を予約し、総務が貸し出しと返却を記録する",
       "kind": "text"
     },
     {
       "id": "domain",
       "label": "会社のメールアドレスのドメイン（例: example.co.jp）",
       "why": "このドメインの人だけがログインできるようにする",
-      "kind": "text"
+      "placeholder": "例: example.co.jp",
+      "kind": "text",
+      "short": true
     },
     {
       "id": "workspace",
@@ -34,6 +39,7 @@
       "id": "externalWho",
       "label": "どんな社外の人が、何をしますか",
       "why": "別の設計図を選ぶ材料にする",
+      "placeholder": "例: 取引先の担当者が、自社あての発注の進み具合を見る",
       "kind": "text",
       "showIf": {
         "id": "external",
@@ -83,7 +89,9 @@
       "id": "existingProjectId",
       "label": "そのプロジェクト ID",
       "why": "本番用として使う",
+      "placeholder": "例: my-company-tools",
       "kind": "text",
+      "short": true,
       "showIf": {
         "id": "existingProject",
         "equals": true
@@ -105,6 +113,7 @@
       "id": "mainScreens",
       "label": "主な画面（分かる範囲で）",
       "why": "最初に作る画面を決める",
+      "placeholder": "例: 備品の一覧、予約の入力、総務用の貸し出し記録",
       "kind": "text",
       "required": false
     }

package/blueprints/internal/locales/en.json

@@ -6,15 +6,18 @@
   "hearing": {
     "appName": {
       "label": "The app's name",
-      "why": "Used on the screens and as the project name"
+      "why": "Used on the screens and as the project name",
+      "placeholder": "e.g. Equipment Loans"
     },
     "appPurpose": {
       "label": "What does the app do? (who does what, and how)",
-      "why": "It decides the data shape and how many screens there are"
+      "why": "It decides the data shape and how many screens there are",
+      "placeholder": "e.g. Staff book equipment such as meeting-room projectors, and the office team records when it goes out and comes back"
     },
     "domain": {
       "label": "Your company's email domain (e.g. example.co.jp)",
-      "why": "Only people with this domain will be able to sign in"
+      "why": "Only people with this domain will be able to sign in",
+      "placeholder": "e.g. example.com"
     },
     "workspace": {
       "label": "Does your company use Google Workspace?",
@@ -26,7 +29,8 @@
     },
     "externalWho": {
       "label": "Which outside people, and what will they do?",
-      "why": "Used to choose the other blueprint"
+      "why": "Used to choose the other blueprint",
+      "placeholder": "e.g. A supplier's contact checks how their orders from us are progressing"
     },
     "users": {
       "label": "About how many people will use it?",
@@ -72,7 +76,8 @@
     },
     "existingProjectId": {
       "label": "That project's ID",
-      "why": "Used for production"
+      "why": "Used for production",
+      "placeholder": "e.g. my-company-tools"
     },
     "billingAccount": {
       "label": "Do you have a Google Cloud billing account (a company card or similar)?",
@@ -84,7 +89,8 @@
     },
     "mainScreens": {
       "label": "The main screens (as far as you know)",
-      "why": "Decides which screens are built first"
+      "why": "Decides which screens are built first",
+      "placeholder": "e.g. the equipment list, a booking form, the office team's loan log"
     }
   },
   "steps": {

package/blueprints/polish/hearing.json

@@ -4,6 +4,7 @@
       "id": "targets",
       "label": "整えたい文書（ファイル・フォルダを 1 行に 1 つ。このフォルダの中の場所で）",
       "why": "候補はこの中から選ぶ",
+      "placeholder": "例:\ndocs/\nREADME.md",
       "kind": "text",
       "lines": true,
       "pick": "files"
@@ -96,6 +97,7 @@
       "id": "avoid",
       "label": "触らないでほしいファイルや場所（任意）",
       "why": "候補から外す",
+      "placeholder": "例: docs/legal/（法務が確認済みのため）",
       "kind": "text",
       "required": false
     }

package/blueprints/polish/locales/en.json

@@ -6,7 +6,8 @@
   "hearing": {
     "targets": {
       "label": "The documents to polish (one file or folder per line, as a place inside this folder)",
-      "why": "The candidates are chosen from these"
+      "why": "The candidates are chosen from these",
+      "placeholder": "e.g.\ndocs/\nREADME.md"
     },
     "style": {
       "label": "Which style should they follow?",
@@ -69,7 +70,8 @@
     },
     "avoid": {
       "label": "Files or places to leave alone",
-      "why": "Left out of the candidates"
+      "why": "Left out of the candidates",
+      "placeholder": "e.g. docs/legal/ (already reviewed by legal)"
     }
   },
   "steps": {
@@ -89,7 +91,7 @@
   "presets": {
     "oshirase": {
       "title": "Polish a company notice",
-      "description": "In the sample notice (oshirase.md), splits the sentences chaff finds too long so they read easily, without changing what they say. The original is kept. Run the \"Make a style\" example in the same folder first and choose its style, and the notice follows that style."
+      "description": "In the sample notice (oshirase.md), fixes what chaff finds (such as an intensifier that says nothing) so it reads easily, without changing what it says. The original is kept. Run the \"Make a style\" example in the same folder first and choose its style, and the notice follows that style."
     },
     "houkoku": {
       "title": "Polish a report as a report",
@@ -101,7 +103,7 @@
     },
     "tejun": {
       "title": "Polish a procedure as a procedure",
-      "description": "Reads the sample procedure (tejun.md) as a manual. Sentences that are too long are split without changing what they say. It looks at what you need before starting, whether one step holds two actions, and how to tell a step worked; where something needs adding, it becomes a question for the author in the report. The original is kept."
+      "description": "Reads the sample procedure (tejun.md) as a manual. What chaff finds (such as a \"here\" link that does not say where it goes) is fixed without changing what it says. It looks at what you need before starting, whether one step holds two actions, and how to tell a step worked; where something needs adding, it becomes a question for the author in the report. The original is kept."
     },
     "shayo": {
       "title": "Polish a regulation as a regulation",
@@ -109,7 +111,7 @@
     },
     "english-blog": {
       "title": "Polish an English blog post",
-      "description": "Reads the sample English technical blog post (post.md) as a technical article. The post stays in English: overlong sentences are split, and an opening that would fit any post or a stock closing line is cut. Where something needs adding, such as a closing that only summarises, it becomes a question for the author in the report. The report comes back in your report language. The original is kept."
+      "description": "Reads the sample English technical blog post (post.md) as a technical article. The post stays in English: an opening that would fit any post or a stock closing line is cut. Where something needs adding, such as a closing that only summarises, it becomes a question for the author in the report. The report comes back in your report language. The original is kept."
     }
   }
 }

package/blueprints/polish/presets/oshirase/oshirase.md

@@ -1,6 +1,6 @@
 # 年末年始の休みについてのお知らせ
 
-年末年始の休みについては、12月29日から1月3日までを会社としての休みとすることになりましたので、その期間中にどうしても対応が必要になるような仕事がある人については、前もって上長の人とよく相談をしておいてもらえるとよいかと思っています。
+年末年始の休みについては、12月29日から1月3日までを会社としての休みとすることになりましたので、その期間中にどうしても対応が必要になるような仕事がある人については、言うまでもなく前もって上長の人とよく相談をしておいてもらえるとよいかと思っています。
 
 休みの期間中の問い合わせについては、急ぎのものについてのみ、当番の人が対応をすることができるような形にしておきたいと考えていますので、当番の人の名前と連絡先については、12月20日までにこのページに書いておくようにします。
 

package/blueprints/polish/presets/tejun/tejun.md

@@ -7,7 +7,7 @@
 1. 経費精算システムを開き、社員番号とパスワードでログインして、左のメニューから「新しい申請」を選びます。
 2. 申請の種類で「交通費」を選びます。
 3. 使った日、出発した駅、着いた駅、金額を入れます。往復のときは「往復」に印を付けると、入れた金額が自動で二倍になって表示される仕組みになっているため、往復の合計の金額ではなく片道の金額を入れるように、入れる前にもう一度確かめてから次の手順に進むよう気をつけてください。
-4. 交通系ICカードで払ったときは、利用履歴を印刷したものを写真に撮り、「添付」から付けます。
+4. 交通系ICカードで払ったときは、利用履歴を印刷したものを写真に撮り、「添付」から付けます。利用履歴の印刷のしかたは[こちら](https://example.com/ic-history)を見てください。
 5. 「申請する」を押します。
 
 ## うまくいかないとき

package/blueprints/polish/presets.json

@@ -3,7 +3,7 @@
     {
       "id": "oshirase",
       "title": "社内のお知らせを整える",
-      "description": "見本のお知らせ（oshirase.md）のうち、chaff が長すぎると指摘した文を、書いてあることは変えずに分けて読みやすくする。直す前の原本は残す。先に「規約をつくる」の例を同じフォルダで済ませて規約を選ぶと、その規約に合わせて整える。",
+      "description": "見本のお知らせ（oshirase.md）のうち、chaff が指摘した所（強めるだけで中身の無い言い方など）を、書いてあることは変えずに直して読みやすくする。直す前の原本は残す。先に「規約をつくる」の例を同じフォルダで済ませて規約を選ぶと、その規約に合わせて整える。",
       "base": "docs",
       "answers": {
         "targets": "oshirase.md",
@@ -42,7 +42,7 @@
     {
       "id": "tejun",
       "title": "手順書を手順書として整える",
-      "description": "見本の手順書（tejun.md）を「マニュアル・手順書」として読む。長すぎる文は、書いてあることは変えずに分ける。始める前に要るもの、一つの手順に動作が二つ入っていないか、うまくいったことの確かめ方を見て、書き足しが要るところは直さずに、書いた人への質問として報告に並べる。直す前の原本は残す。",
+      "description": "見本の手順書（tejun.md）を「マニュアル・手順書」として読む。chaff が指摘した所（行き先の分からない「こちら」のリンクなど）は、書いてあることは変えずに直す。始める前に要るもの、一つの手順に動作が二つ入っていないか、うまくいったことの確かめ方を見て、書き足しが要るところは直さずに、書いた人への質問として報告に並べる。直す前の原本は残す。",
       "base": "docs",
       "answers": {
         "targets": "tejun.md",
@@ -68,7 +68,7 @@
     {
       "id": "english-blog",
       "title": "英語のブログ記事を整える",
-      "description": "見本の英語の技術ブログ（post.md）を「ブログ（技術記事）」として読む。文書は英語のまま、長すぎる文を分け、どの記事にも当てはまる書き出しや結びの決まり文句は削る。要約だけの結びなど、書き足しが要るところは直さずに、書いた人への質問として報告に並べる。報告は画面の言語で返る。直す前の原本は残す。",
+      "description": "見本の英語の技術ブログ（post.md）を「ブログ（技術記事）」として読む。文書は英語のまま、どの記事にも当てはまる書き出しや結びの決まり文句は削る。要約だけの結びなど、書き足しが要るところは直さずに、書いた人への質問として報告に並べる。報告は画面の言語で返る。直す前の原本は残す。",
       "base": "docs",
       "answers": {
         "targets": "post.md",

package/blueprints/product/hearing.json

@@ -4,18 +4,22 @@
       "id": "appName",
       "label": "アプリの名前（仮でよい）",
       "why": "画面と説明書に出す",
-      "kind": "text"
+      "placeholder": "例: レシピ帳",
+      "kind": "text",
+      "short": true
     },
     {
       "id": "idea",
       "label": "何を作りたいですか（一言で）",
       "why": "作るものの芯になる",
+      "placeholder": "例: 家族で使うレシピの共有アプリ",
       "kind": "text"
     },
     {
       "id": "problem",
       "label": "どんな困りごとを解決しますか",
       "why": "必須の機能を選ぶ基準になる",
+      "placeholder": "例: レシピがメモ帳やブックマークに散らばっていて、作りたいときに見つからない",
       "kind": "text"
     },
     {
@@ -29,24 +33,28 @@
       "id": "things",
       "label": "扱うものは何ですか（例: 本、予約、在庫、レシピ）",
       "why": "データの表になる",
+      "placeholder": "例: レシピ、材料、買い物リスト",
       "kind": "text"
     },
     {
       "id": "actions",
       "label": "使う人は何をしますか（例: 登録する、探す、予約する、集計を見る）",
       "why": "API と画面になる",
+      "placeholder": "例: レシピを登録する、材料で探す、買い物リストを作る",
       "kind": "text"
     },
     {
       "id": "mustHaves",
       "label": "これだけは最初から必要、という機能",
       "why": "最後に一つずつ動くことを試験で確かめる",
+      "placeholder": "例: レシピの登録と編集、題名と材料での検索",
       "kind": "text"
     },
     {
       "id": "later",
       "label": "あとでよい機能",
       "why": "最初の版から外しておく",
+      "placeholder": "例: 写真の自動補正、献立の提案",
       "kind": "text",
       "required": false
     },
@@ -61,6 +69,7 @@
       "id": "roles",
       "label": "役割は分けますか（例: 管理者と一般）",
       "why": "だれが何をできるかの規則になる",
+      "placeholder": "例: 管理者はすべてのレシピを消せる。家族は自分のレシピだけ直せる",
       "kind": "text",
       "showIf": {
         "id": "signIn",
@@ -78,6 +87,7 @@
       "id": "references",
       "label": "似ているサービスやイメージ（あれば）",
       "why": "画面の作りの参考にする",
+      "placeholder": "例: クックパッドのような一覧画面。写真が大きく見えるとよい",
       "kind": "text",
       "required": false
     },

package/blueprints/product/locales/en.json

@@ -6,15 +6,18 @@
   "hearing": {
     "appName": {
       "label": "The app's name (a working name is fine)",
-      "why": "Shown on the screens and in the instructions"
+      "why": "Shown on the screens and in the instructions",
+      "placeholder": "e.g. Recipe Box"
     },
     "idea": {
       "label": "What do you want to make (in a few words)?",
-      "why": "It becomes the core of what is built"
+      "why": "It becomes the core of what is built",
+      "placeholder": "e.g. A recipe-sharing app for the family"
     },
     "problem": {
       "label": "What problem does it solve?",
-      "why": "It decides which features are must-haves"
+      "why": "It decides which features are must-haves",
+      "placeholder": "e.g. Our recipes are scattered across notes and bookmarks, and we cannot find one when we want to cook it"
     },
     "audience": {
       "label": "Who will use it?",
@@ -28,19 +31,23 @@
     },
     "things": {
       "label": "What does it handle? (e.g. books, bookings, stock, recipes)",
-      "why": "These become the tables of data"
+      "why": "These become the tables of data",
+      "placeholder": "e.g. recipes, ingredients, shopping lists"
     },
     "actions": {
       "label": "What do the people using it do? (e.g. add, search, book, see totals)",
-      "why": "These become the API and the screens"
+      "why": "These become the API and the screens",
+      "placeholder": "e.g. add a recipe, search by ingredient, make a shopping list"
     },
     "mustHaves": {
       "label": "The features it needs from the very start",
-      "why": "At the end, a test checks each one works"
+      "why": "At the end, a test checks each one works",
+      "placeholder": "e.g. adding and editing recipes, searching by title and ingredient"
     },
     "later": {
       "label": "Features that can wait",
-      "why": "Left out of the first version"
+      "why": "Left out of the first version",
+      "placeholder": "e.g. automatic photo touch-up, meal suggestions"
     },
     "signIn": {
       "label": "How should people sign in?",
@@ -53,7 +60,8 @@
     },
     "roles": {
       "label": "Should there be different roles? (e.g. admin and regular user)",
-      "why": "It becomes the rules for who can do what"
+      "why": "It becomes the rules for who can do what",
+      "placeholder": "e.g. An admin can delete any recipe; family members can edit only their own"
     },
     "dataSensitivity": {
       "label": "The most sensitive information it handles",
@@ -67,7 +75,8 @@
     },
     "references": {
       "label": "Similar services or the look you have in mind (if any)",
-      "why": "Used as a reference for the screens"
+      "why": "Used as a reference for the screens",
+      "placeholder": "e.g. A list like a recipe site's, with large photos"
     },
     "uiLanguage": {
       "label": "The language of the screens",