| name | content-draft |
| description | Draft build-in-public posts, blog articles, and threads in the user's own voice from _context/voice.md. Triggers on - draft a post, write a post, linkedin post, blog post, write content, draft content, tweet, thread, what should I post. |
Content draft
Write in the USER'S voice, never in generic AI voice. The voice file is law.
Process
- Load
_context/voice.md. If it still says STATUS: TEMPLATE, stop and offer brain-setup first; drafting without a voice file produces generic slop.
- Load
_context/now-building.md, _context/stack.md, and _context/goals.md so the draft reflects what they are actually building and learning.
- Mine for material before inventing any: recent daily-log wins, TIL pages in the wiki, project milestones from
projects/, and content/published/ for angles already used (avoid repeats). Build-in-public content is strongest when it is a real artifact: a bug, a number, a before-and-after, a lesson.
- Draft. Match the samples in voice.md: tone, rhythm, vocabulary, opening style, closing style, formatting. Respect the never-use list absolutely.
- Save to
content/drafts/YYYY-MM-DD-slug.md with frontmatter: type: draft, platform, topic, created.
- Show the draft in chat for copy-paste. Offer one revision pass.
Publishing
- When the user says it shipped, move the file to
content/published/ and add published: date and link to its frontmatter.
- If a sibling
dev-portfolio/ (or *-website/) folder exists in the workspace and the piece is a blog post, offer to convert it to MDX in the site's content/blog/ following that repo's frontmatter conventions (read an existing post there first).
Rules
- One platform per draft; a LinkedIn post and a tweet about the same idea are two files.
- True stories from the brain beat invented examples; if there is no real material, ask what they worked on this week rather than fabricating.
- "What should I post" is a valid trigger: propose 3 angles from recent dailies, TILs, and project logs, let them pick one.
