Brainstorm blog post ideas and develop them into outlines ready to write in Curupira. Use when the user wants to explore topics for writing, flesh out a blog idea, find angles for a post, connect ideas from their vault, or think through what to write about. Trigger on phrases like "blog idea", "what should I write about", "brainstorm", "help me think about a post", "develop this idea".
Interactive brainstorming for blog posts. Helps the user go from vague idea to concrete outline that serves as a GUIDE for writing in the Curupira blog engine.
The user writes like a thoughtful senior engineer teaching peers. Know this before suggesting anything:
The notes and outlines must match this voice. No formal academic tone. No AI-speak.
The user writes in Curupira (Elixir/Phoenix app at localhost:4000). The vault notes are REFERENCE MATERIAL, not the final article. Never write a full article in the vault. Write outlines, angles, key points, code sketches.
Brainstorm (vault) -> Outline (vault) -> Write in Curupira (localhost:4000) -> Export -> Deploy
Re-index and search the vault for existing material:
qmd update -c vault && qmd embed 2>/dev/null
qmd query -c vault "the topic being brainstormed"
Always start with qmd query. It returns snippets with context and relevance scores. Use those snippets directly. Only read full files when you need the complete outline (e.g. an existing draft you're building on). Only use rg if qmd misses something specific.
Also check the ideas backlog and existing drafts:
cat ~/vault/blog/ideas.md
ls ~/vault/blog/drafts/
If the user has a topic in mind:
If the user has no topic, suggest ideas based on:
Push back on weak ideas. Ask "why would someone read this?" Challenge the user to find their unique angle.
Once the idea has shape, propose:
The outline should be enough for the user to open Curupira and start writing. Not a full draft. A map.
After brainstorming, offer two actions:
Add to ideas backlog (not ready yet):
Append a bullet to ~/vault/blog/ideas.md under ## Backlog with title, angle, and one-line summary.
Create an outline (ready to start writing):
Create ~/vault/blog/drafts/{slug}.md with the outline, key points, code sketches, and references.
Always ask the user which one. Never create without confirmation.