Back to Details

blog-drafter

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Blog Drafter

博客起草工具

Interview the user to extract their unique perspective, then produce a structured draft with thesis, outline, and research suggestions.
通过访谈挖掘用户的独特视角，然后生成包含论点、大纲和研究建议的结构化初稿。

Process Overview

流程概述

Phase 1: Discovery Interview → Structured Draft + Research
Phase 2: Prose Refinement Interview (after user approves draft)
第一阶段：发现访谈 → 结构化初稿 + 研究建议
第二阶段：文字润色访谈（用户批准初稿后启动）

Phase 1: Discovery Interview

第一阶段：发现访谈

Opening

开场

Ask what topic they want to write about. If they've already stated it, acknowledge and move directly to the interview.
询问用户想要撰写的主题。如果用户已经说明主题，直接确认并进入访谈环节。

Interview Strategy

访谈策略

Use AskUserQuestion for structured choices. Use regular follow-up questions for open-ended exploration. Aim for 4-6 question rounds total.
Round 1: Core Thesis
AskUserQuestion:
  question: "What's the single most important thing you want readers to take away?"
  options:
    - "A specific insight or realization"
    - "A call to change behavior or practice"
    - "A framework or mental model"
    - "A contrarian or non-obvious take"
Then probe: "Can you state that in one sentence?"
Round 2: The "So What"
Ask directly: "Why should a PM, designer, or engineer care about this right now? What pain or opportunity does this address?"
Round 3: Evidence & Experience
AskUserQuestion:
  question: "What's your strongest evidence for this thesis?"
  options:
    - "Personal experience or case study"
    - "Data or research I've seen"
    - "Pattern I've observed across projects/companies"
    - "Logical argument from first principles"
Follow up: "Walk me through the specific example or evidence."
Round 4: Anticipated Resistance
Ask: "What's the strongest objection someone might raise? What would a skeptic say?"
Round 5: Unique Angle
AskUserQuestion:
  question: "What makes your perspective different from what's already written on this topic?"
  options:
    - "I have direct experience others don't"
    - "I'm connecting ideas that aren't usually connected"
    - "I disagree with conventional wisdom"
    - "I have a specific framework or process"
Round 6: Scope & Format
AskUserQuestion:
  question: "What length and depth feels right?"
  options:
    - "Short and punchy (800-1200 words)"
    - "Standard blog post (1500-2500 words)"
    - "Deep dive (3000+ words)"
使用AskUserQuestion提供结构化选项，通过常规跟进问题进行开放式探索。目标是完成4-6轮提问。
第一轮：核心论点
AskUserQuestion:
  question: "你希望读者从文章中获得的最核心的信息是什么？"
  options:
    - "一个具体的见解或感悟"
    - "一个改变行为或实践的倡议"
    - "一个框架或思维模型"
    - "一个反主流或不为人知的观点"
随后追问：“你能用一句话表述这个核心信息吗？”
第二轮：“意义何在”
直接询问：“为什么产品经理、设计师或工程师现在需要关注这个内容？它解决了什么痛点或带来了什么机会？”
第三轮：证据与经验
AskUserQuestion:
  question: "支撑你这个论点的最有力证据是什么？"
  options:
    - "个人经验或案例研究"
    - "我看到过的数据或研究结果"
    - "在多个项目/公司中观察到的模式"
    - "基于第一性原理的逻辑论证"
跟进提问：“请详细描述具体的例子或证据。”
第四轮：预期异议
询问：“有人可能提出的最强烈反对意见是什么？持怀疑态度的人会怎么说？”
第五轮：独特视角
AskUserQuestion:
  question: "与该主题已有的内容相比，你的视角有何独特之处？"
  options:
    - "我拥有他人不具备的直接经验"
    - "我正在关联通常不会被联系在一起的观点"
    - "我不同意传统观点"
    - "我有一个特定的框架或流程"
第六轮：范围与格式
AskUserQuestion:
  question: "合适的篇幅和深度是怎样的？"
  options:
    - "简短有力（800-1200字）"
    - "标准博客文章（1500-2500字）"
    - "深度剖析（3000字以上）"

Interview Principles

访谈原则

  • Listen for contradictions—they often reveal the real insight
  • When answers are abstract, ask for concrete examples
  • If the thesis sounds generic, push: "What would make someone disagree with this?"
  • Capture specific phrases and terminology the user employs
  • 留意矛盾点——它们往往能揭示真正的见解
  • 当回答较为抽象时，要求提供具体例子
  • 如果论点听起来过于通用，追问：“什么会让有人不同意这个观点？”
  • 记录用户使用的特定表述和术语

Phase 1 Output: Structured Draft

第一阶段输出：结构化初稿

After the interview, produce:
访谈结束后，生成以下内容：

1. Thesis Statement

1. 论点陈述

One clear sentence stating the core argument.
用一句清晰的话表述核心论点。

2. Draft Structure

2. 初稿结构

markdown
undefined
markdown
undefined

[Working Title]

[暂定标题]

Hook: [Opening that creates tension or curiosity]
Thesis: [Core argument, stated directly]
钩子：[制造紧张感或好奇心的开场]
论点：[直接表述核心论点]

Section 1: [Setup/Context]

第一节：[背景/上下文]

  • Key point
  • Key point
  • 关键点
  • 关键点

Section 2: [Core Argument/Evidence]

第二节：[核心论点/证据]

  • Key point with specific example from interview
  • Key point
  • 结合访谈中具体例子的关键点
  • 关键点

Section 3: [Addressing Objections]

第三节：[回应异议]

  • Anticipated resistance
  • Response
  • 预期的反对意见
  • 回应内容

Section 4: [Implications/Call to Action]

第四节：[启示/行动号召]

  • What readers should do differently
  • Why it matters
Closing: [Callback to hook or forward-looking statement]
undefined
  • 读者应做出的改变
  • 其重要性
结尾：[呼应钩子或前瞻性陈述]
undefined

3. Research Suggestions

3. 研究建议

Provide 3-5 specific suggestions:
  • Relevant studies, books, or articles to cite
  • Data points that would strengthen arguments
  • Examples from well-known companies/products that illustrate points
  • Experts or practitioners whose work relates to the thesis
Format as actionable items:
markdown
undefined
提供3-5条具体建议：
  • 可引用的相关研究、书籍或文章
  • 能强化论点的数据点
  • 能说明观点的知名公司/产品案例
  • 与论点相关的专家或从业者的研究成果
格式化为可执行事项：
markdown
undefined

Suggested Research

建议研究方向

  • Look for data on [specific metric/phenomenon] to support Section 2
  • Reference [Author]'s work on [topic] for theoretical grounding
  • Find a counter-example from [domain] to strengthen the objection response
  • Check if [Company] has published anything on their approach to [topic]
undefined
  • 查找关于[具体指标/现象]的数据以支撑第二节内容
  • 引用[作者]关于[主题]的研究作为理论基础
  • 从[领域]中寻找反例以强化异议回应部分
  • 查看[公司]是否发布过关于[主题]的相关方法
undefined

4. Open Questions

4. 待澄清问题

Note 2-3 areas where more depth or clarity would strengthen the piece.
After presenting the draft, ask: "Does this structure capture what you want to say? Any sections that feel wrong or missing?"
记录2-3个需要更深入或更清晰内容的领域，以增强文章质量。
提交初稿后，询问：“这个结构是否准确传达了你想要表达的内容？有没有觉得不合适或缺失的部分？”

Phase 2: Prose Refinement

第二阶段：文字润色

Trigger Phase 2 only after user approves the structure.
仅在用户批准结构后启动第二阶段。

Refinement Interview

润色访谈

Round 1: Tone
AskUserQuestion:
  question: "What tone fits this piece?"
  options:
    - "Conversational and accessible"
    - "Authoritative and direct"
    - "Provocative and opinionated"
    - "Thoughtful and nuanced"
Round 2: Opening Style
AskUserQuestion:
  question: "How do you like to open posts?"
  options:
    - "Start with a story or anecdote"
    - "Lead with the controversial claim"
    - "Open with a question"
    - "Set up a problem or tension"
Round 3: Technical Depth
Ask: "How much should I explain? Are readers already familiar with [key concepts from interview], or do they need context?"
Round 4: Specific Preferences
Ask: "Any writing patterns you like or hate? (e.g., 'I never use bullet points' or 'I always include code examples')"
第一轮：语气风格
AskUserQuestion:
  question: "这篇文章适合采用哪种语气？"
  options:
    - "口语化且通俗易懂"
    - "权威且直接"
    - "具有煽动性且立场鲜明"
    - "深思熟虑且细致入微"
第二轮：开场方式
AskUserQuestion:
  question: "你喜欢哪种文章开场方式？"
  options:
    - "以故事或轶事开头"
    - "以有争议的观点开头"
    - "以问题开头"
    - "提出问题或制造紧张感"
第三轮：技术深度
询问：“需要解释到什么程度？读者是否已经熟悉[访谈中提到的关键概念]，还是需要提供背景信息？”
第四轮：个性化偏好
询问：“你有任何喜欢或讨厌的写作模式吗？（例如：‘我从不使用项目符号’或‘我总会加入代码示例’）”

Refinement Output

润色输出

Expand the structure into full prose, incorporating:
  • The chosen tone throughout
  • The selected opening style
  • Appropriate technical depth
  • User's stated preferences
Mark areas where user's voice is needed:
markdown
[VOICE: Add your personal take on why this matters to you]
[EXAMPLE: Insert specific story from your experience here]
Remind user: "This is a starting point for your voice. The final pass is yours."
将结构扩展为完整的文字内容，融入以下元素：
  • 贯穿全文的选定语气
  • 选定的开场方式
  • 合适的技术深度
  • 用户提出的个性化偏好
标记需要用户补充个人风格的区域：
markdown
[个人风格：添加你对这个内容重要性的个人看法]
[示例：在此处插入你经历中的具体故事]
提醒用户：“这是一个供你融入个人风格的起点，最终的润色由你完成。”