Back to Details

article-writing

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Article Writing

文章写作

Write long-form content that sounds like a real person or brand, not generic AI output.
撰写读起来像真实个人或品牌输出的长文本内容，而非通用的AI生成内容。

When to Activate

激活场景

  • drafting blog posts, essays, launch posts, guides, tutorials, or newsletter issues
  • turning notes, transcripts, or research into polished articles
  • matching an existing founder, operator, or brand voice from examples
  • tightening structure, pacing, and evidence in already-written long-form copy
  • 起草博客帖、随笔、发布帖、指南、教程或通讯刊文
  • 将笔记、转录文本或研究内容整理为打磨精良的文章
  • 匹配已有创始人、运营人员或品牌的示例风格
  • 优化已完成长文案的结构、节奏和论据支撑

Core Rules

核心规则

  1. Lead with the concrete thing: example, output, anecdote, number, screenshot description, or code block.
  2. Explain after the example, not before.
  3. Prefer short, direct sentences over padded ones.
  4. Use specific numbers when available and sourced.
  5. Never invent biographical facts, company metrics, or customer evidence.
  1. 以具体内容开篇：示例、输出内容、轶事、数据、截图描述或代码块。
  2. 先给出示例再做解释，而非先解释再给示例。
  3. 优先使用简短直接的句子，避免冗余堆砌。
  4. 有可靠来源时使用具体数据。
  5. 绝对不要虚构传记类事实、公司指标或客户佐证信息。

Voice Capture Workflow

风格捕捉工作流

If the user wants a specific voice, collect one or more of:
  • published articles
  • newsletters
  • X / LinkedIn posts
  • docs or memos
  • a short style guide
Then extract:
  • sentence length and rhythm
  • whether the voice is formal, conversational, or sharp
  • favored rhetorical devices such as parentheses, lists, fragments, or questions
  • tolerance for humor, opinion, and contrarian framing
  • formatting habits such as headers, bullets, code blocks, and pull quotes
If no voice references are given, default to a direct, operator-style voice: concrete, practical, and low on hype.
如果用户需要特定风格，收集以下一项或多项参考：
  • 已发布的文章
  • 通讯内容
  • X / LinkedIn 帖子
  • 文档或备忘录
  • 简短的风格指南
然后提取以下特征：
  • 句子长度和节奏
  • 风格是正式、口语化还是尖锐犀利
  • 偏好的修辞手法，比如括号、列表、碎片化表达、设问等
  • 对幽默、个人观点、反传统叙事的接受度
  • 排版习惯，比如标题、项目符号、代码块、引用块的使用
如果没有提供风格参考，默认使用直接的运营人员风格：具体、实用、少夸大宣传。

Banned Patterns

禁用模式

Delete and rewrite any of these:
  • generic openings like "In today's rapidly evolving landscape"
  • filler transitions such as "Moreover" and "Furthermore"
  • hype phrases like "game-changer", "cutting-edge", or "revolutionary"
  • vague claims without evidence
  • biography or credibility claims not backed by provided context
删除并重写任何符合以下特征的内容：
  • 通用开篇，比如"在当今快速发展的格局下"
  • 冗余过渡词，比如"此外"、"再者"
  • 夸大性短语，比如"游戏规则改变者"、"前沿"、"革命性的"
  • 没有证据支撑的模糊主张
  • 没有提供上下文支撑的传记或可信度声明

Writing Process

写作流程

  1. Clarify the audience and purpose.
  2. Build a skeletal outline with one purpose per section.
  3. Start each section with evidence, example, or scene.
  4. Expand only where the next sentence earns its place.
  5. Remove anything that sounds templated or self-congratulatory.
  1. 明确受众和写作目的。
  2. 搭建大纲框架，每个板块对应一个核心目的。
  3. 每个板块以证据、示例或场景开篇。
  4. 仅在内容有存在价值时再扩充内容。
  5. 删除任何听起来像模板化或自吹自擂的内容。

Structure Guidance

结构指南

Technical Guides

技术指南

  • open with what the reader gets
  • use code or terminal examples in every major section
  • end with concrete takeaways, not a soft summary
  • 开篇点明读者能收获的内容
  • 每个主要板块都使用代码或终端示例
  • 结尾给出具体的要点总结，而非空泛的概述

Essays / Opinion Pieces

随笔 / 观点类文章

  • start with tension, contradiction, or a sharp observation
  • keep one argument thread per section
  • use examples that earn the opinion
  • 以冲突、矛盾或尖锐的观察开篇
  • 每个板块保持一条核心论证线
  • 使用可以支撑观点的示例

Newsletters

通讯

  • keep the first screen strong
  • mix insight with updates, not diary filler
  • use clear section labels and easy skim structure
  • 首屏内容要有吸引力
  • 混合洞见和更新内容，不要放日记式的冗余内容
  • 使用清晰的板块标签和便于快速浏览的结构

Quality Gate

质量校验

Before delivering:
  • verify factual claims against provided sources
  • remove filler and corporate language
  • confirm the voice matches the supplied examples
  • ensure every section adds new information
  • check formatting for the intended platform
交付前：
  • 根据提供的来源核对事实性主张
  • 删除冗余内容和企业套话
  • 确认风格和提供的示例匹配
  • 确保每个板块都提供了新信息
  • 检查排版是否符合目标平台的要求