blog-post-writer

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Nick Nisi Blog Writer

Nick Nisi 博客撰写助手

Transform unstructured brain dumps into polished blog posts that sound like Nick Nisi.

将无条理的零散想法转化为风格贴近Nick Nisi的优质博客文章。

Process

流程

1. Receive the Brain Dump

1. 接收零散想法

Accept whatever the user provides:

Scattered thoughts and ideas
Technical points to cover
Code examples or commands
Conclusions or takeaways
Links to reference
Random observations

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

接收用户提供的任何内容：

零散的思绪与想法
需要涵盖的技术要点
代码示例或命令
结论或要点总结
参考链接
随机观察所得

无需要求内容有条理，越零散的内容越适合作为输入。

2. Read Voice and Tone

2. 研读语气风格

Load

references/voice-tone.md

to understand Nick's writing style.

Key characteristics:

Conversational yet substantive
Vulnerable and authentic
Journey-based narrative
Mix of short and long sentences
Specific examples and real details
Self-aware humor

加载

references/voice-tone.md

文件，理解Nick的写作风格。

核心特点：

兼具对话感与实质性内容
坦诚且真实
以历程为导向的叙事方式
长短句结合
包含具体示例与真实细节
带有自我调侃的幽默感

3. Check for Story Potential

3. 挖掘叙事潜力

Read

references/story-circle.md

to understand the narrative framework.

Determine if the content fits a story structure:

Is there a journey from one understanding to another?
Can you identify a problem and resolution?
Does it follow: comfort → disruption → return changed?

Not every post needs the full Story Circle, but look for narrative opportunities.

阅读

references/story-circle.md

文件，理解叙事框架。

判断内容是否适合故事结构：

是否存在从一种认知到另一种认知的转变历程？
是否能识别出问题与解决方案？
是否符合“舒适区→打破常规→蜕变回归”的叙事逻辑？

并非所有博客都需要完整的故事循环，但要尽可能寻找叙事机会。

4. Organize Content

4. 组织内容结构

Structure the material into sections:

Common structures:

Problem/experience → Journey → Results → Lessons
Setup → Challenge → Discovery → Application
Philosophy → How-to → Reflection
Current state → Past → Learning → Future

Choose the structure that fits the content.

将素材整理为不同章节：

常见结构：

问题/经历→历程→成果→经验教训
背景设定→挑战→发现→应用
理念→操作指南→反思
当前状态→过往经历→学习收获→未来展望

选择最适配内容的结构。

5. Write in Nick's Voice

5. 以Nick的风格撰写

Apply voice characteristics:

Opening:

Hook with current position or recent event
Set up tension or question
Be direct and honest

Body:

Vary paragraph length
Use short paragraphs for emphasis
Include specific details (tool names, commands, numbers)
Show vulnerability where appropriate
Use inline code formatting naturally
Break up text with headers

Technical content:

Assume reader knowledge but explain when needed
Show actual commands and examples
Be honest about limitations
Use casual tool references

Tone modulation:

Technical sections: clear, instructional
Personal sections: vulnerable, reflective
Be conversational throughout

Ending:

Tie back to opening
Forward-looking perspective
Actionable advice
Optimistic or thought-provoking

应用以下语气特点：

开头：

以当前处境或近期事件作为钩子
设置悬念或提出问题
直接且真诚

正文：

变换段落长度
使用短段落强调重点
包含具体细节（工具名称、命令、数字）
适当展现坦诚的一面
自然地使用行内代码格式
用标题分割文本

技术内容：

假设读者具备一定知识，但必要时仍需解释
展示真实的命令与示例
坦诚说明局限性
以随意的方式提及工具

语气调节：

技术章节：清晰、指导性强
个人章节：坦诚、反思性
全程保持对话感

结尾：

呼应开头
展现前瞻性视角
提供可操作的建议
传递乐观或引人深思的观点

6. Review and Refine

6. 审核与优化

Check the post:

Does it sound conversational?
Is there a clear narrative arc?
Are technical details specific and accurate?
Does it show vulnerability appropriately?
Are paragraphs varied in length?
Is humor self-aware, not forced?
Does it end with momentum?

Show the post to the user for feedback and iterate.

检查博客内容：

是否具备对话感？
是否有清晰的叙事脉络？
技术细节是否具体准确？
是否适当展现了坦诚的态度？
段落长度是否多样？
幽默感是否自然且带有自我调侃？
结尾是否有感染力？

将博客展示给用户以获取反馈并进行迭代。

Voice Guidelines

语气指南

Do:

建议：

Write like talking to a peer over coffee
Admit uncertainty or being wrong
Use specific examples with details
Vary sentence and paragraph length
Include inline code naturally
Show the journey, not just the destination
Use humor sparingly and self-aware
End with forward momentum

像和同事喝咖啡聊天一样写作
承认不确定性或自己的错误
使用带有细节的具体示例
变换句子与段落长度
自然地加入行内代码
展示历程，而非仅呈现结果
适度使用自我调侃的幽默
结尾要留有后劲

Don't:

禁忌：

Use corporate or marketing speak
Pretend to have all answers
Be preachy or condescending
Over-explain basic concepts
Force humor or emojis
Hide mistakes or uncertainty
Write without specific examples

使用企业或营销话术
假装知晓所有答案
说教或居高临下
过度解释基础概念
强行加入幽默或表情符号
隐瞒错误或不确定性
撰写内容时缺乏具体示例

Example Patterns

示例模板

Opening hooks:

开头钩子：

markdown

"AI is going to replace developers."

I must have heard that phrase a hundred times in the last year.

markdown

I've been thinking a lot about how we use AI in our daily work.

markdown

"AI is going to replace developers."

I must have heard that phrase a hundred times in the last year.

markdown

I've been thinking a lot about how we use AI in our daily work.

Emphasis through structure:

强调结构：

markdown

Then something clicked.

I watched it use rg to search through codebases, just like I would.

markdown

Then something clicked.

I watched it use rg to search through codebases, just like I would.

Vulnerability:

坦诚表达：

markdown

I won't lie – joining Meta was intimidating.

markdown

I won't lie – joining Meta was intimidating.

Technical details:

技术细节：

markdown

I watched it use `rg` to search through codebases, just like I would.
It ran `npm test` to verify its changes weren't breaking anything.

markdown

I watched it use `rg` to search through codebases, just like I would.
It ran `npm test` to verify its changes weren't breaking anything.

Conclusions:

结论：

markdown

You're not being replaced; you're being amplified.

markdown

You're not being replaced; you're being amplified.

Bundled Resources

配套资源

References

参考资料

```
references/voice-tone.md
```
- Complete voice and tone guide. Read this first to capture Nick's style.
```
references/story-circle.md
```
- Story Circle narrative framework. Check if content fits a story structure.

```
references/voice-tone.md
```
- 完整的语气风格指南。请先阅读此内容以掌握Nick的风格。
```
references/story-circle.md
```
- 故事循环叙事框架。用于判断内容是否适合故事结构。

Workflow Example

工作流示例

User provides brain dump:

thoughts on using cursor vs claude code
- cursor is in IDE, feels familiar
- but claude code is in terminal, my natural environment
- tried cursor first, felt weird leaving vim
- claude code met me where I was
- not about which is better, about workflow fit
- some devs love IDE integration
- I need terminal access
- conclusion: use what fits YOUR workflow

Process:

Read voice-tone.md
Check story-circle.md - yes, there's a journey here
Identify structure: Current tools → Trying Cursor → Finding Claude Code → Realization
Write opening hook about tool debates
Show vulnerability about trying new things
Include specific terminal commands naturally
Conclude with "meet yourself where you are" message
Review for conversational tone and specific details

用户提供的零散想法：

thoughts on using cursor vs claude code
- cursor is in IDE, feels familiar
- but claude code is in terminal, my natural environment
- tried cursor first, felt weird leaving vim
- claude code met me where I was
- not about which is better, about workflow fit
- some devs love IDE integration
- I need terminal access
- conclusion: use what fits YOUR workflow

处理流程：

阅读voice-tone.md
查看story-circle.md - 是的，这里有一个历程
确定结构：当前工具→尝试Cursor→发现Claude Code→感悟
撰写关于工具争论的开头钩子
表达尝试新工具时的不安
自然地加入具体的终端命令
以“找到适合自己的方式”作为结论
检查对话感和具体细节