Back to Details

content-writing

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<!-- Adapted from: awesome-claude-skills/content-research-writer -->
<!-- 改编自: awesome-claude-skills/content-research-writer -->

Content Research & Writing Guide

内容研究与写作指南

Collaborative writing partner for articles, blog posts, and documentation.
协作式写作伙伴，适用于文章、博客文章和文档撰写。

Workflow Overview

工作流程概述

  1. Outline - Structure ideas collaboratively
  2. Research - Find sources and add citations
  3. Write - Draft section by section
  4. Feedback - Get review on each section
  5. Polish - Final review and refinement
  1. 大纲制定 - 协作构建内容结构
  2. 研究调研 - 查找资料并添加引用
  3. 内容撰写 - 分章节起草
  4. 反馈收集 - 获取各章节的评审意见
  5. 润色完善 - 最终评审与优化

File Organization

文件组织结构

~/writing/article-name/
├── outline.md          # Structure
├── research.md         # Sources and citations
├── draft-v1.md         # First draft
├── draft-v2.md         # Revised
├── final.md            # Publication-ready
└── sources/            # Reference materials
~/writing/article-name/
├── outline.md          # 结构大纲
├── research.md         # 资料与引用
├── draft-v1.md         # 第一版草稿
├── draft-v2.md         # 修订版草稿
├── final.md            # 可发布终稿
└── sources/            # 参考资料文件夹

Outline Template

大纲模板

markdown
undefined
markdown
undefined

Article Outline: [Title]

文章大纲: [标题]

Hook

开篇钩子

  • Opening line/story/statistic
  • Why reader should care
  • 开篇语句/故事/统计数据
  • 说明读者为何需要关注

Introduction

引言

  • Context and background
  • Problem statement
  • What this article covers
  • 背景与上下文
  • 问题陈述
  • 本文涵盖内容

Main Sections

主体章节

Section 1: [Title]

章节1: [标题]

  • Key point A
  • Key point B
  • [Research needed: topic]
  • 核心要点A
  • 核心要点B
  • [待研究: 主题]

Section 2: [Title]

章节2: [标题]

  • Key point C
  • Evidence/data needed
  • 核心要点C
  • 需补充的证据/数据

Conclusion

结论

  • Summary
  • Call to action
  • Final thought
  • 内容总结
  • 行动号召
  • 最终思考

Research To-Do

待研究事项

  • Find data on [topic]
  • Source for [claim]
undefined
  • 查找[主题]相关数据
  • 为[观点]寻找资料来源
undefined

Hook Improvement

开篇钩子优化

When reviewing introductions, consider:
  • Does it create curiosity?
  • Does it promise value?
  • Is it specific enough?
  • Does it match the audience?
评审引言部分时，可从以下维度考量：
  • 是否能引发好奇心？
  • 是否传递了价值承诺？
  • 是否足够具体？
  • 是否匹配目标受众？

Hook Types

开篇钩子类型

TypeExample
Bold statement"Product management will never be the same."
Question"What if you could talk to every customer before coffee?"
Story"Sarah spent two weeks building the wrong feature..."
Data"Last month, AI analyzed 500 interviews in 30 minutes."
类型示例
大胆断言"产品管理行业将彻底改变。"
提问式"要是你能在喝咖啡前就和所有客户沟通，会怎么样？"
故事式"萨拉花了两周时间开发了一个完全错误的功能……"
数据式"上个月，AI在30分钟内完成了500份访谈的分析。"

Section Feedback Format

章节反馈格式

markdown
undefined
markdown
undefined

Feedback: [Section Name]

反馈: [章节名称]

What Works Well ✓

亮点 ✓

  • [Strength 1]
  • [Strength 2]
  • [优点1]
  • [优点2]

Suggestions

建议

Clarity

清晰度

  • [Issue] → [Fix]
  • [问题] → [修正方案]

Flow

流畅度

  • [Transition issue] → [Better connection]
  • [过渡问题] → [优化衔接方式]

Evidence

证据支撑

  • [Claim needing support] → [Add citation]
  • [需要支撑的观点] → [添加引用]

Specific Line Edits

具体语句修改

Original:
[Quote from draft]
Suggested:
[Improved version]
Why: [Explanation]
undefined
原文:
[草稿引用内容]
修改建议:
[优化后的内容]
原因: [说明理由]
undefined

Citation Formats

引用格式

Inline:
Studies show 40% improvement (McKinsey, 2024).
Numbered:
Studies show 40% improvement [1].

[1] McKinsey Global Institute. (2024)...
嵌入式引用:
研究表明效率提升了40%（麦肯锡，2024）。
编号式引用:
研究表明效率提升了40% [1]。

[1] 麦肯锡全球研究院. (2024)...

Pre-Publish Checklist

发布前检查清单

  • All claims sourced
  • Citations formatted
  • Examples clear
  • Transitions smooth
  • Call to action present
  • Proofread for typos
  • 所有观点均有资料支撑
  • 引用格式规范
  • 示例清晰易懂
  • 内容过渡流畅
  • 包含行动号召
  • 已校对拼写错误

Voice Preservation

风格保留

  • Learn writer's style from samples
  • Suggest, don't replace
  • Match tone (formal/casual/technical)
  • Ask: "Does this sound like you?"
  • 从样本中学习作者的写作风格
  • 提出建议而非直接替换
  • 匹配语气（正式/随意/技术向）
  • 询问：“这听起来像你的风格吗？”