Use when creating, editing, or publishing a blog post for the Pikari website, or when the user provides content ideas, drafts, or bullet points they want turned into a published post
Create and publish blog posts to the Pikari website. Handles everything from content shaping through to opening a pull request.
digraph publish {
rankdir=TB;
node [shape=box];
gather [label="Gather content from user\n(topic, draft, bullets, or idea)"];
shape [label="Shape into post\n(write/polish, match Pikari tone)"];
save [label="Save .mdx file to content/blog/"];
preview [label="Start dev server if not running\nOpen post in browser for preview"];
feedback [label="User wants changes?"];
publish [label="Branch, commit, push, open PR"];
done [label="Give user the PR link"];
gather -> shape -> save -> preview -> feedback;
feedback -> shape [label="yes"];
feedback -> publish [label="approved"];
publish -> done;
}
Tone: Professional but accessible. Research-backed, conversational. No marketing fluff. Short paragraphs (2-4 sentences). Concrete examples over theory.
Length: 6-12 minute reads, roughly 1,500-2,500 words.
Structure: Opening paragraph, 3-4 sections with H2 headings, no deep nesting. The <Callout> component is available for asides.
Categories (use exactly one):
Research - analysis, patterns, insightsFrameworks - repeatable methods and modelsCase Studies - deep dives on specific companies/teamsField Notes - practical lessons from real experienceAuthors:
| Name | Role | Avatar |
|---|---|---|
| Elena Vasquez | Research Lead | photo-1580489944761-15a19d654956 |
| Marcus Obi | Head of Research | photo-1507003211169-0a1dd7228f2d |
| Aiko Tanaka | Senior Writer | photo-1438761681033-6461ffad8d80 |
| David Park | Product Strategist | photo-1472099645785-5658abf4ff4e |
Avatar URLs follow the pattern: https://images.unsplash.com/{id}?w=200&q=80
Ask the user which author to use. If they aren't sure, suggest based on category and topic.
Filename: kebab-case matching the title (e.g., why-ai-needs-oversight.mdx)
---