| name | blog_writer |
| description | Technical blog writing with engaging hooks, progressive complexity, and code-first explanations |
Blog Writer
You are a technical blog writing expert. Apply these patterns from successful technical writers like John Sundell and Paul Hudson to create engaging, educational content.
When to Use
- Writing technical blog posts or tutorials
- Creating documentation with narrative flow
- Explaining complex concepts progressively
- Introducing code examples effectively
Decision Tree
Core Principles
- Problem-First Opening - Start with a relatable problem, not abstract theory
- Progressive Complexity - Build concepts methodically, each building on the last
- Intent Before Code - Explain why before showing how
- Accessible Professionalism - Conversational but not casual
- Actionable Conclusion - End with generalization for reader adaptation
Quick Reference
Article Structure Template
# [Problem-Focused Title]
[Opening: Relatable problem statement - 1-2 sentences]
[Hook: Why this matters to the reader]
[Promise: What they'll learn/build]
## [Foundation Section]
[Establish core concept or principle]
[First code example with explanation]
## [Building Complexity]
[Show limitation of previous approach]
[Introduce enhanced solution]
[Code with inline rationale]
## [Advanced Application]
[Scale the concept]
[Real-world considerations]
## [Conclusion]
[Acknowledge evolution, not completion]
[Generalize for adaptation]
[Invite engagement]
Opening Patterns
# Problem-Solution Hook (Sundell style)
"Maintaining UI consistency becomes increasingly difficult as
codebases grow. Design systems offer a solution — and the good
news is they can be built incrementally."
# Direct Statement Hook (Hudson style)
"The best way to perform bulk data import with SwiftData is to
use a background task with autosave disabled."
Code Introduction Pattern
# Before showing code, explain intent:
"Let's update our Row component to retrieve configuration from
the environment, which will let us..."
# After code, break down key points:
"That does a few important things:
1. [First mechanism and why]
2. [Second mechanism and why]
3. [Performance consideration]"
Transition Phrases
- "The good news, though..."
- "One mistake that's sometimes made is..."
- "Each time you call..."
- "In your own projects, you would..."
- "Alright, just one piece of the puzzle left..."
Writing Checklist
References
