# content-creation-suite

> Research and write all content types including blog posts, social media, email marketing, technical documentation, long-form content, microcopy, and content repurposing. Use when creating any written content, optimizing copy, writing for specific platforms (Twitter, LinkedIn, email), creating documentation, or adapting content across formats.

- Author: Nir
- Repository: Nirkoso/Nir-Claude
- Version: 20260126102449
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-07
- Source: https://github.com/Nirkoso/Nir-Claude
- Web: https://mule.run/skillshub/@@Nirkoso/Nir-Claude~content-creation-suite:20260126102449

---

---
name: content-creation-suite
description: Research and write all content types including blog posts, social media, email marketing, technical documentation, long-form content, microcopy, and content repurposing. Use when creating any written content, optimizing copy, writing for specific platforms (Twitter, LinkedIn, email), creating documentation, or adapting content across formats.
---

# Content Creation Suite

Comprehensive content creation across all formats and platforms with best practices.

## Content Types & Structures

### 1. Blog Posts

**Blog Post Structure:**
```
Title: [Compelling headline with benefit or intrigue]
Subtitle: [Clarifying context]

Introduction (100-150 words):
- Hook (question, stat, story, or bold claim)
- Problem statement
- Promise of value
- Preview of what's covered

Body (organized by subheadings):
H2: [Main Point 1]
- Supporting details
- Examples
- Data/quotes

H2: [Main Point 2]
- Supporting details
- Examples
- Data/quotes

H2: [Main Point 3]
- Supporting details
- Examples
- Data/quotes

Conclusion:
- Summary of key points
- Call to action
- Next steps or further reading

Meta:
- Word count: [800-2000 words for standard post]
- Reading time: [Estimate]
- Keywords: [Primary and secondary SEO keywords]
```

**Blog Post Formula Options:**

**How-To Post:**
1. Problem statement
2. Step 1 (with details)
3. Step 2 (with details)
4. Step 3 (with details)
5. Common mistakes to avoid
6. Conclusion & CTA

**Listicle:**
1. Introduction (why this list matters)
2. Item 1 (with explanation & example)
3. Item 2 (with explanation & example)
4. Item 3-N (with explanation & example)
5. Bonus item (optional)
6. Conclusion

**Case Study:**
1. Challenge/Problem
2. Solution/Approach
3. Implementation
4. Results (with metrics)
5. Lessons learned
6. How to apply this

### 2. Social Media Copy

#### Twitter/X
```
Character limit: 280
Best practices:
- Front-load value in first line
- Use line breaks for readability
- One idea per tweet
- Include call-to-action
- Emoji for visual interest (sparingly)

Thread Structure:
1/ Hook tweet (stand-alone value)
2/ Context or problem
3-N/ Main points (one per tweet)
Final/ Summary + CTA

Example:
"The biggest mistake in product management isn't what you think.

It's not about prioritization or stakeholder management.

It's this: [Thread] 🧵

1/7"
```

#### LinkedIn
```
Character limit: 3,000 (but keep to 1,300 for visibility)

Format:
Opening Hook (1-2 lines) ← Creates intrigue
[Line break]
Context paragraph
[Line break]
Main insights:
→ Point 1
→ Point 2
→ Point 3
[Line break]
Conclusion or CTA

Best practices:
- Professional tone but conversational
- Use "→" or "•" for bullet points
- Personal stories work well
- Tag relevant people/companies
- Ask questions to boost engagement
```

#### Instagram/Facebook
```
Caption best practices:
- First line is critical (pre-"more" click)
- Tell stories
- Include clear CTA
- Use 3-5 relevant hashtags max
- Emoji for personality
- Ask questions to drive comments

Structure:
[Strong opening line]

[Story or context - 2-3 paragraphs]

[Call to action]

[Hashtags]
```

### 3. Email Marketing

#### Welcome Email Series
```
Email 1 (Immediate):
Subject: Welcome to [Product] - Let's get you started
Preview: Here's what to do first...

Body:
- Thank them for joining
- Set expectations (what they'll receive)
- One clear next step
- Quick win or value delivery

Email 2 (Day 2):
Subject: [Your first win with Product]
- Share success story or use case
- Provide helpful resource
- Encourage engagement

Email 3 (Day 5):
Subject: Are you stuck on anything?
- Offer help
- Common questions/FAQ
- Link to resources

Email 4 (Day 10):
Subject: Here's what you might have missed
- Advanced features
- Pro tips
- Upgrade opportunity (if applicable)
```

#### Newsletter Template
```
Subject Line: [Specific benefit or curiosity]
Preview Text: [Expand on subject, don't repeat]

Header:
[Brief greeting - optional]

Main Content:
Section 1: [Featured article/update]
- 2-3 sentences
- CTA: "Read more →"

Section 2: [Quick tips or links]
• Tip 1
• Tip 2
• Tip 3

Section 3: [Community/social proof]
- Customer story or testimonial
- Community highlight

Footer:
- Unsubscribe (required)
- Social links
- Contact info
```

#### Promotional Email
```
Subject: [Urgency + Benefit + Specificity]
Examples:
- "24 hours left: Save 30% on Pro"
- "Your exclusive invite inside"
- "We built this feature for you"

Structure:
Hook: [Address pain or desire]
Offer: [What they get]
Benefits: [Why it matters - 3-4 bullets]
Social Proof: [Testimonial or stat]
CTA: [Clear action button]
Urgency: [Deadline or scarcity]
P.S.: [Reinforcement or bonus]
```

### 4. Technical Documentation

#### User Guide Template
```
# [Feature/Product Name]

## Overview
Brief description of what this is and what it does.

## Getting Started
Prerequisites:
- Requirement 1
- Requirement 2

Installation/Setup:
1. Step 1
2. Step 2
3. Step 3

## Basic Usage
[Most common use case with example]

## Features
### Feature 1
Description:
How to use:
Example:

### Feature 2
Description:
How to use:
Example:

## Advanced
[Power user features]

## Troubleshooting
Problem: [Common issue]
Solution: [How to fix]

## FAQ
Q: [Question]
A: [Answer]

## Support
[How to get help]
```

#### API Documentation
```
# API Endpoint

## [HTTP Method] /api/endpoint

Description: [What this endpoint does]

### Request
Headers:
- Authorization: Bearer {token}
- Content-Type: application/json

Parameters:
- `parameter1` (string, required): Description
- `parameter2` (integer, optional): Description

Body:
```json
{
  "example": "request body"
}
```

### Response
Success (200):
```json
{
  "example": "response"
}
```

Error (400):
```json
{
  "error": "Error message"
}
```

### Example
```bash
curl -X POST \
  https://api.example.com/endpoint \
  -H 'Authorization: Bearer {token}' \
  -d '{"parameter1": "value"}'
```
```

### 5. Long-Form Content

#### White Paper Structure
```
Title Page:
- Compelling title
- Subtitle
- Author/company
- Date

Executive Summary (1 page):
- Key findings
- Main recommendations
- Bottom-line impact

Table of Contents

Introduction:
- Industry challenge
- Why this matters now
- What this paper covers

Problem Analysis:
- Current state
- Pain points
- Market data

Solution Framework:
- Approach overview
- Methodology
- Best practices

Case Studies:
- Example 1
- Example 2
- Results and lessons

Implementation Guide:
- Step-by-step process
- Tools and resources
- Timeline

Conclusion:
- Summary
- Call to action
- Next steps

About the Author/Company

References and Resources
```

### 6. Microcopy (UX Writing)

**Button Copy:**
```
❌ Weak: "Submit" "Click here" "OK"
✓ Strong: "Create Account" "Get Started" "Save Changes"

Principle: Describe the action and outcome
```

**Error Messages:**
```
❌ "Error 404"
✓ "We can't find that page. Try checking the URL or return to the homepage."

❌ "Invalid input"
✓ "Email addresses need an @ symbol. Can you check yours?"

Principle: Explain what happened and how to fix it
```

**Empty States:**
```
❌ "No items"
✓ "Your inbox is empty. Nice work!"

❌ "0 results"
✓ "No matches found. Try different keywords or browse all products."

Principle: Make it friendly and show next action
```

**Confirmation Messages:**
```
✓ "Changes saved"
✓ "Welcome back, [Name]!"
✓ "Message sent successfully"

Principle: Confirm action and outcome clearly
```

### 7. Content Repurposing

**From Blog Post:**
- → Twitter thread (key points)
- → LinkedIn post (main insight + personal take)
- → Email newsletter (summary + link)
- → Infographic (data points)
- → Video script (same structure)
- → Podcast outline (conversational version)
- → Slide deck (one slide per section)

**From Webinar:**
- → Blog post recap
- → Social snippets (quotes)
- → Email follow-up
- → FAQ document
- → Mini-course modules

**Repurposing Checklist:**
✓ Adapt tone for platform
✓ Resize/reformat visuals
✓ Optimize for platform limits
✓ Update CTAs for context
✓ Credit original if cross-posting

## Writing Best Practices

### General Principles
1. **Clarity over cleverness**: Be clear first, clever second
2. **Front-load value**: Put important info first
3. **Active voice**: "We launched" not "it was launched"
4. **Specific over generic**: Numbers, examples, concrete details
5. **One idea per sentence**: Easy to scan and understand
6. **Cut ruthlessly**: Every word must earn its place
7. **Read aloud**: If it sounds awkward, rewrite it

### Hook Formulas
- **Question**: "Want to know the secret to...?"
- **Stat**: "87% of marketers make this mistake..."
- **Story**: "Last week, I almost lost our biggest client..."
- **Bold claim**: "Everything you know about X is wrong"
- **Curiosity gap**: "The one thing that changed everything..."
- **Relatability**: "We've all been there: [common situation]..."

### Call-to-Action (CTA) Guidelines
- Make it specific and actionable
- Use strong action verbs
- Create urgency when appropriate
- Show the benefit clearly
- Make it visually prominent

**Examples:**
- ❌ "Learn more"
- ✓ "Get your free template"
- ✓ "Start your 14-day trial"
- ✓ "Download the guide"

## Quality Checklist

Before publishing, verify:
✓ Clear value proposition in intro
✓ Scannable (headings, bullets, short paragraphs)
✓ No jargon without explanation
✓ Spell-check and grammar-check
✓ Links work and open correctly
✓ Images have alt text
✓ CTA is clear and compelling
✓ Mobile-friendly formatting
✓ On-brand voice and tone