| name | technical-blog-writer |
| description | Write technical blog posts about real engineering challenges. Use when the user wants technical content, blog posts, tutorials, or explanations for mixed audiences including non-technical readers. |
| license | MIT |
| compatibility | claude-code opencode github-copilot devin pi cursor |
Technical Blog Writer
Write expert-level technical posts that are accessible to non-developers.
Process
- Research: find current, authoritative sources and real-world examples.
- Outline: structure the article around a clear problem-solution flow.
- Draft: follow this structure:
- The problem
- Why it matters
- The solution
- How it works
- Tradeoffs and considerations
- Key takeaways
- FAQs (3-5 questions)
- Refine: check clarity, accuracy, flow, and examples.
Writing rules
- Use plain English. Explain jargon when first introduced.
- Include code only when it clarifies.
- Use active voice and short paragraphs.
- Vary sentence rhythm.
- Include concrete examples, not generic claims.
- Write from experience using "we" and "our" naturally.
- Acknowledge limitations and tradeoffs.
Anti-patterns
- Repetitive "we've" constructions
- Perfect formulaic transitions
- Overly technical explanations without context
- Generic content without examples
Quality checklist
