Copy-paste the block below into any AI coding agent to turn a project, technical concept, or engineering experience into a clear, engaging blog post with real content and real insights, not fluff.
Keywords: technical blog, blog post, writing, tutorial, article, developer writing
Help me write a technical blog post about `[topic / project / experience]`.
The goal: a post that teaches something real, engages the reader, and
demonstrates technical depth without being inaccessible.
## Steps
1. **Understand the audience** - Who is this for? Adjust technical depth
accordingly: beginner (explain concepts), intermediate (assume familiarity
with basics), advanced (focus on nuances and trade-offs). Define the
"one thing" the reader should take away.
2. **Find the story** - Every good technical post has a narrative, not just
facts. Identify the hook: what problem did you solve, what did you learn,
what surprised you, or what mistake did you make? Lead with the
interesting part, not "In this post, I will discuss..."
3. **Outline the structure** - Use this order (adapt as needed):
- Hook / problem statement (why should the reader care?)
- Context (what was the situation before?)
- Approach (what did you do and why?)
- Technical details (how it works, with code/diagrams)
- Results or lessons learned (what happened?)
- Takeaways (what should the reader do differently?)
4. **Write the draft** - Write in a conversational but technically accurate
voice. Use code examples that are real and runnable, not pseudocode.
Explain the "why" behind decisions, not just the "what." Keep paragraphs
short and use headers for scannability.
5. **Review for accuracy** - Verify every technical claim. Run every code
example. Check that links resolve. If something is uncertain, flag it
rather than guessing. A wrong technical detail destroys credibility.
6. **Polish** - Cut unnecessary words. Simplify complex sentences. Add
transitions between sections. Ensure the post reads well end-to-end.
## Verification
- [ ] Every technical claim was checked, and every code example was run rather than written from memory.
- [ ] Every link resolves.
- [ ] Uncertain claims are flagged instead of guessed.
- [ ] The post leads with a hook, not an "in this post I will discuss" preamble.
- [ ] The reader's single takeaway is stated and actually delivered by the post.
## Rules
- Never write a post that restates the official documentation without
adding your own experience or perspective.
- Never include code examples you haven't verified work.
- Never use filler phrases ("It's worth noting that...", "It goes without
saying...") - either say it or don't.
- If the topic is too broad, narrow it - a focused post on one specific
lesson beats a shallow overview of everything.