Blog Writer
Create clear, accurate blog posts that help developers understand Lightfast capabilities and industry trends.
Critical: Accuracy Over Marketing
Before writing anything:
Verify every claim:
- If you cite a number, confirm the source
- If you mention a feature, confirm it exists in production
- When uncertain, ask for clarification
Never oversell:
- Disclose limitations: "Currently supports X; Y coming in vZ"
- Be honest about beta status and rollout timelines
Match category voice:
- Technology: Technical authority, data-driven
- Company: Visionary, category-defining
- Product: Problem-solver, benefit-oriented
Writing Guidelines
- Concise & scannable: Match category word counts
- Lead with value: Start with what readers gain
- Be transparent: Mention beta status, limitations
- Active voice: "You can now..." not "Users are able to..."
- No emoji: Professional tone
- Include TL;DR: 80-100 words for AI citation
- FAQ section: 3-5 questions matching search queries
- Code examples: Required for Technology posts
Workflow
- Detect category from input or ask if unclear
- Load category style from
resources/categories/{category}.md
- Research topic using web-search-researcher agent
- Draft following category template and templates
- Add AEO elements per aeo-requirements
- Review with checklist
Quick Reference
Category Selection
| Category |
Use When |
Audience |
| Technology |
Technical deep-dives, architecture, research |
Developers, engineers |
| Company |
Funding, partnerships, events, hiring |
Executives, investors |
| Product |
Feature launches, updates, tutorials |
Customers, prospects |
Do
- Include code examples (Technology)
- Use "shift from/to" narratives (Company)
- Lead with pain point (Product)
- Link to 3-5 related docs
Don't
- Marketing buzzwords without substance
- Claims without verification
- Long paragraphs (keep sections scannable)
- Generic corporate speak
Output
Save drafts to: thoughts/blog/{slug}-{YYYYMMDD-HHMMSS}.md
Required Frontmatter Fields
Every draft MUST include:
title, slug, publishedAt, category (core)excerpt, tldr (AEO)seo.metaDescription, seo.focusKeyword (SEO)_internal.status, _internal.generated (traceability)
See resources/templates.md for complete frontmatter template.
Resources
- Document Templates
- AEO Requirements
- Pre-Publish Checklist
- Technology Style Guide
- Company Style Guide
- Product Style Guide
1---2name: blog-writer-23description: Create category-aware, AEO-optimized blog posts for Lightfast. Use when writing technology deep-dives, company announcements, or product launches.4---5
6# Blog Writer
7
8Create clear, accurate blog posts that help developers understand Lightfast capabilities and industry trends.
9
10## Critical: Accuracy Over Marketing
11
12Before writing anything:
13
141. **Verify every claim:**
15 - If you cite a number, confirm the source
16 - If you mention a feature, confirm it exists in production
17 - When uncertain, ask for clarification
18
192. **Never oversell:**
20 - Disclose limitations: "Currently supports X; Y coming in vZ"
21 - Be honest about beta status and rollout timelines
22
233. **Match category voice:**
24 - Technology: Technical authority, data-driven
25 - Company: Visionary, category-defining
26 - Product: Problem-solver, benefit-oriented
27
28## Writing Guidelines
29
301. **Concise & scannable**: Match category word counts
312. **Lead with value**: Start with what readers gain
323. **Be transparent**: Mention beta status, limitations
334. **Active voice**: "You can now..." not "Users are able to..."
345. **No emoji**: Professional tone
356. **Include TL;DR**: 80-100 words for AI citation
367. **FAQ section**: 3-5 questions matching search queries
378. **Code examples**: Required for Technology posts
38
39## Workflow
40
411. **Detect category** from input or ask if unclear
422. **Load category style** from `resources/categories/{category}.md`
433. **Research topic** using web-search-researcher agent
444. **Draft following** category template and [templates](resources/templates.md)
455. **Add AEO elements** per [aeo-requirements](resources/aeo-requirements.md)
466. **Review with** [checklist](resources/checklist.md)
47
48## Quick Reference
49
50### Category Selection
51| Category | Use When | Audience |
52|----------|----------|----------|
53| Technology | Technical deep-dives, architecture, research | Developers, engineers |
54| Company | Funding, partnerships, events, hiring | Executives, investors |
55| Product | Feature launches, updates, tutorials | Customers, prospects |
56
57### Do
58- Include code examples (Technology)
59- Use "shift from/to" narratives (Company)
60- Lead with pain point (Product)
61- Link to 3-5 related docs
62
63### Don't
64- Marketing buzzwords without substance
65- Claims without verification
66- Long paragraphs (keep sections scannable)
67- Generic corporate speak
68
69## Output
70
71Save drafts to: `thoughts/blog/{slug}-{YYYYMMDD-HHMMSS}.md`
72
73### Required Frontmatter Fields
74
75Every draft MUST include:
76- `title`, `slug`, `publishedAt`, `category` (core)
77- `excerpt`, `tldr` (AEO)
78- `seo.metaDescription`, `seo.focusKeyword` (SEO)
79- `_internal.status`, `_internal.generated` (traceability)
80
81See `resources/templates.md` for complete frontmatter template.
82
83## Resources
84
85- [Document Templates](resources/templates.md)
86- [AEO Requirements](resources/aeo-requirements.md)
87- [Pre-Publish Checklist](resources/checklist.md)
88- [Technology Style Guide](resources/categories/technology.md)
89- [Company Style Guide](resources/categories/company.md)
90- [Product Style Guide](resources/categories/product.md)
majiayu000