@tomako/tools-runtime 0.1.0

package/src/features/tools/user-interview-guide-generator/user-interview-guide-generator.package.ts

@@ -0,0 +1,774 @@
+import { userInterviewGuideResultSchema } from "../../../lib/tools/user-interview.schema";
+
+import type { ToolPackage } from "../package/types";
+
+/**
+ * 金样工具：archetype 引擎迁移的第一个 ToolPackage。
+ * 替代原 container(195L) + widget(841L) + service(127L) + i18n×3(~760L)，
+ * 行为与 2026-07-03 前的 custom 实现对齐。
+ */
+export const userInterviewGuideGeneratorPackage: ToolPackage = {
+  meta: {
+    slug: "user-interview-guide-generator",
+    toolType: "generator",
+    keywordEvidence:
+      "legacy:2026-06-29 迁移工具，发布前需 pnpm seo:keyword-brief -- --slug user-interview-guide-generator",
+    seo: {
+      publishedAt: "2026-06-29",
+      updatedAt: "2026-07-03",
+      readingTime: "7 min",
+      featured: false,
+      ogImage: "/tools/user-interview-guide-generator-hero-pseo.webp",
+    },
+  },
+  copy: {
+    title: {
+      en: "User Interview Guide Generator",
+      zh: "用户访谈提纲生成器",
+      "zh-tw": "用戶訪談提綱生成器",
+    },
+    description: {
+      en: "Generate a decision-oriented user interview guide: who to recruit, how to open, what to ask, how to probe, what counts as strong evidence, and what needs human review.",
+      zh: "围绕一个产品决策生成用户访谈提纲：招募谁、怎么开场、问什么、如何追问、哪些回答算强信号，以及哪些问题需要人工复核。",
+      "zh-tw":
+        "圍繞一個產品決策生成用戶訪談提綱：招募誰、怎麼開場、問什麼、如何追問、哪些回答算強信號，以及哪些問題需要人工複核。",
+    },
+    intro: {
+      en: "Go beyond a generic question list. Connect product stage, recent participant behavior, and the decision you need to make into an executable interview playbook.",
+      zh: "不是套一份通用问题清单，而是把产品阶段、受访者近期行为和要支持的决策连在一起，生成可执行的访谈作战手册。",
+      "zh-tw":
+        "不是套一份通用問題清單，而是把產品階段、受訪者近期行為和要支持的決策連在一起，生成可執行的訪談作戰手冊。",
+    },
+    category: {
+      en: "User research tools",
+      zh: "用户研究工具",
+      "zh-tw": "用戶研究工具",
+    },
+    keywords: {
+      en: [
+        "user interview guide",
+        "user interview questions generator",
+        "customer interview template",
+        "product discovery questions",
+        "user research tool",
+      ],
+      zh: ["用户访谈提纲", "用户访谈问题生成器", "用户访谈模板", "产品访谈问题", "用户研究工具"],
+      "zh-tw": ["用戶訪談提綱", "用戶訪談問題生成器", "用戶訪談模板", "產品訪談問題", "用戶研究工具"],
+    },
+    inputSignal: {
+      en: "Product stage + interview goal",
+      zh: "产品阶段 + 访谈目的",
+      "zh-tw": "產品階段 + 訪談目的",
+    },
+    outputSignal: {
+      en: "Strategy + questions + evidence signals",
+      zh: "访谈策略 + 问题追问 + 证据信号",
+      "zh-tw": "訪談策略 + 問題追問 + 證據信號",
+    },
+    boundarySignal: {
+      en: "Research draft; review and validate in real interviews",
+      zh: "研究草案，需人工复核和真实访谈验证",
+      "zh-tw": "研究草案，需人工複核和真實訪談驗證",
+    },
+  },
+  form: [
+    {
+      kind: "text",
+      id: "productName",
+      required: true,
+      label: { en: "Product or brand name", zh: "产品或项目名称", "zh-tw": "產品或項目名稱" },
+      hint: { en: "Real name or working title", zh: "真实名称或暂定名", "zh-tw": "真實名稱或暫定名" },
+      placeholder: { en: "e.g. LaunchKit AI", zh: "例如 LaunchKit AI", "zh-tw": "例如 LaunchKit AI" },
+      invalidMessage: {
+        en: "Add a real product name or working title, not a placeholder.",
+        zh: "请填写真实产品名或暂定名，不要只填测试占位文本。",
+        "zh-tw": "請填寫真實產品名或暫定名，不要只填測試佔位文字。",
+      },
+    },
+    {
+      kind: "textarea",
+      id: "productDescription",
+      required: true,
+      rows: 4,
+      minLength: 12,
+      label: { en: "Product / business description", zh: "产品 / 业务描述", "zh-tw": "產品 / 業務描述" },
+      hint: { en: "Who, problem, outcome", zh: "给谁、解决什么、卡在哪", "zh-tw": "給誰、解決什麼、卡在哪" },
+      placeholder: {
+        en: "Write the product, the audience, the problem, and the current blocker. Example: helps indie builders prepare a launch kit before Product Hunt.",
+        zh: "写清产品、目标用户、解决的问题和当前卡点。例如：帮独立开发者在 Product Hunt 发布前准备 launch kit。",
+        "zh-tw": "寫清產品、目標用戶、解決的問題和當前卡點。例如：幫獨立開發者在 Product Hunt 發布前準備 launch kit。",
+      },
+      invalidMessage: {
+        en: "Say who the product serves and what problem or outcome it addresses. One clear sentence is enough.",
+        zh: "说清楚产品给谁用、解决什么问题或带来什么结果。一句清楚的话就够。",
+        "zh-tw": "說清楚產品給誰用、解決什麼問題或帶來什麼結果。一句清楚的話就夠。",
+      },
+    },
+    {
+      kind: "select",
+      id: "productStage",
+      defaultValue: "idea",
+      label: { en: "Current stage", zh: "当前阶段", "zh-tw": "當前階段" },
+      options: [
+        { value: "idea", label: { en: "Idea stage", zh: "想法阶段", "zh-tw": "想法階段" } },
+        { value: "mvp", label: { en: "Before / during MVP", zh: "MVP 前 / MVP 中", "zh-tw": "MVP 前 / MVP 中" } },
+        { value: "prototype", label: { en: "Prototype exists", zh: "已有原型", "zh-tw": "已有原型" } },
+        { value: "launched", label: { en: "Launched", zh: "已上线", "zh-tw": "已上線" } },
+        { value: "growth", label: { en: "Growth stage", zh: "增长阶段", "zh-tw": "增長階段" } },
+        {
+          value: "churn",
+          label: { en: "Churn / inactive analysis", zh: "流失 / 不活跃分析", "zh-tw": "流失 / 不活躍分析" },
+        },
+      ],
+    },
+    {
+      kind: "select",
+      id: "interviewGoal",
+      defaultValue: "problemValidation",
+      label: { en: "Interview goal", zh: "访谈目的", "zh-tw": "訪談目的" },
+      options: [
+        {
+          value: "discovery",
+          label: { en: "Explore problem and audience", zh: "探索问题和人群", "zh-tw": "探索問題和人群" },
+        },
+        {
+          value: "problemValidation",
+          label: { en: "Validate pain strength", zh: "验证痛点强度", "zh-tw": "驗證痛點強度" },
+        },
+        {
+          value: "solutionValidation",
+          label: { en: "Validate solution direction", zh: "验证方案方向", "zh-tw": "驗證方案方向" },
+        },
+        {
+          value: "usability",
+          label: { en: "Test prototype usability", zh: "测试原型可用性", "zh-tw": "測試原型可用性" },
+        },
+        {
+          value: "pricing",
+          label: {
+            en: "Validate pricing and willingness to pay",
+            zh: "验证定价和付费意愿",
+            "zh-tw": "驗證定價和付費意願",
+          },
+        },
+        { value: "churn", label: { en: "Understand churn reasons", zh: "理解流失原因", "zh-tw": "理解流失原因" } },
+        {
+          value: "positioning",
+          label: {
+            en: "Find positioning and customer language",
+            zh: "提炼定位和用户语言",
+            "zh-tw": "提煉定位和用戶語言",
+          },
+        },
+      ],
+    },
+    {
+      kind: "textarea",
+      id: "targetParticipants",
+      required: true,
+      rows: 3,
+      minLength: 8,
+      label: { en: "Target participants", zh: "目标受访者", "zh-tw": "目標受訪者" },
+      hint: { en: "Role plus recent behavior", zh: "人群 + 近期行为", "zh-tw": "人群 + 近期行為" },
+      placeholder: {
+        en: "e.g. indie builders who launched a product recently but still do not have a stable traffic source.",
+        zh: "例如：最近发布过产品、但还没有稳定访问来源的独立开发者 / 小团队。",
+        "zh-tw": "例如：最近發布過產品、但還沒有穩定訪問來源的獨立開發者 / 小團隊。",
+      },
+      invalidMessage: {
+        en: "Name the participant group and a recent behavior or situation that makes them relevant.",
+        zh: "说清楚要访谈哪类人，以及他们最近做过什么或正处在什么场景。",
+        "zh-tw": "說清楚要訪談哪類人，以及他們最近做過什麼或正處在什麼場景。",
+      },
+    },
+    {
+      kind: "textarea",
+      id: "knownHypotheses",
+      rows: 3,
+      label: { en: "Known hypotheses", zh: "已有假设", "zh-tw": "已有假設" },
+      placeholder: {
+        en: "e.g. developers scramble to create logos, screenshots, and social images before launch; resizing and visual consistency hurt most.",
+        zh: "例如：开发者会在上线前临时补齐 Logo、截图、社媒图，最痛的是多尺寸适配和风格统一。",
+        "zh-tw": "例如：開發者會在上線前臨時補齊 Logo、截圖、社群圖片，最痛的是多尺寸適配和風格統一。",
+      },
+    },
+    {
+      kind: "textarea",
+      id: "decisionToMake",
+      rows: 3,
+      label: {
+        en: "Decision this round should inform",
+        zh: "这轮访谈要帮助你做什么决策",
+        "zh-tw": "這輪訪談要幫助你做什麼決策",
+      },
+      placeholder: {
+        en: "e.g. whether the MVP should start with Product Hunt/social launch kits or App Store screenshots.",
+        zh: "例如：MVP 是否先做 Product Hunt / 社媒发布物料包，还是先做 App Store 截图。",
+        "zh-tw": "例如：MVP 是否先做 Product Hunt / 社群發布物料包，還是先做 App Store 截圖。",
+      },
+    },
+    {
+      kind: "toggle",
+      id: "hasPrototype",
+      defaultValue: false,
+      label: { en: "Prototype / demo", zh: "是否已有原型 / demo", "zh-tw": "是否已有原型 / demo" },
+      onLabel: { en: "Exists", zh: "已有", "zh-tw": "已有" },
+      offLabel: { en: "Not yet", zh: "没有", "zh-tw": "沒有" },
+    },
+    {
+      kind: "select",
+      id: "sessionLength",
+      defaultValue: "45",
+      label: { en: "Session length", zh: "访谈时长", "zh-tw": "訪談時長" },
+      options: [
+        { value: "30", label: { en: "30 min", zh: "30 分钟", "zh-tw": "30 分鐘" } },
+        { value: "45", label: { en: "45 min", zh: "45 分钟", "zh-tw": "45 分鐘" } },
+        { value: "60", label: { en: "60 min", zh: "60 分钟", "zh-tw": "60 分鐘" } },
+      ],
+    },
+  ],
+  /**
+   * direct 车道试点（2026-07-04）：任务是"表单 brief → 固定 schema 提纲"的单次变换，
+   * 无需浏览/调研/文件 IO，符合 direct 判据（tool-package-pipeline.md）。
+   * 原 agent 车道契约（$user-interview-guide + user-interview-guide.mjs 写回）保留在
+   * Skills-OL，如需回退将本块换回 lane: "agent" 即可。
+   */
+  runtime: {
+    lane: "direct",
+    scene: "user_interview_guide",
+    system:
+      "You are Tomako's user interview research strategist. You design decision-oriented interview guides that ground every question in recent real behavior and honest evidence standards. You never invent user evidence and you surface gaps instead of pretending certainty.",
+    promptTemplate: `Design a user interview guide from this structured brief:
+
+\`\`\`json
+{{briefJson}}
+\`\`\`
+
+Quality requirements:
+- currentRead must restate the brief faithfully: product, stage, interviewGoal, and coreDecision. Derive coreDecision from decisionToMake; if it is empty, infer the nearest product decision this research should support and record that inference in currentRead.assumptions.
+- recommendedInterviewType must match interviewGoal and hasPrototype (discovery, problem validation, solution validation, usability, pricing, churn, or positioning interview).
+- sessionFlow segments must add up to roughly sessionLength minutes; minutes is a string number per segment.
+- Write 6-10 questions. Ground questions in recent real behavior before opinions or solutions. Tie every question to the product decision, a participant criterion, or an evidence signal. Each question needs purpose, listenFor, followUps, and one leading-question pattern to avoid.
+- followUpTrees: 3-5 realistic answer triggers with concrete probes.
+- strongSignals, weakSignals, and riskSignals must be checkable evidence standards a note-taker can apply during the session, not generic advice.
+- If the brief lacks context, state honest assumptions, list the gaps in missingInfo, add human checks to reviewChecklist, and put concrete next actions in postInterviewHandoff.
+- Set promptVersion to "direct-v1".`,
+    maxTokens: 8000,
+  },
+  resultSchema: userInterviewGuideResultSchema,
+  resultView: [
+    {
+      block: "keyValues",
+      title: { en: "Current read", zh: "当前判断", "zh-tw": "當前判斷" },
+      items: [
+        { label: { en: "Product", zh: "产品", "zh-tw": "產品" }, path: "currentRead.product" },
+        { label: { en: "Stage", zh: "阶段", "zh-tw": "階段" }, path: "currentRead.stage" },
+        { label: { en: "Interview goal", zh: "访谈目的", "zh-tw": "訪談目的" }, path: "currentRead.interviewGoal" },
+        { label: { en: "Core decision", zh: "核心决策", "zh-tw": "核心決策" }, path: "currentRead.coreDecision" },
+        { label: { en: "Assumptions", zh: "假设", "zh-tw": "假設" }, path: "currentRead.assumptions" },
+        {
+          label: { en: "Recommended interview type", zh: "推荐访谈类型", "zh-tw": "推薦訪談類型" },
+          path: "recommendedInterviewType",
+        },
+      ],
+    },
+    {
+      block: "bulletList",
+      title: { en: "Research objectives", zh: "研究目标", "zh-tw": "研究目標" },
+      path: "researchObjectives",
+    },
+    {
+      block: "bulletGroups",
+      title: { en: "Target participants", zh: "目标受访者", "zh-tw": "目標受訪者" },
+      columns: [
+        {
+          label: { en: "Recruit", zh: "招募条件", "zh-tw": "招募條件" },
+          path: "participantCriteria",
+          tone: "positive",
+        },
+        {
+          label: { en: "Exclude", zh: "排除条件", "zh-tw": "排除條件" },
+          path: "exclusionCriteria",
+          tone: "risk",
+        },
+      ],
+    },
+    {
+      block: "cardList",
+      title: { en: "Session flow", zh: "访谈流程", "zh-tw": "訪談流程" },
+      path: "sessionFlow",
+      layout: "grid",
+      card: {
+        titleField: "label",
+        metaField: "minutes",
+        metaSuffix: { en: " min", zh: " 分钟", "zh-tw": " 分鐘" },
+        body: { field: "goal" },
+      },
+    },
+    {
+      block: "cardList",
+      title: { en: "Interview questions", zh: "访谈问题", "zh-tw": "訪談問題" },
+      path: "questions",
+      card: {
+        titleField: "question",
+        body: { field: "purpose", label: { en: "Purpose", zh: "目的", "zh-tw": "目的" } },
+        lists: [
+          { field: "listenFor", label: { en: "Listen for", zh: "重点听", "zh-tw": "重點聽" } },
+          { field: "followUps", label: { en: "Follow-ups", zh: "追问", "zh-tw": "追問" } },
+        ],
+        footer: { field: "avoid", label: { en: "Avoid", zh: "避免", "zh-tw": "避免" } },
+      },
+    },
+    {
+      block: "cardList",
+      title: { en: "Branching probes", zh: "分支追问树", "zh-tw": "分支追問樹" },
+      path: "followUpTrees",
+      card: {
+        titleField: "trigger",
+        lists: [{ field: "probes", label: { en: "Probes", zh: "追问", "zh-tw": "追問" } }],
+      },
+    },
+    {
+      block: "bulletGroups",
+      title: { en: "Signal watchlist", zh: "重点观察信号", "zh-tw": "重點觀察信號" },
+      columns: [
+        { label: { en: "Strong signals", zh: "强信号", "zh-tw": "強信號" }, path: "strongSignals", tone: "positive" },
+        { label: { en: "Weak signals", zh: "弱信号", "zh-tw": "弱信號" }, path: "weakSignals" },
+        { label: { en: "Risk signals", zh: "风险信号", "zh-tw": "風險信號" }, path: "riskSignals", tone: "risk" },
+      ],
+    },
+    {
+      block: "bulletList",
+      title: { en: "Missing information", zh: "缺失信息", "zh-tw": "缺失資訊" },
+      path: "missingInfo",
+      tone: "risk",
+    },
+    {
+      block: "bulletList",
+      title: { en: "Human review checklist", zh: "人工复核清单", "zh-tw": "人工複核清單" },
+      path: "reviewChecklist",
+    },
+    {
+      block: "bulletList",
+      title: { en: "Post-interview handoff", zh: "访谈后交接", "zh-tw": "訪談後交接" },
+      path: "postInterviewHandoff",
+    },
+  ],
+  widget: {
+    formTitle: { en: "Interview context", zh: "访谈背景", "zh-tw": "訪談背景" },
+    formHint: {
+      en: "Describe the product, stage, and research goal so the output can center on your decision.",
+      zh: "写清产品、阶段和访谈目的，输出会围绕你的产品决策组织。",
+      "zh-tw": "寫清產品、階段和訪談目的，輸出會圍繞你的產品決策組織。",
+    },
+    submitLabel: { en: "Generate interview guide", zh: "生成访谈提纲", "zh-tw": "生成訪談提綱" },
+    pendingTitle: {
+      en: "Preparing the interview guide",
+      zh: "正在准备访谈提纲",
+      "zh-tw": "正在準備訪談提綱",
+    },
+    pendingHint: {
+      en: "Tomako will understand the research goal first, then return a reviewable structured result. Keep this page open.",
+      zh: "Tomako 会先理解研究目标，再生成可复核的结构化结果。请保持页面打开。",
+      "zh-tw": "Tomako 會先理解研究目標，再生成可複核的結構化結果。請保持頁面打開。",
+    },
+    errorOverrides: {
+      validation: {
+        title: { en: "Add real context", zh: "请补充真实背景", "zh-tw": "請補充真實背景" },
+        body: {
+          en: "The product description and participant criteria need to be specific. Test text, numbers, and vague filler are blocked.",
+          zh: "产品描述和目标受访者需要足够具体，不能只填测试文本、数字或空泛描述。",
+          "zh-tw": "產品描述和目標受訪者需要足夠具體，不能只填測試文字、數字或空泛描述。",
+        },
+      },
+    },
+  },
+  page: {
+    workspace: {
+      heading: {
+        en: "Design the interview as a product decision test",
+        zh: "先把访谈设计成一次产品决策实验",
+        "zh-tw": "生成一套可複核的用戶訪談提綱",
+      },
+      hint: {
+        en: "Enter the product context, current stage, decision to validate, and target participants. Tomako turns that into an executable guide: who to recruit, how to open, what to ask, how to probe, and what counts as strong evidence.",
+        zh: "输入产品背景、当前阶段、要验证的判断和目标受访者，Tomako 会把它整理成可执行的访谈提纲：招募谁、怎么开场、问什么、追问什么、哪些回答才算强信号。",
+        "zh-tw":
+          "輸入產品背景、訪談目標和目標受訪者，Tomako 會生成結構化訪談提綱，並把缺失資訊、假設和人工複核點一起寫出來。",
+      },
+      badge: { en: "Before the interview", zh: "访谈前准备", "zh-tw": "訪談前準備" },
+    },
+    sections: [
+      {
+        kind: "cards",
+        heading: {
+          en: "What you can use immediately",
+          zh: "生成后可以直接拿去做什么",
+          "zh-tw": "你會得到什麼",
+        },
+        items: [
+          {
+            title: { en: "Interview strategy", zh: "访谈策略", "zh-tw": "訪談策略" },
+            body: {
+              en: "Choose discovery, problem validation, solution validation, pricing, churn, or positioning before writing questions.",
+              zh: "先判断应该做探索、问题验证、方案验证、定价、流失还是定位访谈，避免直接套通用问题清单。",
+              "zh-tw": "先判斷應該做探索、問題驗證、方案驗證、定價、流失還是定位訪談，避免直接套通用問題清單。",
+            },
+          },
+          {
+            title: { en: "Participant criteria", zh: "受访者筛选条件", "zh-tw": "受訪者篩選條件" },
+            body: {
+              en: "Turn 'talk to users' into concrete screener criteria that prioritize people with recent real behavior.",
+              zh: "把“找用户聊聊”改成可执行的筛选条件，优先找近期发生过相关行为、能讲具体案例的人。",
+              "zh-tw": "把“找用戶聊聊”改成可執行的篩選條件，優先找近期發生過相關行為、能講具體案例的人。",
+            },
+          },
+          {
+            title: {
+              en: "Questions, purpose, and probes",
+              zh: "问题、目的和追问",
+              "zh-tw": "問題、目的和追問",
+            },
+            body: {
+              en: "Each question explains why it exists, what to listen for, how to probe, and which leading behavior to avoid.",
+              zh: "每个问题都会说明为什么问、重点听什么、怎样继续追问，以及哪些诱导式问法应该避免。",
+              "zh-tw": "每個問題都會說明為什麼問、重點聽什麼、怎樣繼續追問，以及哪些誘導式問法應該避免。",
+            },
+          },
+          {
+            title: {
+              en: "Evidence signals and review checks",
+              zh: "证据信号和复核清单",
+              "zh-tw": "證據信號和複核清單",
+            },
+            body: {
+              en: "Separate strong signals, weak feedback, risks, missing information, and post-interview handoff actions.",
+              zh: "把强信号、弱反馈、风险信号、缺失信息和访谈后交接动作拆开，方便团队复盘。",
+              "zh-tw": "把強信號、弱反饋、風險信號、缺失資訊和訪談後交接動作拆開，方便團隊覆盤。",
+            },
+          },
+        ],
+      },
+      {
+        kind: "bullets",
+        heading: {
+          en: "Turn “talk to users” into an executable interview",
+          zh: "从“找用户聊聊”变成可执行访谈",
+          "zh-tw": "適合哪些場景",
+        },
+        image: {
+          src: "/tools/user-interview-guide-generator-support-pseo.webp",
+          alt: {
+            en: "Illustration of a researcher choosing target participants and recent behavior signals for interview recruiting.",
+            zh: "研究者根据目标受访者和近期行为设计访谈招募条件的插画。",
+            "zh-tw": "用戶訪談生成器支持場景示意圖，展示目標受訪者、近期行為和產品決策。",
+          },
+          side: "right",
+          wide: true,
+        },
+        groups: [
+          {
+            items: {
+              en: [
+                "You need to validate whether a pain is real and strong before building a feature or MVP.",
+                "You want interviews to serve a product decision instead of collecting loose opinions.",
+                "You already have a prototype, demo, or page and need to learn when users would actually use it.",
+                "You need a guide that another teammate can run with clear flow, probes, and evidence signals.",
+              ],
+              zh: [
+                "你要在做功能或 MVP 前验证痛点是否真实、是否够强。",
+                "你需要围绕一个产品决策设计访谈，而不是收集泛泛意见。",
+                "你已经有原型、demo 或页面，想知道用户在什么条件下会使用。",
+                "你要把访谈交给团队成员执行，需要清楚的流程、追问和证据信号。",
+              ],
+              "zh-tw": [
+                "你要在做功能或 MVP 前驗證痛點是否真實、是否夠強。",
+                "你需要圍繞一個產品決策設計訪談，而不是收集泛泛意見。",
+                "你已經有原型、demo 或頁面，想知道用戶在什麼條件下會使用。",
+                "你要把訪談交給團隊成員執行，需要清楚的流程、追問和證據信號。",
+              ],
+            },
+          },
+        ],
+      },
+      {
+        kind: "bullets",
+        heading: {
+          en: "When not to generate a guide yet",
+          zh: "什么时候先不要生成提纲",
+          "zh-tw": "不適合哪些場景",
+        },
+        image: {
+          src: "/tools/user-interview-guide-generator-failure-pseo.webp",
+          alt: {
+            en: "Illustration of a vague research question being clarified into concrete interview goals and probes.",
+            zh: "把模糊研究问题澄清成具体访谈目标和追问的插画。",
+            "zh-tw": "用戶訪談生成器失敗恢復示意圖，展示任務號、寫回校驗和人工複核。",
+          },
+          side: "left",
+          wide: true,
+        },
+        groups: [
+          {
+            items: {
+              en: [
+                "It does not replace real interviews, behavior data, conversion tests, or paid experiments.",
+                "It cannot decide that a product is worth building from one vague idea.",
+                "It is not suitable for medical, legal, financial, or other regulated research without professional review.",
+                "If the input is test text, numbers, or vague filler, the page blocks it or marks missing context.",
+              ],
+              zh: [
+                "不能替代真实访谈、行为数据、转化实验或付款测试。",
+                "不能根据一句模糊想法直接判断产品一定值得做。",
+                "不适合处理医疗、法律、金融等需要专业合规审查的访谈设计。",
+                "如果输入只有测试文本、数字或空泛描述，结果会被阻止或标记为需要补充信息。",
+              ],
+              "zh-tw": [
+                "不能替代真實訪談、行為數據、轉化實驗或付款測試。",
+                "不能根據一句模糊想法直接判斷產品一定值得做。",
+                "不適合處理醫療、法律、金融等需要專業合規審查的訪談設計。",
+                "如果輸入只有測試文字、數字或空泛描述，結果會被阻止或標記為需要補充資訊。",
+              ],
+            },
+          },
+          {
+            title: {
+              en: "How thin context is handled",
+              zh: "信息不足时怎么处理",
+              "zh-tw": "失敗和恢復方式",
+            },
+            items: {
+              en: [
+                "If task submission fails, the page keeps your input so you can add context and retry.",
+                "If the backend does not return a structured result, the page shows the task id for support debugging.",
+                "If the backend returns a result for another tool or the structure does not match, the page will not display a fake success state.",
+                "The generated guide still needs human review for sensitive questions, recruit scope, and leading phrasing.",
+              ],
+              zh: [
+                "如果任务提交失败，页面会保留输入内容，补充上下文后可以重新生成。",
+                "如果后台没有返回结构化结果，页面会显示任务号，方便排查生成链路。",
+                "如果返回结果属于其他工具或结构不匹配，页面不会展示伪成功结果。",
+                "生成结果仍需人工检查敏感问题、受访者范围和是否过度诱导。",
+              ],
+              "zh-tw": [
+                "如果任務提交失敗，頁面會保留輸入內容，補充上下文後可以重新生成。",
+                "如果 Agent 沒有寫回結構化結果，頁面會顯示任務號，方便排查寫回鏈路。",
+                "如果返回結果類型或 schema 不匹配，頁面不會展示偽成功結果。",
+                "生成結果仍需人工檢查敏感問題、受訪者範圍和是否過度誘導。",
+              ],
+            },
+          },
+        ],
+      },
+      {
+        kind: "bullets",
+        heading: {
+          en: "How to use the guide during the interview",
+          zh: "访谈当天怎么用这份提纲",
+          "zh-tw": "如何使用生成結果",
+        },
+        image: {
+          src: "/tools/user-interview-guide-generator-result-use-pseo.webp",
+          alt: {
+            en: "Illustration of a researcher using an interview guide during a live customer conversation.",
+            zh: "研究者在现场访谈中使用提纲追问真实经历的插画。",
+            "zh-tw": "用戶訪談結果使用示意圖，展示從訪談提綱到記錄和洞察報告的鏈路。",
+          },
+          side: "right",
+          wide: true,
+        },
+        groups: [
+          {
+            items: {
+              en: [
+                "First check whether the research objective maps to a near-term product decision.",
+                "Use the participant criteria as a screener and filter out people without recent real experience.",
+                "During the interview, probe concrete behavior before explaining the solution.",
+                "After the interview, send the transcript to the record generator, then synthesize multiple records into insights.",
+              ],
+              zh: [
+                "先检查研究目标是否真的对应一个近期要做的产品决策。",
+                "用受访者条件写 screener，过滤掉没有最近真实经历的人。",
+                "访谈中按真实经历追问，不要急着解释你的方案。",
+                "访谈后把转写文本交给访谈记录生成器，再把多份记录合成洞察报告。",
+              ],
+              "zh-tw": [
+                "先檢查研究目標是否真的對應一個近期要做的產品決策。",
+                "用受訪者條件寫 screener，過濾掉沒有最近真實經歷的人。",
+                "訪談中按真實經歷追問，不要急著解釋你的方案。",
+                "訪談後把逐字稿交給訪談記錄生成器，再把多份記錄合成洞察報告。",
+              ],
+            },
+          },
+        ],
+      },
+      {
+        kind: "cards",
+        heading: {
+          en: "Why this is not a generic interview template",
+          zh: "为什么不是通用访谈模板",
+          "zh-tw": "為什麼用 Tomako 做這一步",
+        },
+        items: [
+          {
+            title: {
+              en: "Built around decisions, not documents",
+              zh: "面向决策，而不是面向文档",
+              "zh-tw": "面向決策，而不是面向文檔",
+            },
+            body: {
+              en: "The result ties questions, probes, signals, and handoff actions back to the product decision you need to make.",
+              zh: "结果会把问题、追问、信号和交接动作绑定到产品决策，减少“聊完但不知道怎么判断”的情况。",
+              "zh-tw": "結果會把問題、追問、信號和交接動作綁定到產品決策，減少“聊完但不知道怎麼判斷”的情況。",
+            },
+          },
+          {
+            title: { en: "Clear failure boundaries", zh: "有明确的失败边界", "zh-tw": "有明確的失敗邊界" },
+            body: {
+              en: "The page exposes missing information and review checks, and it does not pass off a local template as a generated result.",
+              zh: "页面会暴露缺失信息和复核点；拿不到合法结构化结果时不会把本地模板冒充为生成结果。",
+              "zh-tw": "頁面會暴露缺失資訊和複核點；拿不到合法結構化結果時不會把本地模板冒充為生成結果。",
+            },
+          },
+          {
+            title: {
+              en: "Connects to the research workflow",
+              zh: "能接到后续研究链路",
+              "zh-tw": "能接到後續研究鏈路",
+            },
+            body: {
+              en: "The same interview output can feed structured notes and multi-interview insight reports.",
+              zh: "同一套访谈结果可以继续进入记录整理和多场访谈洞察报告，减少手动重排证据的成本。",
+              "zh-tw": "同一套訪談結果可以繼續進入記錄整理和多場訪談洞察報告，減少手動重排證據的成本。",
+            },
+          },
+          {
+            title: { en: "Useful for small teams", zh: "适合小团队快速迭代", "zh-tw": "適合小團隊快速迭代" },
+            body: {
+              en: "Indie builders, PMs, and founders can get an executable draft, then calibrate it with one or two pilot interviews.",
+              zh: "独立开发者、PM 和创始人可以先拿到可执行草案，再用 1-2 场试访谈校准。",
+              "zh-tw": "獨立開發者、PM 和創始人可以先拿到可執行草案，再用 1-2 場試訪談校準。",
+            },
+          },
+        ],
+      },
+      {
+        kind: "bullets",
+        heading: {
+          en: "What a good interview guide should protect",
+          zh: "好访谈提纲应该保护什么",
+          "zh-tw": "好工具的判斷標準",
+        },
+        image: {
+          src: "/tools/user-interview-guide-generator-standard-pseo.webp",
+          alt: {
+            en: "Illustration of a branching probe tree connected to evidence signals and product decision criteria.",
+            zh: "访谈追问树连接到证据信号和产品决策标准的插画。",
+            "zh-tw": "好訪談工具標準示意圖，展示問題目的、追問和證據等級。",
+          },
+          side: "left",
+          wide: true,
+        },
+        groups: [
+          {
+            items: {
+              en: [
+                "When input is thin, the tool should expose the gap instead of generating confident filler.",
+                "The output should support recruiting, interviewing, note-taking, and review, not just advice.",
+                "Every question should have a purpose, probes, and an anti-leading reminder.",
+                "The result must be copyable, reviewable, handoff-ready, and tied to a task id for debugging.",
+              ],
+              zh: [
+                "输入不足时应该指出缺口，而不是生成看似完整的答案。",
+                "输出要能直接支持招募、访谈、记录和复盘，不只是一段建议。",
+                "每个问题都应该有目的、追问和反诱导提醒。",
+                "结果必须能复制、复核、交接，并保留任务号用于排查。",
+              ],
+              "zh-tw": [
+                "輸入不足時應該指出缺口，而不是生成看似完整的答案。",
+                "輸出要能直接支持招募、訪談、記錄和覆盤，不只是一段建議。",
+                "每個問題都應該有目的、追問和反誘導提醒。",
+                "結果必須能複製、複核、交接，並保留任務號用於排查。",
+              ],
+            },
+          },
+        ],
+      },
+    ],
+    faq: [
+      {
+        question: {
+          en: "Will this tell me whether the product is worth building?",
+          zh: "这个工具会直接告诉我产品是否值得做吗？",
+          "zh-tw": "這個工具會直接告訴我產品是否值得做嗎？",
+        },
+        answer: {
+          en: "No. It designs interviews that produce better evidence. The build decision still needs transcripts, behavior data, competition, technical cost, and real conversion tests.",
+          zh: "不会。它帮助你设计能获得证据的访谈。是否值得做还要结合访谈记录、行为数据、竞争、技术成本和真实转化实验。",
+          "zh-tw": "不會。它幫助你設計能獲得證據的訪談。是否值得做還要結合訪談記錄、行為數據、競爭、技術成本和真實轉化實驗。",
+        },
+      },
+      {
+        question: {
+          en: "Can I ask whether users would pay?",
+          zh: "可以直接问用户愿不愿意付费吗？",
+          "zh-tw": "可以直接問用戶願不願意付費嗎？",
+        },
+        answer: {
+          en: "Yes, but do not rely on stated intent alone. Past spending, current workaround, cost of the problem, and willingness to enter a next-step test matter more.",
+          zh: "可以问，但不能只看口头意愿。更重要的是过去是否付过钱、现在怎么解决、问题造成多大代价，以及是否愿意进入下一步测试。",
+          "zh-tw": "可以問，但不能只看口頭意願。更重要的是過去是否付過錢、現在怎麼解決、問題造成多大代價，以及是否願意進入下一步測試。",
+        },
+      },
+      {
+        question: {
+          en: "Can I interview users without a prototype?",
+          zh: "没有原型也能访谈吗？",
+          "zh-tw": "沒有原型也能訪談嗎？",
+        },
+        answer: {
+          en: "Yes. Without a prototype, discovery or problem validation is usually stronger. Reconstruct recent behavior before testing solution reactions.",
+          zh: "可以。没有原型时更适合做探索或问题验证，先还原用户最近一次真实经历，再决定是否值得做方案验证。",
+          "zh-tw": "可以。沒有原型時更適合做探索或問題驗證，先還原用戶最近一次真實經歷，再決定是否值得做方案驗證。",
+        },
+      },
+      {
+        question: {
+          en: "Why does the generated guide still need review?",
+          zh: "生成结果为什么还要人工复核？",
+          "zh-tw": "生成結果為什麼還要人工複核？",
+        },
+        answer: {
+          en: "Interviews affect recruiting, privacy, sensitive questions, and product judgment. Tomako drafts a structured guide, but your team still needs to check fit and compliance.",
+          zh: "访谈会影响招募、隐私、敏感问题和产品判断。Tomako 会生成结构化草案，但团队仍要确认问题是否合规、是否适合目标受访者。",
+          "zh-tw": "訪談會影響招募、隱私、敏感問題和產品判斷。Tomako 會生成結構化草案，但團隊仍要確認問題是否合規、是否適合目標受訪者。",
+        },
+      },
+    ],
+    cta: {
+      hint: {
+        en: "After the interview, turn the transcript into a structured record, then synthesize multiple records into insights.",
+        zh: "完成访谈后，把转写文本整理成结构化记录，再进入多场访谈洞察分析。",
+        "zh-tw": "完成訪談後，把逐字稿整理成結構化記錄，再進入多場訪談洞察分析。",
+      },
+      primary: {
+        href: "/tools/user-interview-record-generator",
+        label: { en: "Structure interview notes", zh: "整理访谈记录", "zh-tw": "整理訪談記錄" },
+      },
+      secondary: {
+        href: "/tools",
+        label: { en: "Back to all tools", zh: "返回全部工具", "zh-tw": "返回全部工具" },
+      },
+    },
+  },
+  assets: {
+    hero: {
+      src: "/tools/user-interview-guide-generator-hero-pseo.webp",
+      alt: {
+        en: "Illustration of a researcher preparing a product interview guide with a whiteboard, notebook, and evidence markers.",
+        zh: "研究者在白板和笔记本前准备产品用户访谈提纲的插画。",
+        "zh-tw": "用戶訪談提綱生成器界面，展示從研究目標到訪談問題和證據信號的流程。",
+      },
+    },
+  },
+};