Community

blog-posts

Write blog posts and articles with a strong hook, clear structure, and a consistent voice. Use whenever the user asks for a blog post, article, newsletter issue, or long-form web content, wants a draft "for my blog/site", or shares an outline or topic to turn into a post — regardless of length or how casually they ask.

View on GitHub

Blog Posts

Write posts a busy person finishes. Every section must earn the scroll: concrete claims, real examples, no throat-clearing.

Before drafting

Establish (from the request, or by asking at most one question): audience, goal (teach / persuade / announce), target length, and voice. If the user has prior posts or a style note, match it. Otherwise default to: first person, plain words, short sentences, contractions.

Structure

  1. Hook (first 2–3 sentences): a specific problem, surprising fact, or scene — never "In today's fast-paced world" or a dictionary definition.
  2. Promise: one sentence on what the reader gets by the end.
  3. Body: 3–5 sections with descriptive subheads (a skimmer reading only subheads should get the argument). One idea per section, each grounded by an example, number, or mini-story.
  4. Close: restate the takeaway in fresh words + one clear next step. No "In conclusion".

Rules

  1. Specific beats general: "cut build time from 9 min to 40 s" not "significantly improved performance". Invent nothing — mark placeholders like [YOUR METRIC] when the user must fill facts in.
  2. Cut filler on sight: "very", "really", "it's important to note", "delve", "in order to".
  3. Vary sentence length; read one paragraph aloud mentally per section.
  4. Titles: give 3 options — one direct/SEO, one curiosity, one contrarian. Never promise what the post doesn't deliver.
  5. Format for the web: paragraphs ≤ 4 lines, bold the 3–5 load-bearing phrases, use a list only when order or enumeration matters.

Edge cases

  • Topic too broad ("write about AI"): propose 3 sharper angles and draft the one you'd pick, saying why.
  • SEO request: weave the keyword into title, first 100 words, and one subhead — never keyword-stuff.
  • Expert audience: skip 101 definitions; open at the frontier of what they already know.