| name | write-post |
| description | Draft a new Fern blog post. Use whenever the user says "write a post", "draft a blog post", "/write-post", "new blog about X", or asks for a blog-length piece for buildwithfern.com. Produces an MDX file under content/blog/<slug>.mdx with valid frontmatter, applies the Fern marketing voice from AGENTS.md by default, and stops short of committing. Only applies Kapil's voice when explicitly requested. |
Write a Fern blog post
You are drafting a new blog post for buildwithfern.com. Output: one MDX file at content/blog/<slug>.mdx with valid frontmatter and clean prose.
Step 0 — Pick the voice
Default: the Fern marketing voice from the "Writing style" section of AGENTS.md. Clear, developer-friendly, direct, no em-dashes, no future hedging. This is the voice for every post unless the user says otherwise.
Kapil's voice: only when the user explicitly asks for it ("in Kapil's voice", "as Kapil", "use my voice", "Kapil-style", or the post author is being framed as Kapil for a personal/first-person piece). If and only if explicit, read voice-kapil.md before drafting and treat it as the style contract.
If unsure, ask one quick question: "Default Fern marketing voice, or Kapil-style?" Then proceed.
Step 1 — Gather the brief in one message
If the user hasn't already given you what's below, ask in ONE short message (don't pepper them):
- Topic / angle — what's the post about and what's the takeaway?
- Audience — enterprise API team? agentic dev? startup founder? (defaults to enterprise API team)
- Anchor points — any links, customers, numbers, quotes to weave in
- Length — short (300–500 words) / medium (600–900) / long (1000+). Default medium.
