blog-generator

# Blog Generator

## Overview

This skill generates professional blog posts that consistently reflect a brand's voice, values, and communication style. It transforms basic topic inputs into structured, engaging content suitable for publication.

**Keywords**: blog post, blog writing, content creation, brand voice, thought leadership, SEO content, marketing content, article writing

## Prerequisites

Before generating a blog post, ensure one of the following is available:

1. **Brand Voice Profile** - Output from the `brand-voice-generator` skill containing:
   - Voice description (attributes, personality, style)
   - Core values with manifestation descriptions
   - Replication guidelines
   - Representative excerpts

2. **Inline Brand Voice** - User-provided voice characteristics including:
   - Tone descriptors (e.g., "innovative, informative, inviting")
   - Key values to embody
   - Style preferences

If no brand voice is provided, prompt the user: "To generate on-brand content, please provide your brand voice profile. You can create one using the brand-voice-generator skill, or describe your brand's tone and values."

## Workflow

### Step 1: Gather Inputs

Collect the following from the user:

**Required:**
- **Topic/Brief**: The subject matter and key points to cover
- **Brand Voice**: Profile or description of brand voice characteristics

**Optional:**
- **Target audience**: Who will read this content
- **Primary CTA**: What action readers should take
- **Key messages**: Specific points that must be included
- **SEO keywords**: Terms to incorporate naturally
- **Word count target**: Approximate length (default: 800-1200 words)

### Step 2: Apply Brand Voice Transformation

Reference `references/voice-transformation-guide.md` for detailed transformation rules.

**Core Transformation Principles:**

| Generic Approach | Brand Voice Approach |
|------------------|---------------------|
| Feature-first opening | Context-setting thought leadership |
| List-heavy structure | Narrative flow with conceptual sections |
| Sales-y, urgent tone | Measured, authoritative positioning |
| Technical headers | Value-focused headers |
| Feature enumeration | Business transformation framing |
| FAQ sections | Sophisticated reader assumptions |
| "Ready to try?" CTAs | Elevated, confident CTAs |

### Step 3: Structure the Blog Post

Apply the brand voice to each structural element:

#### 3.1 Opening (Hook + Context)
- Begin with industry context or thought leadership framing
- Avoid starting with product features or promotional language
- Establish relevance before introducing solution
- Match the emotional register from brand voice (inspiring, confident, etc.)

#### 3.2 Section Headers
- Use value-focused language over technical descriptions
- Headers should tell a transformation story
- Examples:
  - ❌ "What is [Product]?"
  - ✅ "Centralized Skill Management"
  - ❌ "Features List"
  - ✅ "Why This Matters for Enterprise AI"

#### 3.3 Body Paragraphs
- Follow sentence structure preferences from brand voice
- Use the specified formality level consistently
- Incorporate brand values naturally (don't state them explicitly)
- Maintain the relationship dynamic (guide, partner, expert, etc.)

#### 3.4 Supporting Evidence
- Frame benefits before mechanics
- Lead with business outcomes, follow with how
- Use the brand's preferred proof style (data, testimonials, logic)

#### 3.5 Closing + CTA
- Summarize transformation, not features
- CTA should match brand's confidence level
- Avoid desperate urgency; maintain brand authority

### Step 4: Generate Content

Write the blog post following this structure:

```
[Title - Clear, benefit-focused, matches brand voice]

[Opening paragraph - Industry context, thought leadership hook]

[Section 1 Header - Value-focused]
[2-3 paragraphs establishing context and relevance]

[Section 2 Header - Transformation-focused]
[2-3 paragraphs on capabilities/approach]

[Section 3 Header - Business impact]
[2-3 paragraphs on outcomes and benefits]

[Optional: Section 4 Header - How it works]
[Brief, accessible explanation if needed]

[Closing Header - Forward-looking]
[1-2 paragraphs with confident CTA]
```

### Step 5: Generate Metadata

After the blog post, provide:

**Meta Title** (50-60 characters)
- Include primary keyword
- Match brand voice tone

**Meta Description** (150-160 characters)
- Summarize value proposition
- Include call to action
- Match brand voice

### Step 6: Quality Check

Before delivering, verify:

- [ ] Opening establishes context before product/solution
- [ ] No list-heavy sections (convert to narrative)
- [ ] Headers are value-focused, not feature-focused
- [ ] Tone matches brand voice throughout
- [ ] CTA is confident, not desperate
- [ ] No FAQ section (unless specifically requested)
- [ ] Sentence structure matches brand preferences
- [ ] Word choice aligns with brand formality level

## Output Format

Deliver the blog post in this format:

```
# [Blog Title]

[Full blog content with proper markdown formatting]

---

**Meta Data**

**Meta Title:** [50-60 character title]

**Meta Description:** [150-160 character description]

**Primary Keywords:** [2-3 keywords]

**Word Count:** [Approximate count]
```

## Reference Files

- `references/voice-transformation-guide.md` - Detailed rules for applying brand voice
- `references/blog-structures.md` - Templates for different blog types
- `references/before-after-examples.md` - Examples showing brand voice transformation

## Blog Type Variations

Reference `references/blog-structures.md` for type-specific guidance:

- **Announcement/Launch**: Product or feature announcements
- **Thought Leadership**: Industry insights and perspectives  
- **How-To/Tutorial**: Educational content with steps
- **Case Study**: Customer success stories
- **Comparison**: Product or approach comparisons

## Best Practices

- **Lead with value**: Always establish why before what
- **Maintain narrative flow**: Each section should connect to the next
- **Embody, don't state**: Show brand values through writing style, don't list them
- **Assume sophistication**: Avoid over-explaining or FAQ-style content
- **Confident close**: End with authority, not desperation