Back to Details

write-better

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Writing guidance for AI agents

AI Agent写作指南

Write so the reader understands the point, the evidence, and the next action without rereading. Protect the reader's attention. Prefer plain language, concrete details, and useful structure.
撰写内容时，要确保读者无需重读就能理解核心观点、依据以及下一步行动。珍惜读者的注意力，优先使用平实语言、具体细节和实用结构。

1. Start with the useful part

1. 从核心有用信息切入

Put the main point in the first one or two sentences.
For professional communication, lead with one of these:
  • the request
  • the decision
  • the conclusion
  • the result
  • the problem
  • the relevant fact
Add context after the reader knows why they are reading.
Bad:
I wanted to reach out to provide some context regarding the project timeline.
Better:
The release will move from May 12 to May 19 because the payment tests are still failing.
Brief context may come first when the reader needs it to interpret sensitive, legal, safety-related, or surprising information correctly.
将核心观点放在开头一两句中。
对于专业沟通，可从以下内容入手：
  • 请求事项
  • 决策结果
  • 结论
  • 成果
  • 问题
  • 相关事实
在读者明确阅读目的后，再补充背景信息。
反面示例：
我想和你沟通一下项目时间线的相关背景。
正面示例：
由于支付测试仍未通过，发布日期将从5月12日推迟至5月19日。
当读者需要背景信息才能正确理解敏感、法律相关、安全相关或意外信息时，可先简要说明背景。

2. Make every sentence earn its place

2. 每句话都要有存在的价值

Every sentence should change what the reader knows, decides, or does.
A sentence may contribute:
  • a fact
  • a definition
  • a reason
  • evidence
  • a condition
  • a constraint
  • a consequence
  • an exception
  • a warning
  • a decision
  • an action
  • a concrete example
Delete sentences that only announce, emphasize, summarize, or decorate a point already made.
Common filler:
  • "That distinction matters."
  • "It is important to note that..."
  • "The practical mental model is simple."
  • "This highlights the importance of..."
  • "Here is what you need to know."
  • "In today's rapidly changing environment..."
  • "At its core..."
  • "The real question is..."
State the information instead.
每句话都应改变读者的认知、决策或行动。
一句话可起到以下作用：
  • 陈述事实
  • 给出定义
  • 说明原因
  • 提供依据
  • 列出条件
  • 指出限制
  • 说明后果
  • 标注例外
  • 发出警告
  • 告知决策
  • 明确行动
  • 给出具体示例
删除那些仅用于宣告、强调、总结或修饰已表达观点的句子。
常见冗余表达：
  • "这种区别很重要。"
  • "需要注意的是..."
  • "实用的思维模型很简单。"
  • "这凸显了...的重要性。"
  • "以下是你需要了解的内容。"
  • "在当今快速变化的环境中..."
  • "从本质上讲..."
  • "真正的问题是..."
直接陈述信息即可。

3. Preserve information, not length

3. 保留信息，而非篇幅

Keep the original facts, requirements, qualifications, and necessary examples.
You may:
  • delete empty sentences
  • merge paragraphs
  • remove repeated explanations
  • shorten examples
  • reorder information
  • replace abstractions with concrete language
Do not preserve the original paragraph count or sentence count. A padded five-paragraph draft may need to become two paragraphs.
保留原文的事实、要求、限定条件和必要示例。
你可以：
  • 删除空洞句子
  • 合并段落
  • 移除重复解释
  • 精简示例
  • 调整信息顺序
  • 用具体语言替代抽象表述
无需保留原文的段落数或句子数。一篇冗余的五段式草稿可能只需精简为两段。

4. Use plain language

4. 使用平实语言

Prefer familiar words and direct constructions.
Use:
  • "use" instead of "utilize"
  • "help" instead of "facilitate"
  • "improve" instead of "enhance"
  • "use" instead of "leverage"
  • "is" instead of "serves as"
  • "has" instead of "boasts"
  • "can" instead of "has the ability to"
Treat these words as warnings:
delve, leverage, robust, seamless, streamline, utilize, comprehensive, holistic, facilitate, optimize, harness, navigate, landscape, realm, foster, empower, crucial, essential, pivotal, significantly
Keep one when it has a precise technical meaning. Remove it when it adds polish without precision.
Good:
The compiler optimizes repeated lookups.
Weak:
The platform optimizes the customer journey through seamless automation.
优先使用常见词汇和直接句式。
例如：
  • 用"使用"替代"utilize"
  • 用"帮助"替代"facilitate"
  • 用"改进"替代"enhance"
  • 用"使用"替代"leverage"
  • 用"是"替代"serves as"
  • 用"拥有"替代"boasts"
  • 用"可以"替代"has the ability to"
以下词汇需谨慎使用：
delve, leverage, robust, seamless, streamline, utilize, comprehensive, holistic, facilitate, optimize, harness, navigate, landscape, realm, foster, empower, crucial, essential, pivotal, significantly
当这些词汇具有精准技术含义时保留，若仅为修饰而无实际意义则删除。
正面示例：
编译器会优化重复查找操作。
反面示例：
该平台通过无缝自动化优化客户旅程。

5. Be concrete

5. 内容要具体

Use names, dates, numbers, owners, systems, and observable actions.
Weak:
We should improve cross-functional alignment to streamline delivery.
Better:
Priya will send the revised API schema to the mobile team by Tuesday. The team will confirm the migration date by Thursday.
Prefer language the reader can picture happening.
Replace abstract nouns with actions when possible:
  • "conduct an evaluation of" becomes "evaluate"
  • "make a determination" becomes "decide"
  • "provide assistance" becomes "help"
  • "perform an inspection" becomes "inspect"
使用名称、日期、数字、负责人、系统名称和可观察的行动。
反面示例：
我们应改善跨职能协作以简化交付流程。
正面示例：
Priya将于周二前将修订后的API schema发送给移动端团队，该团队需在周四前确认迁移日期。
优先使用读者能具象化的表述。
尽可能将抽象名词转化为动作：
  • "conduct an evaluation of" 改为 "评估"
  • "make a determination" 改为 "决定"
  • "provide assistance" 改为 "帮助"
  • "perform an inspection" 改为 "检查"

6. Put actions in usable form

6. 让行动指令清晰可用

For requests, specify:
  • who should act
  • what they should do
  • when it is due
  • what completion looks like
Weak:
Let me know your thoughts.
Better:
Please confirm the revised launch date by Thursday at 3 p.m.
Prefer one main outcome per message. Several related actions may appear together when each one is explicit. Number them when order, ownership, or completion matters.
对于请求类内容，需明确：
  • 行动负责人
  • 具体行动内容
  • 截止时间
  • 完成标准
反面示例：
告诉我你的想法。
正面示例：
请于周四下午3点前确认修订后的发布日期。
优先确保每条信息对应一个核心目标。当多个相关行动均明确时，可放在一起；若行动的顺序、负责人或完成状态很重要，可进行编号。

7. Match the genre

7. 匹配内容类型

Clarity does not require the same voice everywhere.
For documentation:
  • describe current behavior
  • explain how to use it
  • state constraints and failure conditions
  • include examples only when they remove ambiguity
  • avoid promotional language and personality
For workplace messages:
  • use the tone appropriate to the relationship
  • keep politeness brief
  • make the request easy to identify
  • avoid unnecessary formality
For essays and personal writing:
  • preserve genuine opinions, uncertainty, humor, and irregularities
  • do not manufacture quirks to appear human
  • do not add tangents, fragments, or fake self-corrections unless they belong to the author's voice
Match the genre before matching stylistic mannerisms.
不同场景下，清晰表达的要求也不同。
对于文档：
  • 描述当前行为
  • 说明使用方法
  • 列出限制条件和失败场景
  • 仅在消除歧义时添加示例
  • 避免使用宣传性语言和个性化表达
对于职场消息：
  • 使用符合人际关系的语气
  • 保持礼貌但简洁
  • 让请求易于识别
  • 避免不必要的正式表述
对于文章和个人写作：
  • 保留真实观点、不确定性、幽默感和独特表达
  • 不要为了显得人性化而刻意制造怪异表述
  • 除非属于作者的表达风格，否则不要添加题外话、片段化内容或虚假的自我修正
先匹配内容类型，再调整风格细节。

8. Preserve the author's voice

8. 保留作者的表达风格

When a writing sample is available, study:
  • sentence length
  • vocabulary
  • paragraph openings
  • punctuation
  • degree of formality
  • transition habits
  • humor
  • recurring phrases
Keep meaningful irregularities. Do not replace the author's voice with a generic casual style.
Do not add personality merely to signal that a human wrote the text.
若有作者的写作样本，需关注：
  • 句子长度
  • 词汇选择
  • 段落开头方式
  • 标点使用
  • 正式程度
  • 过渡习惯
  • 幽默感
  • 常用短语
保留有意义的独特表达，不要用通用的随意风格替代作者的原有风格。
不要为了伪装成人类写作而刻意添加个性化内容。

9. Avoid rhetorical packaging

9. 避免修辞包装

Do not turn ordinary information into slogans, aphorisms, or miniature speeches.
Avoid formulas such as:
  • "It is not X. It is Y."
  • "It is not just about X. It is about Y."
  • "X is the language of Y."
  • "X becomes a trap."
  • "The future of X is Y."
  • "What really matters is..."
  • "The heart of the matter is..."
Use corrective contrast only when the reader is likely to hold the mistaken belief and correcting it affects their actions.
Weak:
This is not merely a performance improvement. It is a transformation of the developer experience.
Better:
The change reduces build time from 11 minutes to 4 minutes.
不要将普通信息转化为口号、格言或小型演讲。
避免使用以下句式：
  • "这不是X，而是Y。"
  • "这不仅仅是关于X，更是关于Y。"
  • "X是Y的语言。"
  • "X变成了陷阱。"
  • "X的未来是Y。"
  • "真正重要的是..."
  • "问题的核心是..."
仅当读者可能持有错误认知且纠正该认知会影响其行动时，才使用对比纠正。
反面示例：
这不仅仅是性能提升，更是开发者体验的变革。
正面示例：
此次更改将构建时间从11分钟缩短至4分钟。

10. Do not manufacture emphasis

10. 不要刻意强调

Avoid unsupported claims that something is important, significant, pivotal, profound, or transformative.
Explain the consequence.
Weak:
This is a crucial change for the organization.
Better:
Without this change, the company cannot process EU customer data after September 1.
The facts should carry the emphasis.
避免无依据地宣称某事重要、关键、深远或具有变革性。
直接说明后果即可。
反面示例：
这对组织来说是一项关键变革。
正面示例：
若不进行此次更改，公司将无法在9月1日后处理欧盟客户的数据。
事实本身就具有说服力。

11. Control metadiscourse

11. 控制元话语

Metadiscourse tells the reader how to interpret the writing rather than giving them the information.
Common forms:
  • "This means..."
  • "That distinction..."
  • "In other words..."
  • "It is worth noting..."
  • "The key point..."
  • "As we can see..."
  • "Let us explore..."
  • "Now let us look at..."
Use these only when they resolve a real structural ambiguity. Do not place them at the start of each paragraph to create artificial continuity.
Do not open by announcing how many points will follow when the count adds no information.
Weak:
Three things to know. First, the migration pauses writes.
Better:
The migration pauses writes for five minutes.
Use a count when it helps the reader navigate numbered steps, track requirements, or understand that the quantity matters.
Check paragraph openings that begin with "This" or "That." Make sure the paragraph advances the explanation rather than renaming the previous one.
元话语是指导读者如何解读内容，而非直接提供信息的表述。
常见形式：
  • "这意味着..."
  • "这种区别..."
  • "换句话说..."
  • "值得注意的是..."
  • "核心观点是..."
  • "正如我们所见..."
  • "让我们探讨..."
  • "现在来看..."
仅当这些表述能解决实际的结构歧义时才使用，不要在每个段落开头使用它们来制造虚假的连贯性。
不要在开头宣布要点数量，除非该数量能提供有效信息。
反面示例：
有三件事需要了解。首先，迁移会暂停写入操作。
正面示例：
迁移会暂停写入操作五分钟。
当数量有助于读者导航编号步骤、跟踪要求或理解数量的重要性时，再使用计数。
检查以"This"或"That"开头的段落，确保段落是推进解释而非重复之前的内容。

12. Avoid semantic repetition

12. 避免语义重复

Do not repeat a claim merely with different vocabulary.
A restatement should add at least one of these:
  • greater precision
  • a necessary example
  • a consequence
  • a limit
  • an exception
  • an operational instruction
Delete paraphrase chains that explain the same point several times.
不要仅通过更换词汇来重复观点。
重述内容应至少添加以下一项：
  • 更高的精准度
  • 必要示例
  • 后果
  • 限制
  • 例外
  • 操作指令
删除多次解释同一观点的 paraphrase 链。

13. Use lists only when the structure helps

13. 仅在结构有帮助时使用列表

Use a list when the reader needs to:
  • compare items
  • follow steps
  • check requirements
  • identify owners
  • scan options
Do not force ideas into groups of three. Do not add a third item for rhythm or completeness.
Avoid long lists with bold labels when a sentence or table would be easier to read.
当读者需要以下操作时使用列表：
  • 比较条目
  • 遵循步骤
  • 核对要求
  • 确定负责人
  • 浏览选项
不要强行将想法分成三组，不要为了节奏或完整性而添加第三个条目。
当句子或表格更易读时，避免使用带有粗体标签的长列表。

14. Let sentence structure follow the information

14. 让句式结构匹配信息

Avoid a uniform run of medium-length sentences. Also avoid forced alternation between short and long sentences.
Do not add fragments or dramatic pauses merely to vary the rhythm.
Read the passage aloud. Revise it when:
  • every sentence has the same shape
  • clauses arrive in repeated groups of three
  • each paragraph ends with a punchline
  • several short sentences manufacture drama
  • the prose ticks with an obvious pattern
Sentence length should reflect the amount and relationship of the information.
避免统一使用中等长度的句子，也避免刻意交替使用长短句。
不要为了改变节奏而添加片段化内容或戏剧性停顿。
大声朗读段落，若出现以下情况则进行修改：
  • 每个句子结构相同
  • 从句以重复的三组形式出现
  • 每个段落都以点睛之笔结尾
  • 多个短句刻意制造戏剧性
  • 文本带有明显的模式化节奏
句子长度应反映信息的数量和关联度。

15. Use direct subjects and verbs

15. 使用直接的主语和动词

Name the actor when responsibility matters.
Weak:
The request was reviewed and a decision was made.
Better:
The security team reviewed the request and rejected it.
Passive voice is acceptable when the actor is unknown, irrelevant, already understood, or less important than the process.
Acceptable:
Tokens are deleted after 30 days.
The problem is unclear responsibility, not passive grammar itself.
Systems and tools may be the subject when the verb describes observable behavior.
Acceptable:
The API returns JSON.
Do not give software human intentions, beliefs, or desires unless that description is literally accurate.
Weak:
The platform wants to guide users through setup.
Better:
The onboarding flow shows each setup step in order.
当责任很重要时，明确行动主体。
反面示例：
请求已被审阅，且已做出决策。
正面示例：
安全团队审阅了请求并予以驳回。
当行动主体未知、无关、已明确或不如流程重要时，可使用被动语态。
合理示例：
令牌将在30天后被删除。
问题在于责任不明确，而非被动语法本身。
当动词描述可观察的行为时，系统和工具可作为主语。
合理示例：
API返回JSON格式数据。
不要赋予软件人类的意图、信念或欲望，除非该描述完全准确。
反面示例：
该平台希望引导用户完成设置。
正面示例：
引导流程会按顺序展示每个设置步骤。

16. Do not cycle through synonyms

16. 不要刻意替换同义词

Repeat the correct term when precision matters.
Weak:
The customer submits a request. The user then receives a response. The account holder can review the result.
Better:
The customer submits a request, receives the response, and reviews the result.
Technical writing benefits from stable terminology.
当精准度很重要时，重复使用正确术语。
反面示例：
客户提交请求。用户随后收到回复。账户持有人可查看结果。
正面示例：
客户提交请求、收到回复并查看结果。
技术写作受益于稳定的术语。

17. Remove fake depth

17. 去除虚假深度

Watch for participial phrases that add interpretation without evidence:
  • highlighting
  • underscoring
  • reflecting
  • showcasing
  • symbolizing
  • fostering
  • contributing to
  • ensuring
Weak:
The redesign uses blue and green, reflecting the company's commitment to trust and growth.
Better:
The redesign uses blue and green. The design brief identifies them as the company's existing brand colors.
Do not infer symbolism, intention, or significance without a source.
注意那些添加无依据解读的分词短语：
  • highlighting
  • underscoring
  • reflecting
  • showcasing
  • symbolizing
  • fostering
  • contributing to
  • ensuring
反面示例：
此次重新设计使用了蓝色和绿色，体现了公司对信任与增长的承诺。
正面示例：
此次重新设计使用了蓝色和绿色。设计 brief 指出这些是公司现有的品牌色。
不要在无来源的情况下推断象征意义、意图或重要性。

18. Avoid vague authority

18. 避免模糊的权威表述

Do not write:
  • "Experts say..."
  • "Observers have noted..."
  • "Industry reports suggest..."
  • "Critics argue..."
  • "Research shows..."
Name the source and state the finding.
Better:
In its 2025 survey of 640 developers, Stack Overflow found that 42 percent checked AI-generated code less carefully when working under deadline pressure.
When no reliable source exists, remove the claim or state the uncertainty plainly.
不要写：
  • "专家表示..."
  • "观察者指出..."
  • "行业报告显示..."
  • "批评者认为..."
  • "研究表明..."
明确来源并陈述研究结果。
正面示例：
Stack Overflow在2025年对640名开发者的调查中发现，42%的开发者在截止日期压力下，对AI生成代码的检查会更不仔细。
若无可靠来源，删除该声明或明确说明不确定性。

19. Avoid promotional language

19. 避免宣传性语言

Documentation and factual writing should not sound like advertising.
Remove phrases such as:
  • groundbreaking
  • vibrant
  • breathtaking
  • renowned
  • world-class
  • powerful and intuitive
  • rich history
  • commitment to excellence
  • exciting journey
  • bright future
Replace praise with observable details.
Weak:
The platform delivers a seamless and powerful experience.
Better:
The platform imports CSV files up to 2 GB and reports row-level validation errors.
文档和事实性写作不应听起来像广告。
删除以下短语：
  • groundbreaking
  • vibrant
  • breathtaking
  • renowned
  • world-class
  • powerful and intuitive
  • rich history
  • commitment to excellence
  • exciting journey
  • bright future
用可观察的细节替代赞美。
反面示例：
该平台提供无缝且强大的体验。
正面示例：
该平台可导入最大2GB的CSV文件，并报告行级验证错误。

20. Use punctuation plainly

20. 平实使用标点

Do not use em dashes.
Replace them with:
  • a period for a separate thought
  • a comma for a short interruption
  • a colon for an explanation
  • parentheses for a true aside
Do not use punctuation to manufacture drama.
Preserve conventional en dashes only when the applicable style guide requires them for ranges or compound relationships. A house style may replace those too.
不要使用破折号（em dashes）。
用以下方式替代：
  • 用句号分隔独立想法
  • 用逗号分隔简短插入语
  • 用冒号引出解释
  • 用括号标注真正的题外话
不要用标点制造戏剧性。
仅当适用的风格指南要求使用短破折号（en dashes）表示范围或复合关系时才保留，内部风格也可能替代它们。

21. Keep formatting functional

21. 保持格式实用

Avoid:
  • mechanical boldface
  • emojis in professional headings
  • title case for every heading
  • decorative callouts
  • a heading followed by a sentence that merely repeats it
  • repeated "Key takeaway" boxes
  • unnecessary conclusion sections
Use sentence case for headings unless the established style guide requires otherwise.
Formatting should make the information easier to find.
避免：
  • 机械性加粗
  • 专业标题中使用表情符号
  • 每个标题都使用标题大小写
  • 装饰性提示框
  • 标题后仅重复标题内容的句子
  • 重复的"关键要点"框
  • 不必要的结论部分
除非既定风格指南要求，否则标题使用句子大小写。
格式应便于查找信息。

22. Keep politeness proportionate

22. 保持礼貌适度

Use enough courtesy to maintain the relationship. Stop there.
Avoid:
  • "I hope this message finds you well."
  • "Please do not hesitate to reach out."
  • "I would be more than happy to..."
  • "I was wondering if perhaps..."
  • "Of course!"
  • "Absolutely!"
  • "Great question!"
One greeting and one "thanks" are usually enough.
Direct does not mean rude. State the request clearly and respect the reader's time.
使用足够的礼貌维持人际关系即可，无需过度。
避免：
  • "希望你一切安好。"
  • "如有疑问，请勿犹豫随时联系我。"
  • "我非常乐意..."
  • "我想知道是否..."
  • "当然！"
  • "绝对！"
  • "好问题！"
通常一句问候和一句感谢就足够了。
直接并不意味着粗鲁。清晰陈述请求，尊重读者的时间。

23. Handle uncertainty honestly

23. 诚实地处理不确定性

State what is known, what is unknown, and what would resolve the uncertainty.
Good:
The logs show that the request failed after authentication. They do not show whether the upstream service timed out. We need the gateway logs to confirm that.
Do not fill gaps with plausible background, vague biography, or generic explanations.
Avoid stacked hedging:
It could potentially possibly be...
Use the narrowest accurate qualifier:
  • may
  • probably
  • appears to
  • the available evidence suggests
说明已知内容、未知内容以及解决不确定性的方法。
正面示例：
日志显示请求在认证后失败，但未显示上游服务是否超时。我们需要网关日志来确认这一点。
不要用看似合理的背景、模糊的描述或通用解释填补空白。
避免堆砌模糊限定词：
这可能或许大概是...
使用最精准的限定词：
  • 可能
  • 大概
  • 似乎
  • 现有证据表明

24. Describe the current state

24. 描述当前状态

Documentation and comments should usually explain how the system works now.
Weak:
This function was added to replace the previous implementation, which iterated through every item.
Better:
This function uses a hash map for constant-time lookups.
Narrate the change only in changelogs, release notes, migration guides, incident reports, or historical explanations.
文档和注释通常应说明系统当前的工作方式。
反面示例：
该函数是为了替换之前遍历每个条目的实现而添加的。
正面示例：
该函数使用哈希表实现常数时间查找。
仅在变更日志、发布说明、迁移指南、事件报告或历史解释中叙述变更。

25. End when the work is done

25. 适可而止

Do not add a generic conclusion after the necessary information.
Avoid:
  • "In conclusion..."
  • "The future looks bright."
  • "This is a step in the right direction."
  • "Exciting times lie ahead."
  • "I hope this helps."
  • "Let me know if you have any questions."
End with the result, the decision, the deadline, or the next action.
在提供必要信息后，不要添加通用结论。
避免：
  • "综上所述..."
  • "未来一片光明。"
  • "这是正确方向上的一步。"
  • "激动人心的时刻即将到来。"
  • "希望这对你有帮助。"
  • "如有任何问题，请告诉我。"
以结果、决策、截止日期或下一步行动结尾。

Editing process

编辑流程

Use this process internally unless the user asks to see the analysis.
除非用户要求查看分析过程，否则内部使用此流程。

First pass: meaning

第一轮：核心含义

Identify:
  • the main point
  • required facts
  • decisions
  • constraints
  • uncertainties
  • actions
  • deadlines
Remove unsupported claims and invented details.
确认：
  • 核心观点
  • 必要事实
  • 决策
  • 限制条件
  • 不确定性
  • 行动
  • 截止日期
删除无依据的声明和编造的细节。

Second pass: structure

第二轮：结构调整

Move the main point to the beginning.
Group related information. Delete repetition. Merge weak paragraphs. Add headings only when they improve navigation.
将核心观点移至开头。
整合相关信息，删除重复内容，合并薄弱段落，仅在提升导航性时添加标题。

Third pass: language

第三轮：语言优化

Replace:
  • abstract nouns with verbs
  • vague claims with specifics
  • ceremonial language with direct language
  • promotional wording with observable facts
  • synonym cycling with stable terms
替换：
  • 抽象名词为动词
  • 模糊声明为具体内容
  • 客套语言为直接表述
  • 宣传性措辞为可观察事实
  • 同义词替换为稳定术语

Fourth pass: rhetoric

第四轮：修辞修正

Remove:
  • slogans
  • forced contrasts
  • aphorisms
  • rules of three
  • artificial punchlines
  • significance claims
  • empty transitions
  • fake-candid openers
  • tutorial-style announcements
删除：
  • 口号
  • 刻意对比
  • 格言
  • 三段式规则
  • 人为点睛之笔
  • 重要性宣称
  • 空泛过渡语
  • 虚假坦诚的开头
  • 教程式宣告

Fifth pass: rhythm and punctuation

第五轮：节奏与标点

Read the text aloud.
Check for:
  • uniform sentence length
  • repeated sentence patterns
  • stacked fragments
  • excessive parenthetical material
  • em dashes
  • dramatic punctuation
  • paragraphs that end too neatly
Revise only where the rhythm interferes with clarity or sounds manufactured.
大声朗读文本。
检查：
  • 统一的句子长度
  • 重复的句式
  • 堆叠的片段化内容
  • 过多的插入语
  • 破折号
  • 戏剧性标点
  • 过于刻意收尾的段落
仅当节奏影响清晰度或显得刻意时才进行修改。

Final pass: reader test

最终轮：读者测试

Ask:
  1. Can the reader identify the main point immediately?
  2. Does each sentence add useful information?
  3. Are actions, owners, and deadlines explicit?
  4. Can any sentence be deleted without loss?
  5. Does the tone fit the relationship and genre?
  6. Is any phrase present mainly because it sounds polished?
  7. Has the text preserved the author's actual voice?
  8. Does the ending stop at the right place?
Return the final version. Do not expose drafts, audits, or self-critique unless requested.
提问：
  1. 读者能否立即识别核心观点？
  2. 每句话是否都添加了有用信息？
  3. 行动、负责人和截止日期是否明确？
  4. 是否有句子可删除而不损失信息？
  5. 语气是否符合人际关系和内容类型？
  6. 是否存在仅为了显得精致而添加的短语？
  7. 是否保留了作者的真实表达风格？
  8. 结尾是否恰到好处？
返回最终版本，除非用户要求，否则不要展示草稿、审核或自我批判内容。