content-writing

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Content Writing Skill

内容写作技能

Use When

使用场景

Copywriting and content creation standards for website pages, blog posts, and all written copy. Covers headlines, ledes, readability, niche vocabulary, scannable formatting, and persuasive structure. Cross-cutting skill — apply whenever...
The task needs reusable judgment, domain constraints, or a proven workflow rather than ad hoc advice.

网页、博客文章及所有书面文案的文案撰写与内容创作标准。涵盖标题、导语、可读性、细分领域词汇、可快速浏览的格式以及有说服力的结构。这是一项跨领域技能——无论何时……
任务需要可复用的判断逻辑、领域约束或成熟的工作流程，而非临时建议。

Do Not Use When

禁止使用场景

The task is unrelated to
```
content-writing
```
or would be better handled by a more specific companion skill.
The request only needs a trivial answer and none of this skill's constraints or references materially help.

任务与
```
content-writing
```
无关，或更适合由更细分的配套技能处理。
请求仅需要简单答案，且本技能的约束条件或参考资料无法提供实质性帮助。

Required Inputs

必要输入

Gather relevant project context, constraints, and the concrete problem to solve; load
```
references
```
only as needed.
Confirm the desired deliverable: design, code, review, migration plan, audit, or documentation.

收集相关项目背景、约束条件以及具体需要解决的问题；仅在需要时加载
```
references
```
内容。
确认期望的交付成果：设计、代码、评审、迁移计划、审计或文档。

Workflow

工作流程

Read this
```
SKILL.md
```
first, then load only the referenced deep-dive files that are necessary for the task.
Apply the ordered guidance, checklists, and decision rules in this skill instead of cherry-picking isolated snippets.
Produce the deliverable with assumptions, risks, and follow-up work made explicit when they matter.

首先阅读本
```
SKILL.md
```
，然后仅加载完成任务所需的相关深度参考文件。
应用本技能中按顺序排列的指导方针、检查清单和决策规则，而非随意挑选孤立片段。
交付成果中需明确说明重要的假设条件、风险以及后续工作。

Quality Standards

质量标准

Keep outputs execution-oriented, concise, and aligned with the repository's baseline engineering standards.
Preserve compatibility with existing project conventions unless the skill explicitly requires a stronger standard.
Prefer deterministic, reviewable steps over vague advice or tool-specific magic.

输出内容需以执行为导向、简洁明了，并与仓库的基础工程标准保持一致。
除非技能明确要求更高标准，否则需遵循现有项目惯例。
优先采用可确定、可评审的步骤，而非模糊建议或依赖特定工具的“魔法操作”。

Anti-Patterns

反模式

Treating examples as copy-paste truth without checking fit, constraints, or failure modes.
Loading every reference file by default instead of using progressive disclosure.

将示例视为可直接复制粘贴的标准，而不检查是否适配、是否符合约束条件或存在失效模式。
默认加载所有参考文件，而非逐步按需披露。

Outputs

输出成果

A concrete result that fits the task: implementation guidance, review findings, architecture decisions, templates, or generated artifacts.
Clear assumptions, tradeoffs, or unresolved gaps when the task cannot be completed from available context alone.
References used, companion skills, or follow-up actions when they materially improve execution.

符合任务要求的具体结果：实施指导、评审结论、架构决策、模板或生成的工件。
当仅靠现有上下文无法完成任务时，需明确说明假设条件、权衡取舍或未解决的缺口。
当参考资料、配套技能或后续行动对执行有实质性帮助时，需列出相关内容。

Evidence Produced

生成的证据

Category	Artifact	Format	Example
UX quality	Page copy review	Markdown doc covering headline, lede, body, and CTA per page against the content-writing standard	`docs/content/page-copy-review-checkout.md`

类别	工件	格式	示例
UX质量	页面文案评审	按照内容写作标准涵盖页面标题、导语、正文和CTA的Markdown文档	`docs/content/page-copy-review-checkout.md`

References

参考资料

Use the
```
references/
```
directory for deep detail after reading the core workflow below.

Professional copywriting standards for website copy, blog posts, articles, and all written content. This is a cross-cutting skill — apply these principles whenever creating or editing text for any page.

阅读以下核心工作流程后，如需详细内容可查看
```
references/
```
目录。

适用于网页文案、博客文章、专栏及所有书面内容的专业文案撰写标准。这是一项跨领域技能——无论何时创建或编辑任何页面的文本，都应遵循这些原则。

The Reader-First Rule

读者优先原则

Every word exists for the reader, not the writer. Before writing anything, answer:

Who is the reader? What do they already know?
What are they looking for? What problem brought them here?
Why should they care? What benefit do they gain?

Write for the reader all the time. That is what separates content that converts from content that gets ignored.

每个词汇都是为读者而非作者服务的。在写作前，先回答以下问题：

谁是读者？他们已经了解哪些信息？
他们在寻找什么？是什么问题促使他们来到这里？
他们为何要关注？能获得什么益处？

始终为读者写作。这正是有转化力的内容与被忽略的内容之间的区别。

Headlines & Titles

标题与副标题

The headline is the most important element. Five times as many people read the headline as read the body. If the headline fails, everything below it is wasted.

标题是最重要的元素。阅读标题的人数是阅读正文的五倍。如果标题失效，下面的所有内容都将白费。

Headline Rules

标题规则

Promise a benefit. Headlines that promise benefits outperform those that don't.
Give news. Readers seek new information — new products, new methods, new insights.
Select your reader. Flag down the people you want. If writing for banana farmers, put "banana farmers" in the headline.
Be specific. "How to Increase Banana Yield by 40%" beats "Tips for Better Farming."
Long headlines that say something outpull short headlines that say nothing. Never sacrifice clarity for brevity.
Write the headline AFTER the content. Only then do you know the full scope and best angle.
Telegraph in simple language. Readers do not stop to decipher obscure headlines.

承诺益处：承诺益处的标题效果优于未承诺的。
传递资讯：读者寻求新信息——新产品、新方法、新见解。
定位目标读者：明确吸引你想要的人群。如果是为香蕉种植者写作，就在标题中加入“香蕉种植者”。
具体明确：“如何将香蕉产量提高40%”比“更好的种植技巧”效果更好。
有实质内容的长标题优于空洞的短标题：切勿为了简洁而牺牲清晰度。
写完内容后再写标题：只有这时你才了解内容的完整范围和最佳角度。
用简单直白的语言传达信息：读者不会停下来解读晦涩的标题。

Headline Formulas That Work

有效的标题公式

How to [achieve desired result]: "How to Store Bananas for Maximum Shelf Life"
[Number] Ways/Reasons/Steps: "7 Steps to Higher-Quality Matooke Flour"
Question that mirrors the reader's problem: "Is Your Banana Crop Vulnerable to Fusarium Wilt?"
News/announcement: "New Banana Cultivar Resists Black Sigatoka Disease"
Direct benefit: "Reduce Post-Harvest Losses by Half with These Storage Methods"

如何[实现期望结果]：“如何储存香蕉以延长保质期”
[数字]种方法/理由/步骤：“提升马托基面粉品质的7个步骤”
反映读者问题的问句：“你的香蕉作物易受枯萎病侵害吗？”
资讯/公告：“新型香蕉品种可抗黑条叶斑病”
直接益处：“采用这些储存方法将收获后损失减少一半”

What to Avoid in Headlines

标题避坑指南

Clever wordplay the reader won't get
Headlines that could apply to any topic (too generic)
ALL CAPS for entire headlines (harder to read)
Clickbait that the content cannot deliver on

读者无法理解的巧妙文字游戏
适用于任何主题的通用标题（过于宽泛）
全部大写的标题（更难阅读）
内容无法兑现的标题党

Additional Guidance

额外指导

Extended guidance for

content-writing

was moved to references/skill-deep-dive.md to keep this entrypoint compact and fast to load.

Use that deep dive for:

```
The Lede (Opening)
```
```
Readability
```
```
Niche Vocabulary (Thematic Depth)
```
```
Scannable Formatting
```
```
The "So What?" Test
```
```
Attribution as Authority
```
```
Unique Value Proposition
```
```
Features vs Benefits
```
```
Structure Templates
```
```
Keeping Eyes Moving
```
```
Writing Styles
```
```
Takeaways
```
Additional deep-dive sections continue in the reference file.

content-writing

的扩展指导已移至references/skill-deep-dive.md，以保持本入口简洁易读、加载快速。

如需以下内容，请查看该深度参考文件：

```
导语（开头部分）
```
```
可读性
```
```
细分领域词汇（主题深度）
```
```
可快速浏览的格式
```
```
"那又如何？"测试
```
```
以权威性为依托的署名
```
```
独特价值主张
```
```
功能 vs 益处
```
```
结构模板
```
```
保持读者注意力
```
```
写作风格
```
```
要点总结
```
更多深度内容请查看参考文件。",