write-content

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Write Content

撰写内容

Writes a complete SEO-optimized article. Four phases: research → content type decision → knowledge extraction → write. Includes the full anti-AI-slop ruleset and the voice rules that make the output sound like a practitioner, not a press release.

撰写一篇完整的SEO优化文章。分为四个阶段：调研→内容类型决策→知识提取→撰写。包含全套反AI垃圾内容规则集，以及让输出内容听起来像从业者而非新闻稿的语气规则。

Input

输入

Topic or target keyword (required)
(Optional) An existing content brief — skip the research phase if provided
(Optional) Expert interview output from the
```
expert-interview
```
skill

If no topic is given, ask for one before proceeding.

主题或目标关键词（必填） -（可选）现有内容brief——若提供则跳过调研阶段 -（可选）来自
```
expert-interview
```
技能的专家访谈输出

若未提供主题，请先询问用户获取。

Business context persistence

业务上下文持久化

Business context (audience, tone, language, brand voice, examples) shapes every article. Don't re-ask these questions every session.

First use: ask 4-5 questions and save the answers somewhere persistent in your agent's environment. Use the safest default first:

Claude Code:
```
~/.claude/projects/<path>/memory/business-context.md
```
is the recommended default. Do NOT write to
```
./CLAUDE.md
```
unless the user explicitly asks for it —
```
CLAUDE.md
```
is the user's project instructions file and appending unsolicited content to it can surprise them on every subsequent agent turn.
Claude Desktop / Claude.ai: save to a Project's context or a pinned note.
Cursor:
```
.cursor/rules/business-context.md
```
.
Any other agent:
```
seo-context.md
```
in the working directory.

Always confirm the write location with the user before saving. If any of these are unavailable or the user objects, fall back to re-asking the questions each session.

Every use after that: load that file first. If missing, ask where the user saved it or re-ask the questions.

Questions on first use:

What does the business do, and who is it for?
What's the brand's tone of voice? (Professional / Casual / Technical / Authoritative / Conversational)
What language should content be written in?
What topics should NEVER appear? (compliance, competitor mentions, etc.)
Who are the 2-3 main competitors?

业务上下文（受众、语气、语言、品牌风格、示例）会影响每一篇文章。无需在每次会话中重复询问这些问题。

首次使用：询问4-5个问题，并将答案保存在Agent环境中的持久化位置。优先使用最安全的默认路径：

Claude Code：推荐默认路径为
```
~/.claude/projects/<path>/memory/business-context.md
```
。除非用户明确要求，否则不要写入
```
./CLAUDE.md
```
——
```
CLAUDE.md
```
是用户的项目说明文件，未经请求向其中追加内容会在后续每次Agent交互时给用户带来意外。
Claude Desktop / Claude.ai：保存到项目上下文或固定笔记中。
Cursor：
```
.cursor/rules/business-context.md
```
。
其他Agent：工作目录下的
```
seo-context.md
```
。

保存前务必与用户确认写入位置。若上述路径不可用或用户反对，则退回到每次会话重新询问问题。

后续每次使用：先加载该文件。若文件缺失，询问用户保存位置或重新询问问题。

首次使用时的问题：

该业务从事什么领域，面向哪些受众？
品牌的语气风格是什么？（专业/随意/技术/权威/对话式）
内容应使用哪种语言撰写？
绝对不能涉及哪些主题？（合规、竞品提及等）
主要竞争对手有哪2-3家？

Phase 1: Research

阶段1：调研

If a content brief wasn't provided, Google the topic and read the top 5 results. Note: what formats are ranking, what angles exist, what gaps you see. 3-5 bullet points, not a full brief.

Skip this phase entirely if a brief or prior conversation context already contains SERP analysis.

若未提供内容brief，则针对主题进行谷歌搜索并阅读排名前五的结果。记录：排名内容的格式、现有角度、发现的空白。用3-5个要点列出，无需完整brief。

若brief或之前的对话上下文已包含SERP分析，则完全跳过此阶段。

Phase 2: Content Type Decision

阶段2：内容类型决策

Based on what's ranking, pick a content type: how-to, definition/explainer, comparison (X vs Y), listicle/roundup, product review, case study, pillar/ultimate guide, FAQ, landing page, service page, news/trend analysis.

State it plainly: "The top results for [keyword] are all [format]. I'll write a [content type] with [key structural element]. Sound good, or did you have something else in mind?"

Wait for confirmation.

Load

references/content-types-overview.md

for the decision table covering all 23 content types. Then load the specific template from

references/content-types/<type>.md

(e.g.,

references/content-types/how-to.md

) for H1/H2 structure, schema, featured snippet format, CTA placement, word count targets. The 19 content types bundled as full templates: how-to, definition, comparison, listicle, pillar-page, faq-page, landing-page, service-page, case-study, statistics-page, news-article, glossary-page, alternatives-page, buying-guide, product-page, category-page, integration-page, location-page, programmatic-page. For the 4 types covered only by the overview table (thought-leadership, product-reviews, pricing-pages, about-pages), those live under

eeat-audit/references/content-types/

because the E-E-A-T bar for them is the load-bearing factor.

根据排名情况选择内容类型：操作指南、定义/解释文、对比文（X vs Y）、清单/汇总文、产品评测、案例研究、核心/终极指南、FAQ、着陆页、服务页、新闻/趋势分析。

直接说明： "[关键词]的排名结果均为[格式]。我将撰写一篇[内容类型]，包含[关键结构元素]。这样可以吗，还是您有其他想法？"

等待用户确认。

加载

references/content-types-overview.md

查看涵盖所有23种内容类型的决策表。然后从

references/content-types/<type>.md

加载对应模板（例如

references/content-types/how-to.md

），获取H1/H2结构、Schema、精选摘要格式、CTA位置、字数目标。已打包的19种完整模板内容类型：操作指南、定义、对比、清单、核心页面、FAQ页面、着陆页、服务页、案例研究、统计页面、新闻文章、术语表页面、替代方案页面、购买指南、产品页面、分类页面、集成页面、位置页面、程序化页面。仅在概览表中涵盖的4种类型（思想领导力、产品评测、定价页面、关于页面）位于

eeat-audit/references/content-types/

下，因为E-E-A-T标准是这些内容的核心考量因素。

Phase 3: Knowledge Extraction

阶段3：知识提取

Ask 2-3 quick questions to extract unique knowledge the user has. Pick from:

"What do most people get wrong about [topic]?"
"Can you give me a specific example — a client, a project, a number?"
"What surprised you when you actually did this?"
"Who should NOT follow this advice, and why?"

Ask one at a time. Keep it quick.

Adapt style:

Newer/smaller site, less SEO-savvy user: conversational, explain why each question matters
Established site, experienced user: fast, direct, no hand-holding

提出2-3个简短问题以提取用户独有的知识。可从以下问题中选择：

"大多数人对[主题]存在哪些误解？"
"您能否提供一个具体示例——客户案例、项目数据、相关数字？"
"您实际操作时遇到过哪些意外情况？"
"哪些人群不应遵循此建议，原因是什么？"

一次只问一个问题，保持简洁。

调整风格：

新网站/小型网站、SEO经验不足的用户：采用对话式，解释每个问题的重要性
成熟网站、经验丰富的用户：直接高效，无需过多引导

Phase 4: Write the Article

阶段4：撰写文章

Length: Do not target a specific word count. Match the depth of top-ranking content from Phase 1. Length follows intent and competition — never pad to hit a number.

Produce the complete article in clean markdown. Follow ALL of these rules:

篇幅：不要设定具体字数目标。匹配阶段1中排名靠前内容的深度。篇幅由用户意图和竞争情况决定——绝不要为凑字数而注水。

用清晰的Markdown格式生成完整文章。严格遵循以下所有规则：

Voice and Stance

语气与立场

Write like a practitioner talking to a peer. Not a textbook, not a press release.
Take clear positions. "We tested this and X works better than Y" beats "both X and Y have merits."
Use "you" and "I/we" — write to one person, not an audience.
Include specific numbers, names, dates. Never "many companies" — always "[Company] in [year]."
Weave in interview answers as first-person experience. Preserve phrasing where it sounds natural.
Use contractions: "doesn't" not "does not."
Show thinking changing: "At first I thought this was a branding problem — turns out it was pricing all along." Self-correction is a human signal.
Anchor in real context — reference current events, industry shifts, or cultural touchstones where relevant.

以从业者和同行交流的口吻写作，不要像教科书或新闻稿。
明确表明立场。"我们测试后发现X比Y更有效"优于"X和Y各有优势"。
使用"你"和"我/我们"——面向单个读者写作，而非泛泛的受众。
包含具体数字、名称、日期。绝不要用"许多公司"——要具体到"[公司名称]在[年份]"。
将访谈答案作为第一人称经验融入内容。在自然的情况下保留原表述。
使用缩写形式：用"doesn't"而非"does not"。
体现思维变化："起初我以为这是品牌问题——后来发现其实是定价问题。"自我修正属于人类特征。
结合真实背景——相关时参考当前事件、行业变化或文化热点。

Rhythm and Structure

节奏与结构

Vary sentence length dramatically. Mix 5-word punches with 30-word complexes. Never 3+ consecutive sentences of similar length.
Vary paragraph length. One-sentence paragraphs are fine. So are 6-sentence ones.
Use fragments for emphasis. Start sentences with "And" or "But" when natural.
Include parenthetical asides and brief tangents — humans do this, AI doesn't.
Shift registers. After a technical explanation, drop into a casual aside. Uniform register = AI tell.
Break the topic-sentence-support pattern. Start some paragraphs with an example, a question, or a statement that only makes sense after reading on.
Cover sections asymmetrically. Spend 500 words on the interesting part and 50 on the boring-but-necessary one.
Don't summarize at the end of sections unless genuinely complex (3+ subsections).

大幅变换句子长度。将5词短句与30词长句混合使用。绝不要出现3个及以上连续长度相似的句子。
变换段落长度。单句段落没问题，6句段落也可以。
使用片段句式强调重点。自然情况下可以用"And"或"But"开头。
加入括号内的题外话和简短支线内容——人类会这么做，AI不会。
变换语体风格。技术解释后可以转为随意的题外话。统一语体是AI的典型特征。
打破"主题句-支撑内容"的固定模式。有些段落可以从示例、问题或读完后文才理解的陈述开始。
不对称地安排各部分篇幅。有趣的部分写500字，必要但枯燥的部分写50字。
除非内容确实复杂（包含3个及以上子部分），否则不要在章节末尾进行总结。

Show, Don't Just State

具象化表达，而非单纯陈述

Don't state facts. Show them through brief scenarios. Instead of "page speed affects rankings" — "You click a search result. Three seconds pass. Still loading. You hit back. Google tracked every millisecond."
For claims backed by experience, narrate the moment: what was tried, what happened, what surprised you.

不要只陈述事实，通过简短场景展示。比如不说"页面速度影响排名"——要说"你点击一个搜索结果。三秒过去了，页面还在加载。你返回上一页。谷歌记录了每一毫秒的数据。"
对于基于经验的主张，叙述具体场景：尝试了什么，发生了什么，有哪些意外发现。

Anti-Slop Rules

反垃圾内容规则

NEVER use these words — highest-signal AI tells: delve, landscape (metaphorical), testament, leverage, utilize, robust, seamless, furthermore, moreover, additionally, pivotal, multifaceted, harness, embark, navigate (metaphorical), showcase, streamline, paramount, culminate, spearhead, commence, endeavor, vibrant, innovative, comprehensive (as adjective).

NEVER use these phrases: "It's worth noting", "In today's [anything]", "Let's dive in", "In conclusion", "plays a crucial/vital/pivotal role", "It goes without saying", "In the realm of".

Avoid these structural patterns:

Rule-of-three groupings (use 2 or 4 items instead)
Synonym cycling (repeat the right word rather than finding alternatives)
Copula avoidance ("serves as" — just say "is")
Em-dash chains (max 1-2 per 1000 words)
Binary contrasts ("it's not X, it's Y" — just make the argument)
Participial tack-ons ("...highlighting the importance of X" — delete or make a separate sentence)
Clustering of: however, notably, essentially, that said, arguably — fine individually, but 3+ in one article flags AI

绝对禁止使用以下单词——AI内容的最高信号特征： delve, landscape（比喻义）, testament, leverage, utilize, robust, seamless, furthermore, moreover, additionally, pivotal, multifaceted, harness, embark, navigate（比喻义）, showcase, streamline, paramount, culminate, spearhead, commence, endeavor, vibrant, innovative, comprehensive（作形容词时）。

绝对禁止使用以下短语： "It's worth noting", "In today's [anything]", "Let's dive in", "In conclusion", "plays a crucial/vital/pivotal role", "It goes without saying", "In the realm of"。

避免以下结构模式：

三分法分组（改用2个或4个条目）
同义词替换循环（重复正确单词，而非寻找替代词）
避免系动词（用"is"代替"serves as"）
破折号连用（每1000字最多1-2个）
二元对比（"不是X，而是Y"——直接论证即可）
分词附加结构（"...highlighting the importance of X"——删除或改为单独句子）
过度使用：however, notably, essentially, that said, arguably——单独使用没问题，但一篇文章中出现3个及以上会被标记为AI内容

Content Type Structure

内容类型结构

How-to: 40-60 word quick answer first (featured snippet target), then numbered steps, each step = one action with "what goes wrong"
Comparison: Verdict first ("Choose A if... Choose B if..."), then detailed analysis
Listicle: Summary table above fold, consistent evaluation framework per item
Definition: "[Term] is..." in the first sentence, no preamble
Case study: Lead with the result number, then the story (PAS framework)
Pillar page: Table of contents, overview, then link to deep-dive articles
Service/landing page: PAS framework. Pain point first, agitate consequences, then solution

操作指南：先写40-60词的快速解答（目标是精选摘要），然后是编号步骤，每个步骤对应一个操作，并说明"可能出现的问题"
对比文：先给出结论（"如果...选择A；如果...选择B"），再进行详细分析
清单文：首屏展示汇总表格，每个条目使用统一的评估框架
定义文：第一句就写"[术语]是..."，不要铺垫
案例研究：开头先给出结果数据，然后讲述故事（PAS框架）
核心页面：包含目录、概述，然后链接到深度文章
服务/着陆页：采用PAS框架。先提出痛点，放大后果，再给出解决方案

SEO Structure

SEO结构

Primary keyword in meta title, H1, first 100 words, 2-3 H2s. ~2% body density, naturally distributed.
Place a 40-60 word direct answer immediately after the most important H2 — targets featured snippets. "How" queries get ordered lists, "what is" gets paragraphs, comparisons get tables.
Weave 2-3 PAA questions into the article as H2/H3 headings with direct answers.
Include 3-5 internal links per 1,000 words. Use descriptive anchor text — never "click here."
Front-load value. The first screen is the highest-value real estate. No preamble paragraphs.

核心关键词出现在元标题、H1、前100词、2-3个H2中。正文中自然分布，密度约2%。
在最重要的H2后立即放置40-60词的直接解答——目标是精选摘要。"How"类查询用有序列表，"what is"类用段落，对比文用表格。
将2-3个PAA问题作为H2/H3标题融入文章，并给出直接解答。
每1000字包含3-5个内部链接。使用描述性锚文本——绝不要用"点击这里"。
前置核心价值。首屏是最有价值的位置，不要写铺垫段落。

Long Article Strategy (1,500+ words)

长文策略（1500词以上）

Write section by section. Track what you've covered to prevent repetition and voice drift.
At least 30% of the article must contain details no generic AI could produce: the user's data, examples, opinions, experience.

分章节撰写。记录已覆盖内容，避免重复和语气偏差。
至少30%的内容必须包含通用AI无法生成的细节：用户的数据、示例、观点、经验。

Final Checks

最终检查

"So What?" test: For each major section — could anyone have written this, for anyone, about anything? If yes, inject specific knowledge.
Self-check: Scan for blacklisted words, sections where every paragraph starts with a topic sentence, unnecessary section summaries, participial tack-ons. Fix before delivering.

"那又怎样？"测试：对于每个主要章节——是否任何人都能为任何受众撰写任何主题的此类内容？如果是，注入专属知识。
自我检查：扫描是否有黑名单词汇、所有段落都以主题句开头的章节、不必要的章节总结、分词附加结构。交付前修正这些问题。

Output

输出

Clean markdown. Title + article content. Nothing else.

清晰的Markdown格式。仅包含标题+文章内容，无其他内容。

Language

语言

Write in the language from the business context. If not specified, match the language of the user's messages.

使用业务上下文中指定的语言。若未指定，匹配用户消息的语言。

Bundled references

打包参考资料

Load from

references/

only when the step or rule calls for them. Don't preload — each file is heavy enough to blow context if stacked.

Content type templates (

references/content-types/

) — load one after Phase 2:

Common:

how-to.md

definition.md

comparison.md

listicle.md

pillar-page.md

faq-page.md

landing-page.md

service-page.md

case-study.md

Content and news:

statistics-page.md

news-article.md

glossary-page.md

Commercial:

alternatives-page.md

buying-guide.md

product-page.md

category-page.md

integration-page.md

location-page.md

programmatic-page.md

```
references/content-types-overview.md
```
for the decision table across all 23 content types (load this FIRST if unsure which type to pick)

Writing technique modules (

references/

) — load when the matching Phase 4 rule needs more depth:

```
anti-slop-ruleset.md
```
— full tiered banned vocab + structural tell list (when the inline anti-slop block isn't catching something)
```
voice-injection-playbook.md
```
— voice and register techniques (when the draft reads flat)
```
information-gain-writing.md
```
— the 30% rule and how to satisfy it (for the "So What" test)
```
serp-driven-writing.md
```
— how Phase 1 research shapes the article (if the draft drifts from the SERP intent)
```
intent-matching.md
```
— length and format decisions from intent (when the SERP is mixed)
```
eeat-signal-embedding.md
```
— how to surface experience without a bio section
```
structured-data-snippets.md
```
— JSON-LD and featured snippet formatting per content type
```
geo-optimization.md
```
— optimizing for AI Overview / generative engine citation
```
navboost-engagement.md
```
— engagement signal writing (dwell time, scroll depth)
```
quality-scoring.md
```
— self-scoring rubric to run before delivery
```
writing-pipeline.md
```
— the research → draft → edit loop
```
seo-optimization-layer.md
```
— keyword placement, internal linking, metadata pass
```
fact-checking.md
```
— how to verify every specific number and claim
```
human-input-framework.md
```
— the knowledge-extraction questions (reinforces Phase 3)

仅在步骤或规则要求时从

references/

加载。不要预加载——每个文件内容较多，叠加会超出上下文限制。

内容类型模板（

references/content-types/

）——阶段2后加载一个：

常见类型：

how-to.md

definition.md

comparison.md

listicle.md

pillar-page.md

faq-page.md

landing-page.md

service-page.md

case-study.md

内容与新闻类：

statistics-page.md

news-article.md

glossary-page.md

商业类：

alternatives-page.md

buying-guide.md

product-page.md

category-page.md

integration-page.md

location-page.md

programmatic-page.md

```
references/content-types-overview.md
```
包含所有23种内容类型的决策表（若不确定选择哪种类型，先加载此文件）

写作技巧模块（

references/

）——当阶段4的对应规则需要更深入内容时加载：

```
anti-slop-ruleset.md
```
——完整的分级禁用词汇+结构特征列表（当内置反垃圾内容规则未覆盖时使用）
```
voice-injection-playbook.md
```
——语气与语体技巧（当草稿读起来平淡时使用）
```
information-gain-writing.md
```
——30%规则及实现方法（用于"那又怎样？"测试）
```
serp-driven-writing.md
```
——阶段1调研如何影响文章（当草稿偏离SERP意图时使用）
```
intent-matching.md
```
——基于意图的篇幅与格式决策（当SERP内容混合时使用）
```
eeat-signal-embedding.md
```
——无需个人简介即可体现专业经验的方法
```
structured-data-snippets.md
```
——各内容类型的JSON-LD与精选摘要格式
```
geo-optimization.md
```
——针对AI概览/生成引擎引用的优化
```
navboost-engagement.md
```
——提升参与度信号的写作技巧（停留时间、滚动深度）
```
quality-scoring.md
```
——交付前的自我评分标准
```
writing-pipeline.md
```
——调研→草稿→编辑流程
```
seo-optimization-layer.md
```
——关键词布局、内部链接、元数据优化
```
fact-checking.md
```
——如何验证每个具体数字和主张
```
human-input-framework.md
```
——知识提取问题（强化阶段3）