blog-writer

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Developer Blog Writer

开发者博客撰写指南

Transform unstructured thoughts into polished technical blog posts.

将非结构化的想法转化为打磨精良的技术博客文章。

Reference Files

参考文件

Load these before writing:

File	Purpose
`references/voice-tone.md`	Writing voice and style guide
`references/story-circle.md`	Narrative framework for posts
`references/post-templates.md`	Starter structures by post type
`references/seo-checklist.md`	Pre-publish SEO checks

撰写前请加载以下文件：

文件	用途
`references/voice-tone.md`	写作语气与风格指南
`references/story-circle.md`	文章叙事框架
`references/post-templates.md`	按文章类型划分的起始结构模板
`references/seo-checklist.md`	发布前SEO检查清单

Process

流程

1. Receive the Brain Dump

1. 接收原始想法收集内容

Accept whatever is provided:

Scattered thoughts and ideas
Technical points to cover
Code snippets or commands
Conclusions or takeaways

Don't require organization. The mess is the input.

接收任何形式的输入：

零散的想法与观点
需要涵盖的技术要点
代码片段或命令
结论或关键收获

无需要求内容有条理，杂乱的内容正是输入素材。

2. Load Voice Guide

2. 加载写作风格指南

Read

references/voice-tone.md

for writing style:

Professional-casual tone
First-person, inclusive language ("we", "us")
Show the journey, not just the destination

阅读

references/voice-tone.md

以明确写作风格：

专业且随意的语气
使用第一人称包容性语言（“我们”、“咱们”）
展示探索过程，而非仅呈现最终结果

3. Identify Post Type

3. 确定文章类型

Type	Use When
Tutorial	Step-by-step instructions
Project Showcase	Sharing what you built
Opinion	Your take on a topic
TIL	Quick, focused insight
Comparison	X vs Y analysis

类型	适用场景
教程	分步式操作说明
项目展示	分享你所构建的项目
观点文	表达你对某一主题的看法
TIL（今日所学）	简短、聚焦的见解分享
对比文	X与Y的分析对比

4. Check for Story Potential

4. 挖掘叙事潜力

Read

references/story-circle.md

and look for:

Journey from confusion to clarity
Problem you solved
Something learned the hard way
Perspective shift

阅读

references/story-circle.md

，寻找以下元素：

从困惑到清晰的探索历程
你解决的问题
从失败中获得的经验
视角的转变

5. Organize & Write

5. 组织内容并撰写

Opening: Hook with problem, question, or motivation. No "In this post, I will..."

Body:

Vary paragraph length
Include specific details
Show actual code
Be honest about what didn't work

Ending:

Tie back to opening
Actionable takeaway
Forward-looking ("Stay tuned for...")

开头： 以问题、疑问或动机作为钩子。不要使用“在本文中，我将……”这类表述。

正文：

变换段落长度
包含具体细节
展示实际代码
坦诚分享未成功的尝试

结尾：

呼应开头内容
提供可落地的关键收获
展望未来（例如：“敬请期待后续……”）

6. Review & Optimize

6. 审核与优化

Voice check:

Does it sound like a developer talking to peers?
Is there a clear thread from start to finish?

SEO check (from

references/seo-checklist.md

Primary keyword in title and first paragraph
Meta description (150-160 chars)
URL slug is short and clean
2-3 internal/external links
Code blocks specify language

语气检查：

语气是否像开发者与同行交流？
文章是否有清晰的逻辑主线贯穿始终？

SEO检查（参考

references/seo-checklist.md

）：

标题和首段包含核心关键词
元描述（150-160字符）
URL短且简洁
2-3个内部/外部链接
代码块指定编程语言

Quick Voice Reference

快速风格参考

Do:

建议：

Write like explaining to a smart colleague
Admit uncertainty or mistakes
Use specific examples with real details
Show what you tried, not just what worked

像向聪明的同事讲解一样写作
承认不确定性或错误
使用带有真实细节的具体示例
展示你尝试过的方法，而非仅分享成功方案

Don't:

禁忌：

Use corporate or marketing speak
Over-explain basic concepts
Start with "In this post..." or "As we all know..."
Force humor or excessive emojis

使用企业或营销话术
过度解释基础概念
以“在本文中……”或“众所周知……”开头
强行加入幽默或过多表情符号