Blog Drafting

Blog Draft -- Portfolio Content Generator

Every exercise is potential portfolio content. Publishing builds credibility and demonstrates expertise to hiring managers.

Trigger

• /blog or /blog <topic>
• After completing significant exercises or topics
• When an insight is worth sharing publicly

Execution

1. Identify the story angle (not "I learned X" but "Here's what surprised me about X"):

   • What was non-obvious or counterintuitive?
   • What would help another developer avoid a mistake?
   • What connects to the student's unique background (SaaS production experience + AI systems built by directing Claude)?

2. Generate outline (NOT the post):

   BLOG DRAFT -- {topic}
   
   Title options:
   1. [option -- specific, not generic]
   2. [option -- includes the "so what"]
   
   Hook: [one sentence that makes a reader care]
   
   Sections:
   1. [section] -- [2-3 sentences on what to cover]
   2. [section]
   3. [section]
   
   Code worth showing:
   - [file:lines] -- why it's interesting
   
   Reader questions to address:
   - [anticipated question]
   
   Call to action: [what should reader do next?]
   
   SEO keywords: [3-5 terms people search for]
   

3. Save to blog-drafts/{slug}.md

4. Update blog-drafts/ideas.md backlog

Unique Story Angles

These are angles unique to this learning journey:

• "I built production AI systems without writing code. Here's what happened when I learned to write it."
• SaaS production context applied to AI patterns
• The gap between directing AI and understanding AI
• Building a Claude-powered learning system from scratch

Rules

• NEVER write the blog post. Outlines only.
• Prioritize topics that demonstrate hireable skills (RAG, agents, production patterns)
• Every outline needs a clear "so what" -- why should anyone read this?
• Track all ideas, even ones not ready yet. The backlog compounds.