Initial commit

2025-11-29 18:48:55 +08:00
commit f28999f19c
127 changed files with 62038 additions and 0 deletions
--- a/skills/content-brief-generator/references/content_frameworks.md
+++ b/skills/content-brief-generator/references/content_frameworks.md
@@ -0,0 +1,707 @@
+# Content Structure Frameworks
+
+Proven frameworks for organizing and writing compelling content.
+
+---
+
+## Overview
+
+Content frameworks are repeatable structures that guide writing and ensure your content achieves its goals. Use these templates to outline before writing.
+
+---
+
+## AIDA (Attention, Interest, Desire, Action)
+
+**Best for:** Marketing copy, sales pages, landing pages, email campaigns
+
+### Structure
+
+**1. Attention (Headline/Hook)**
+- Grab attention immediately
+- Promise a benefit
+- Create curiosity
+
+**2. Interest (Build engagement)**
+- Explain the problem
+- Show you understand their pain
+- Present relevant information
+
+**3. Desire (Create want)**
+- Show benefits and outcomes
+- Provide social proof
+- Paint a picture of success
+
+**4. Action (Drive conversion)**
+- Clear call-to-action
+- Remove friction
+- Create urgency
+
+### Example Outline
+
+```markdown
+# Stop Wasting Hours on Manual Testing [Attention]
+
+## Testing doesn't have to be painful [Interest]
+- Current state of manual testing
+- Why it's time-consuming
+- Hidden costs of bugs in production
+
+## Automated testing changes everything [Desire]
+- Save 20 hours per week
+- Catch bugs before deployment
+- Team testimonials
+- ROI calculator
+
+## Start automating today [Action]
+- Free trial (no credit card)
+- 5-minute setup
+- CTA button
+```
+
+---
+
+## PAS (Problem, Agitate, Solve)
+
+**Best for:** Blog posts, emails, social media, persuasive content
+
+### Structure
+
+**1. Problem**
+- Identify the pain point
+- Show you understand it
+- Make it relatable
+
+**2. Agitate**
+- Amplify the problem
+- Show consequences of inaction
+- Create urgency
+- Use emotion
+
+**3. Solve**
+- Present your solution
+- Show how it solves the problem
+- Provide proof
+- Call-to-action
+
+### Example Outline
+
+```markdown
+# Problem: Your API is slow
+- Users complain about response times
+- You're losing customers
+- You don't know why
+
+# Agitate: It's getting worse
+- Every 100ms delay = 1% revenue loss
+- Competitors are faster
+- Your reputation suffers
+- Engineers are overwhelmed debugging
+
+# Solve: Our monitoring platform
+- Real-time performance tracking
+- Identify bottlenecks instantly
+- Optimize before users notice
+- Case study: 50% faster in 2 weeks
+- CTA: Start free trial
+```
+
+---
+
+## Inverted Pyramid
+
+**Best for:** News articles, technical documentation, business content
+
+### Structure
+
+**1. Most important (Lead)**
+- Who, what, when, where, why (5 Ws)
+- Key information first
+- Answer main question
+
+**2. Supporting details**
+- Context and background
+- Additional facts
+- Quotes and data
+
+**3. Background information**
+- Less critical details
+- Historical context
+- Related information
+
+### Example Outline
+
+```markdown
+# Lead (Most important)
+Next.js 14 released today with major performance improvements:
+- 50% faster builds
+- Built-in caching
+- Server Actions stable
+
+# Supporting details
+- How Server Actions work
+- Performance benchmarks
+- Migration guide from v13
+- Developer quotes
+
+# Background
+- History of Next.js
+- Previous version features
+- Future roadmap
+```
+
+---
+
+## Storytelling Arc
+
+**Best for:** Case studies, brand stories, narrative content, testimonials
+
+### Structure
+
+**1. Setup (Character & Context)**
+- Introduce protagonist
+- Set the scene
+- Establish normal state
+
+**2. Conflict (Challenge)**
+- Problem arises
+- Stakes are established
+- Tension builds
+
+**3. Resolution (Solution)**
+- How problem was solved
+- Journey and obstacles
+- Transformation
+
+**4. Takeaway (Lesson)**
+- What was learned
+- Broader implications
+- Call-to-action
+
+### Example Outline
+
+```markdown
+# Setup
+- Meet Sarah, CTO of startup
+- Team of 20 engineers
+- Managing infrastructure manually
+
+# Conflict
+- Infrastructure costs spiraling
+- Deployment taking 4 hours
+- Engineers frustrated
+- Investors questioning spend
+
+# Resolution
+- Discovered our platform
+- Implemented in 2 weeks
+- Automated deployments
+- Cut costs 60%
+
+# Takeaway
+- Infrastructure-as-code is essential
+- Right tools unlock velocity
+- CTA: See how you can automate
+```
+
+---
+
+## How-To / Tutorial
+
+**Best for:** Educational content, guides, tutorials, instructions
+
+### Structure
+
+**1. Introduction**
+- What you'll learn
+- Why it matters
+- Prerequisites
+- Time estimate
+
+**2. Step-by-step instructions**
+- Numbered sequential steps
+- One action per step
+- Screenshots/code examples
+- Expected results
+
+**3. Troubleshooting**
+- Common errors
+- Solutions
+- How to get help
+
+**4. Conclusion**
+- What you accomplished
+- Next steps
+- Related resources
+
+### Example Outline
+
+```markdown
+# How to Deploy a Next.js App to Vercel
+
+## Introduction
+- What you'll build
+- Prerequisites: Node.js, Git, Next.js app
+- Time: 10 minutes
+
+## Steps
+1. Create Vercel account
+   - Go to vercel.com
+   - Sign up with GitHub
+   - Screenshot
+
+2. Connect repository
+   - Click "New Project"
+   - Select repo
+   - Screenshot
+
+3. Configure settings
+   - Framework: Next.js
+   - Build command
+   - Environment variables
+
+4. Deploy
+   - Click "Deploy"
+   - Wait for build
+   - View live site
+
+## Troubleshooting
+- Build fails: Check Node version
+- ENV vars missing: Add in settings
+
+## Next Steps
+- Custom domain
+- CI/CD integration
+- Performance monitoring
+```
+
+---
+
+## Listicle
+
+**Best for:** Top X articles, roundups, comparison posts, curated lists
+
+### Structure
+
+**1. Introduction**
+- Why this list matters
+- How items were selected
+- Quick overview
+
+**2. List items (typically 5-10)**
+- Each item: Title + description
+- Benefits and features
+- Examples or screenshots
+- Why it's on the list
+
+**3. Conclusion**
+- Summary
+- Recommendation
+- CTA
+
+### Listicle Types
+
+**Numbered (Ranked):**
+- Best to worst
+- Most to least important
+- Sequential order
+
+**Bulleted (Unranked):**
+- Equal weight
+- Any order
+- No hierarchy
+
+### Example Outline
+
+```markdown
+# 7 Essential VS Code Extensions for Python Developers
+
+## Introduction
+- Why VS Code for Python
+- How we selected these
+- All are free
+
+## List
+1. Pylance
+   - What it does
+   - Key features
+   - Installation
+   - Screenshot
+
+2. Python (Microsoft)
+   - Core extension
+   - Debugging features
+   - Why it's #1
+
+[Continue for 7 items]
+
+## Conclusion
+- Start with top 3
+- Try others as needed
+- CTA: Share your favorites
+```
+
+---
+
+## Comparison / Versus
+
+**Best for:** Product comparisons, alternative posts, decision content
+
+### Structure
+
+**1. Introduction**
+- What's being compared
+- Why it matters
+- Quick verdict (optional)
+
+**2. Overview of each option**
+- Brief description
+- Key features
+- Ideal user
+
+**3. Head-to-head comparison**
+- Feature by feature
+- Use table format
+- Pros and cons
+
+**4. Use cases**
+- When to use Option A
+- When to use Option B
+- Special scenarios
+
+**5. Verdict**
+- Recommendation
+- Decision framework
+- CTA
+
+### Example Outline
+
+```markdown
+# React vs Vue: Which Framework to Choose in 2024
+
+## Introduction
+- Both are popular
+- Key differences matter
+- We'll help you decide
+
+## React Overview
+- Created by Facebook
+- JSX syntax
+- Large ecosystem
+- Best for: Enterprise
+
+## Vue Overview
+- Progressive framework
+- Template syntax
+- Gentle learning curve
+- Best for: Rapid development
+
+## Feature Comparison
+
+| Feature | React | Vue |
+|---------|-------|-----|
+| Learning curve | Steep | Gentle |
+| Performance | Excellent | Excellent |
+| Ecosystem | Huge | Growing |
+
+## Use Cases
+- Choose React if: Large team, TypeScript
+- Choose Vue if: Solo dev, quick prototype
+
+## Verdict
+- No wrong choice
+- Context matters
+- CTA: Try both with tutorial
+```
+
+---
+
+## Ultimate Guide / Pillar Content
+
+**Best for:** Comprehensive resources, cornerstone content, authority building
+
+### Structure
+
+**1. Introduction (Table of Contents)**
+- What's covered
+- Who it's for
+- How to use guide
+- Jump links to sections
+
+**2. Fundamentals**
+- Basic concepts
+- Terminology
+- Why it matters
+
+**3. Deep Dive Sections**
+- Multiple major sections
+- Each could be standalone post
+- Comprehensive coverage
+
+**4. Advanced Topics**
+- Expert-level content
+- Edge cases
+- Best practices
+
+**5. Resources**
+- Tools and software
+- Further reading
+- Related guides
+
+**6. FAQ**
+- Common questions
+- Quick answers
+
+### Example Outline
+
+```markdown
+# The Complete Guide to API Authentication (2024)
+
+## Table of Contents
+[Jump links to all sections]
+
+## Introduction
+- Why authentication matters
+- What you'll learn
+- Who this is for
+
+## Part 1: Authentication Basics
+- What is authentication vs authorization
+- Common methods overview
+- Security principles
+
+## Part 2: API Keys
+- How they work
+- Implementation guide
+- Pros and cons
+- Best practices
+
+## Part 3: OAuth 2.0
+- OAuth flow explained
+- Implementation
+- Use cases
+- Security considerations
+
+## Part 4: JWT Tokens
+- How JWT works
+- Implement in Node.js
+- Refresh tokens
+- Security tips
+
+## Part 5: Best Practices
+- Security checklist
+- Performance optimization
+- Error handling
+- Testing authentication
+
+## Tools & Resources
+- Libraries and frameworks
+- Testing tools
+- Further reading
+
+## FAQ
+- 10+ common questions
+
+## Conclusion
+- Key takeaways
+- Choose right method
+- Next steps
+```
+
+---
+
+## Feature Announcement
+
+**Best for:** Product launches, new feature releases, updates
+
+### Structure
+
+**1. Headline + Visual**
+- Clear announcement
+- What's new
+- Eye-catching graphic
+
+**2. The Problem**
+- What users struggled with
+- Why we built this
+
+**3. The Solution**
+- How feature solves it
+- Key benefits
+- Demo or video
+
+**4. How It Works**
+- Step-by-step
+- Screenshots
+- Technical details
+
+**5. Availability**
+- Who can use it
+- How to access
+- Pricing (if applicable)
+
+**6. What's Next**
+- Future improvements
+- Feedback request
+- Related features
+
+### Example Outline
+
+```markdown
+# Introducing Real-Time Collaboration
+
+[Hero image/GIF]
+
+## The Problem
+- Users couldn't work together
+- Version conflicts
+- Lost changes
+
+## The Solution
+- Live cursors
+- Instant updates
+- Conflict resolution
+- 50ms latency
+
+## How It Works
+1. Invite team members
+2. See who's online
+3. Work simultaneously
+4. Changes sync instantly
+
+## Available Now
+- All Pro plans
+- No additional cost
+- Enable in settings
+
+## What's Next
+- Comments coming soon
+- Video chat integration
+- We'd love your feedback
+```
+
+---
+
+## Thought Leadership / Opinion
+
+**Best for:** Industry commentary, trend analysis, hot takes
+
+### Structure
+
+**1. Strong Opening**
+- Contrarian take or
+- Bold prediction or
+- Provocative question
+
+**2. Current State**
+- What most people think
+- Common assumptions
+- Status quo
+
+**3. Your Perspective**
+- Why you disagree or
+- What others are missing
+- Your unique insight
+
+**4. Evidence**
+- Data and examples
+- Trends you're seeing
+- Expert opinions
+
+**5. Implications**
+- What this means
+- Who's affected
+- What should change
+
+**6. Call-to-Action**
+- What readers should do
+- Discussion prompt
+- Share thoughts
+
+### Example Outline
+
+```markdown
+# Microservices Are Overrated (And Here's Why)
+
+## Opening
+- Everyone wants microservices
+- Most don't need them
+- Monoliths are underrated
+
+## Current State
+- Industry trends
+- Why microservices are popular
+- What blogs/consultants say
+
+## My Perspective
+- Complexity costs
+- Most apps aren't at scale
+- Premature optimization
+
+## Evidence
+- Case studies of failures
+- Cost analysis
+- When microservices make sense
+
+## Implications
+- Start with monolith
+- Extract services later
+- Focus on business value
+
+## Conclusion
+- Challenge the hype
+- Make informed decisions
+- Share your experience
+```
+
+---
+
+## Framework Selection Guide
+
+**Choose framework based on:**
+
+| Goal | Best Framework |
+|------|----------------|
+| Drive conversions | AIDA, PAS |
+| Educate/inform | Inverted Pyramid, How-To |
+| Build authority | Ultimate Guide, Thought Leadership |
+| Compare options | Comparison, Listicle |
+| Tell story | Storytelling Arc |
+| Announce feature | Feature Announcement |
+
+**Multiple frameworks:**
+- Can combine frameworks
+- Example: Storytelling intro + How-To body
+- Adapt to your needs
+
+---
+
+## Template for Any Framework
+
+```markdown
+# [Compelling Title]
+
+## Hook (First 100 words)
+- Grab attention
+- State problem or benefit
+- Include primary keyword
+
+## Body (Main content)
+- [Apply chosen framework]
+- Use subheadings
+- Include examples
+- Add visuals
+
+## Conclusion
+- Summarize key points
+- Reinforce main takeaway
+- Clear CTA
+
+## Additional Resources
+- Internal links
+- External references
+- Further reading
+```
+
+---
+
+**Remember:** Frameworks are starting points, not rigid rules. Adapt them to your content needs and audience.
--- a/skills/content-brief-generator/references/seo_guidelines.md
+++ b/skills/content-brief-generator/references/seo_guidelines.md
@@ -0,0 +1,730 @@
+
+
+# SEO Guidelines for Content Briefs
+
+Comprehensive SEO best practices for content writers to rank higher and drive organic traffic.
+
+---
+
+## SEO Fundamentals
+
+### What is SEO?
+
+**Search Engine Optimization (SEO)** is the practice of optimizing content to rank higher in search engine results pages (SERPs) and drive organic (unpaid) traffic.
+
+**Key components:**
+- **Technical SEO:** Site structure, performance, indexing
+- **On-page SEO:** Content optimization, keywords, meta tags
+- **Off-page SEO:** Backlinks, domain authority, social signals
+
+**This guide focuses on on-page SEO for content creation.**
+
+---
+
+## Keyword Research
+
+### Finding the Right Keywords
+
+**1. Start with seed keywords**
+- Your main topic or product
+- What users search for
+- Industry terminology
+
+**2. Expand with keyword tools**
+- **Google Keyword Planner** (free)
+- **Ahrefs** (paid, comprehensive)
+- **SEMrush** (paid, competitive analysis)
+- **Ubersuggest** (freemium)
+- **AnswerThePublic** (question-based keywords)
+
+**3. Analyze keyword metrics**
+
+| Metric | What It Means | Good Target |
+|--------|---------------|-------------|
+| Search Volume | Monthly searches | 500-10K for most content |
+| Keyword Difficulty | Competition (0-100) | < 40 for newer sites |
+| CPC | Paid ad cost | Higher = more commercial |
+| SERP Features | Rich snippets, featured boxes | Opportunity to capture |
+
+**4. Evaluate search intent**
+
+**Types of search intent:**
+- **Informational:** "how to", "what is", "guide to"
+- **Navigational:** Brand names, specific pages
+- **Commercial:** "best", "review", "comparison"
+- **Transactional:** "buy", "price", "discount"
+
+**Match content type to intent:**
+- Informational → Blog posts, guides, tutorials
+- Commercial → Reviews, comparisons, listicles
+- Transactional → Product pages, landing pages
+
+---
+
+## Keyword Strategy
+
+### Primary Keyword
+**One main target keyword per piece of content**
+
+**Characteristics:**
+- Relevant to topic
+- Moderate search volume (500-10K typically)
+- Achievable difficulty
+- Matches search intent
+
+**Example:**
+For a tutorial on JWT authentication:
+- Primary: "JWT authentication tutorial" (2,400/month, KD 35)
+
+### Secondary Keywords
+**2-4 related keywords that support the primary**
+
+**Types:**
+- Synonyms: "JSON web token tutorial"
+- Related terms: "JWT Node.js", "secure API authentication"
+- Long-tail variations: "how to implement JWT authentication"
+
+**Example:**
+- Secondary: "JSON web token Node.js", "JWT implementation guide", "API authentication tutorial"
+
+### LSI Keywords (Latent Semantic Indexing)
+**Related terms that provide context**
+
+**How to find:**
+- Google "related searches" at bottom of SERP
+- "People also ask" boxes
+- LSIGraph tool
+- Ahrefs "Also rank for" section
+
+**Example:**
+For JWT content: "access token", "refresh token", "bearer token", "authentication flow", "authorization header"
+
+---
+
+## On-Page SEO Elements
+
+### Title Tag (H1)
+
+**Requirements:**
+- Include primary keyword
+- 50-60 characters (to avoid truncation)
+- Compelling and click-worthy
+- Front-load important words
+
+**Formula:**
+`[Primary Keyword]: [Benefit/Hook] | [Brand]`
+
+**Examples:**
+
+❌ Bad:
+- "Authentication" (too vague)
+- "The Complete, Comprehensive, Ultimate Guide to JSON Web Token Authentication in Node.js Applications" (too long)
+
+✅ Good:
+- "JWT Authentication Tutorial: Secure Your Node.js API in 10 Minutes"
+- "How to Implement JWT Authentication | Complete Node.js Guide"
+
+**Best practices:**
+- Use power words: "Complete", "Ultimate", "Essential", "Proven"
+- Include numbers: "10 Minutes", "5 Steps", "2024 Guide"
+- Address user intent: "How to", "Step-by-Step", "Quick Start"
+
+---
+
+### Meta Description
+
+**Requirements:**
+- 150-160 characters
+- Include primary keyword
+- Compelling call-to-action
+- Accurate summary
+
+**Not a ranking factor but affects CTR (click-through rate)**
+
+**Formula:**
+`[Problem] + [Solution] + [Benefit/CTA]`
+
+**Examples:**
+
+❌ Bad:
+- "Learn about JWT authentication" (boring, no value)
+- "This article covers everything you need to know about JSON Web Tokens, including how they work, how to implement them, and best practices" (too long, truncated)
+
+✅ Good:
+- "Learn JWT authentication with Node.js in 10 minutes. Step-by-step tutorial with code examples. Secure your API today."
+- "Implement JWT authentication in your Node.js app. Complete guide with Express.js examples and security best practices."
+
+---
+
+### Headers (H2, H3, H4)
+
+**Purpose:**
+- Structure content for readability
+- Signal topic relevance to search engines
+- Improve featured snippet chances
+
+**Best practices:**
+
+**H2 (Main sections):**
+- Include keywords naturally
+- 3-7 H2s per article typically
+- Descriptive and scannable
+
+**H3 (Subsections):**
+- Support H2 topics
+- Use long-tail keywords
+- Answer specific questions
+
+**Examples:**
+
+✅ Good header structure:
+```
+# JWT Authentication Tutorial [H1]
+
+## What Is JWT Authentication? [H2 - keyword + question]
+
+## How JWT Authentication Works [H2 - keyword + process]
+### The Authentication Flow [H3]
+### Access Tokens vs Refresh Tokens [H3]
+
+## Implementing JWT in Node.js [H2 - keyword + action]
+### Installing Dependencies [H3]
+### Creating JWT Tokens [H3]
+### Verifying JWT Tokens [H3]
+
+## JWT Security Best Practices [H2 - keyword + value]
+```
+
+**Avoid:**
+- Generic headers: "Introduction", "Conclusion"
+- Keyword stuffing: "JWT JWT JWT Authentication"
+- Skipping heading levels (H2 → H4)
+
+---
+
+### Content Body
+
+**Keyword usage:**
+
+**Primary keyword placement:**
+- [ ] First 100 words (important!)
+- [ ] In H1 (title)
+- [ ] In at least one H2
+- [ ] In URL slug
+- [ ] 3-5 times throughout content (naturally)
+- [ ] In conclusion
+
+**Secondary keywords:**
+- [ ] Sprinkle naturally throughout
+- [ ] In H2s and H3s where relevant
+- [ ] In image alt text
+- [ ] In anchor text for internal links
+
+**Keyword density:**
+- **Target: 0.5-2.5%** of total words
+- Don't obsess over exact percentage
+- Prioritize natural writing
+- Use synonyms and variations
+
+**Example:**
+
+❌ Bad (keyword stuffing):
+"JWT authentication is important. JWT authentication secures your API. Implementing JWT authentication with JWT authentication libraries makes JWT authentication easier."
+
+✅ Good (natural use):
+"JWT authentication provides a secure way to handle user sessions in modern APIs. This token-based approach offers several advantages over traditional session management..."
+
+---
+
+### Internal Linking
+
+**Why it matters:**
+- Distributes page authority
+- Helps search engines discover pages
+- Improves user engagement
+- Reduces bounce rate
+
+**Best practices:**
+- **3-5 internal links** per blog post
+- Link to relevant related content
+- Use descriptive anchor text (not "click here")
+- Link to authoritative pages
+- Create content clusters
+
+**Anchor text examples:**
+
+❌ Bad:
+- "Click here to learn more"
+- "Read this article"
+- Full URLs as anchor text
+
+✅ Good:
+- "Learn about [secure API design patterns](link)"
+- "Our [Node.js security guide](link) covers..."
+- "For more on [authentication vs authorization](link)..."
+
+**Content clustering:**
+```
+Pillar Page: "Complete Guide to API Authentication"
+    ├─ Cluster: "JWT Authentication Tutorial"
+    ├─ Cluster: "OAuth 2.0 Implementation Guide"
+    ├─ Cluster: "API Key Best Practices"
+    └─ Cluster: "Session vs Token Authentication"
+```
+
+---
+
+### External Linking
+
+**Why link externally:**
+- Provides value to readers
+- Signals trust and authority
+- May earn reciprocal links
+- Shows you're not keyword-focused
+
+**Best practices:**
+- **2-3 external links** to authoritative sources
+- Link to original research/data
+- Link to tools/resources mentioned
+- Open in new tab (user preference)
+- Use `rel="nofollow"` for untrusted sources
+
+**Authority sources:**
+- Official documentation
+- Government sites (.gov)
+- Educational institutions (.edu)
+- Industry research firms
+- Reputable publications
+
+---
+
+### Images & Alt Text
+
+**SEO value:**
+- Image search traffic
+- Featured snippets with images
+- Improved user engagement
+- Accessibility (screen readers)
+
+**Image optimization:**
+
+**File size:**
+- Compress images (< 200KB ideal)
+- Use WebP format when possible
+- Lazy loading for below-fold images
+
+**File names:**
+- Descriptive, not "IMG_1234.jpg"
+- Include keyword: "jwt-authentication-flow.png"
+- Use hyphens, not underscores
+
+**Alt text:**
+- Describe image content
+- Include keyword naturally
+- 10-15 words typical
+- Don't stuff keywords
+
+**Examples:**
+
+❌ Bad:
+- Alt: "image" or empty
+- File: "screenshot-2024.png"
+
+✅ Good:
+- Alt: "JWT authentication flow diagram showing token generation and verification"
+- File: "jwt-authentication-flow-diagram.png"
+
+---
+
+## URL Structure
+
+**SEO-friendly URLs:**
+
+**Best practices:**
+- **Include primary keyword**
+- **Short and descriptive** (3-5 words)
+- **Use hyphens**, not underscores
+- **Lowercase only**
+- **Avoid parameters** (?id=123)
+
+**Examples:**
+
+❌ Bad:
+- `/blog/post?id=12345`
+- `/blog/2024/01/15/new-post`
+- `/JWT_Authentication_Tutorial_Complete_Guide`
+
+✅ Good:
+- `/jwt-authentication-tutorial`
+- `/blog/jwt-authentication-nodejs`
+- `/guides/api-authentication`
+
+---
+
+## Content Length & Quality
+
+### Optimal Length
+
+**General guidelines:**
+
+| Content Type | Optimal Length | Rationale |
+|--------------|----------------|-----------|
+| Blog post | 1,500-2,500 words | Comprehensive coverage |
+| Tutorial | 2,000-3,000 words | Detailed instructions |
+| Listicle | 1,000-2,000 words | Quick, scannable |
+| Landing page | 500-1,000 words | Concise, conversion-focused |
+| Product page | 300-500 words | Key info only |
+
+**But length isn't everything:**
+- Match top-ranking content length
+- Cover topic comprehensively
+- Don't add fluff to hit word count
+- Value > length
+
+### Content Quality Signals
+
+**E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness):**
+
+**Experience:**
+- First-hand knowledge
+- Personal insights
+- Real-world examples
+
+**Expertise:**
+- Author credentials
+- Technical accuracy
+- Depth of coverage
+
+**Authoritativeness:**
+- Backlinks from reputable sites
+- Author byline
+- Citations and references
+
+**Trustworthiness:**
+- Accurate information
+- Proper citations
+- Clear sources
+- Privacy policy, contact info
+
+---
+
+## Technical SEO Checklist
+
+### Page Speed
+- [ ] Page loads in < 3 seconds
+- [ ] Images optimized and compressed
+- [ ] Lazy loading implemented
+- [ ] Minified CSS/JS
+- [ ] Browser caching enabled
+
+### Mobile-Friendly
+- [ ] Responsive design
+- [ ] Text readable without zooming
+- [ ] Touch targets 48x48px+
+- [ ] No horizontal scrolling
+
+### Core Web Vitals
+- [ ] LCP (Largest Contentful Paint) < 2.5s
+- [ ] FID (First Input Delay) < 100ms
+- [ ] CLS (Cumulative Layout Shift) < 0.1
+
+### Indexing
+- [ ] Pages not blocked by robots.txt
+- [ ] XML sitemap submitted
+- [ ] Canonical tags set correctly
+- [ ] No duplicate content
+
+---
+
+## Featured Snippets & Rich Results
+
+### What Are Featured Snippets?
+
+**"Position 0" results** that appear above organic listings
+
+**Types:**
+- **Paragraph** (definitions, answers)
+- **List** (steps, rankings)
+- **Table** (comparisons, data)
+- **Video** (tutorials)
+
+### How to Win Snippets
+
+**1. Target question keywords**
+- "What is", "How to", "Why does"
+- "Best", "Top", "Checklist"
+
+**2. Structure for snippets**
+
+**Paragraph snippets:**
+- Answer question in 40-60 words
+- Place answer directly after H2
+- Define terms clearly
+
+**List snippets:**
+- Use numbered lists (for steps)
+- Use bullet lists (for items)
+- 5-8 items optimal
+
+**Table snippets:**
+- Use HTML tables
+- Clear headers
+- Comparison data
+
+**Example:**
+
+```markdown
+## What Is JWT Authentication?
+
+JWT (JSON Web Token) authentication is a stateless authentication method that uses cryptographically signed tokens to verify user identity. Instead of storing session data on the server, JWT embeds user information in a secure token that clients include with each request.
+
+### How JWT Authentication Works:
+
+1. User logs in with credentials
+2. Server validates and creates JWT
+3. Token sent to client
+4. Client includes token in requests
+5. Server verifies token signature
+```
+
+---
+
+## Schema Markup
+
+**Structured data** that helps search engines understand content
+
+**Common types for content:**
+- **Article:** Blog posts, news
+- **HowTo:** Step-by-step guides
+- **FAQPage:** FAQ sections
+- **VideoObject:** Embedded videos
+- **BreadcrumbList:** Navigation
+
+**Example (JSON-LD):**
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "Article",
+  "headline": "JWT Authentication Tutorial",
+  "author": {
+    "@type": "Person",
+    "name": "John Developer"
+  },
+  "datePublished": "2024-01-15",
+  "image": "https://example.com/jwt-tutorial.jpg"
+}
+```
+
+**Tools:**
+- [Google Rich Results Test](https://search.google.com/test/rich-results)
+- [Schema Markup Generator](https://technicalseo.com/tools/schema-markup-generator/)
+
+---
+
+## SEO Content Writing Process
+
+### 1. Keyword Research (1-2 hours)
+- [ ] Identify primary keyword
+- [ ] Find secondary keywords
+- [ ] Analyze top 10 results
+- [ ] Determine search intent
+- [ ] Note target word count
+
+### 2. Content Outline (30 min)
+- [ ] Create H2/H3 structure
+- [ ] Include keywords in headers
+- [ ] Plan internal links
+- [ ] Identify research needs
+
+### 3. Write First Draft (2-4 hours)
+- [ ] Write naturally first
+- [ ] Focus on value
+- [ ] Answer user questions
+- [ ] Include examples
+
+### 4. SEO Optimization (30-60 min)
+- [ ] Primary keyword in first 100 words
+- [ ] Keywords in headers (natural)
+- [ ] Add internal links (3-5)
+- [ ] Add external links (2-3)
+- [ ] Optimize images and alt text
+- [ ] Write meta description
+- [ ] Check keyword density
+
+### 5. Quality Check (30 min)
+- [ ] Fact-check all claims
+- [ ] Verify links work
+- [ ] Read aloud for flow
+- [ ] Check readability score
+- [ ] Proofread carefully
+
+---
+
+## SEO Tools
+
+### Free Tools
+- **Google Search Console** - Monitor performance
+- **Google Analytics** - Track traffic
+- **Google Keyword Planner** - Keyword research
+- **Ubersuggest** - Limited keyword data
+- **AnswerThePublic** - Question keywords
+- **Yoast SEO (WordPress)** - On-page optimization
+
+### Paid Tools
+- **Ahrefs** ($99-$999/mo) - All-in-one SEO
+- **SEMrush** ($119-$449/mo) - Comprehensive suite
+- **Surfer SEO** ($49-$199/mo) - Content optimization
+- **Clearscope** ($170+/mo) - Content intelligence
+- **MarketMuse** ($149-$600/mo) - Content planning
+
+### Free Browser Extensions
+- **Keywords Everywhere** - Search volume data
+- **MozBar** - Domain authority checker
+- **SEO Meta in 1 Click** - View meta tags
+- **Detailed** - View structured data
+
+---
+
+## Common SEO Mistakes
+
+### ❌ Avoid These
+
+**1. Keyword stuffing**
+- Overusing keywords unnaturally
+- Hurts readability and rankings
+
+**2. Thin content**
+- < 500 words without depth
+- Doesn't fully answer question
+
+**3. Duplicate content**
+- Copying content across pages
+- Plagiarizing from other sites
+
+**4. Ignoring mobile**
+- Non-responsive design
+- 60%+ of traffic is mobile
+
+**5. Slow page speed**
+- Large uncompressed images
+- Too many scripts
+- Poor hosting
+
+**6. No internal linking**
+- Isolated pages
+- Lost link equity
+
+**7. Bad user experience**
+- Intrusive popups
+- Auto-playing videos
+- Difficult navigation
+
+**8. Ignoring search intent**
+- Wrong content type
+- Doesn't answer query
+
+---
+
+## Measuring SEO Success
+
+### Key Metrics
+
+**Rankings:**
+- Track target keyword positions
+- Monitor ranking changes
+- Tool: Google Search Console, Ahrefs
+
+**Organic Traffic:**
+- Sessions from organic search
+- Growth over time
+- Tool: Google Analytics
+
+**Click-Through Rate (CTR):**
+- % of impressions that click
+- Improve with better titles/descriptions
+- Tool: Google Search Console
+
+**Engagement:**
+- Time on page (3+ minutes good)
+- Pages per session
+- Bounce rate (< 60% good)
+
+**Conversions:**
+- Goal completions from organic
+- Newsletter signups
+- Lead forms submitted
+
+### Timeline for Results
+
+**Realistic expectations:**
+- **Week 1-4:** Indexed, minimal movement
+- **Month 2-3:** Start ranking for long-tail
+- **Month 4-6:** Ranking for target keywords
+- **Month 6-12:** Established authority
+
+**Factors affecting timeline:**
+- Domain authority
+- Competition
+- Content quality
+- Backlinks
+
+---
+
+## SEO Checklist for Writers
+
+### Before Writing
+- [ ] Keyword research complete
+- [ ] Search intent identified
+- [ ] Top 10 results analyzed
+- [ ] Target word count determined
+
+### During Writing
+- [ ] Primary keyword in first 100 words
+- [ ] Keywords in H1, H2s naturally
+- [ ] Internal links planned (3-5)
+- [ ] External links identified (2-3)
+- [ ] Images with descriptive file names
+
+### After Writing
+- [ ] Meta description written (150-160 chars)
+- [ ] All images have alt text
+- [ ] URL slug optimized
+- [ ] Schema markup added (if applicable)
+- [ ] Links tested
+- [ ] Readability check (Flesch score 60+)
+- [ ] Mobile preview
+- [ ] Page speed check
+
+---
+
+## Quick Reference
+
+### Optimal Keyword Density
+- Primary: 0.5-2.5% of content
+- Don't force it, write naturally
+
+### Word Count Targets
+- Blog: 1,500-2,500 words
+- Tutorial: 2,000-3,000 words
+- Landering page: 500-1,000 words
+
+### Link Targets
+- Internal: 3-5 per post
+- External: 2-3 to authority sites
+
+### Title Length
+- 50-60 characters
+- Include primary keyword
+
+### Meta Description
+- 150-160 characters
+- Include keyword + CTA
+
+### Image Optimization
+- < 200KB file size
+- Descriptive file name
+- Alt text 10-15 words
+
+---
+
+**Remember:** SEO is important, but user experience comes first. Write for humans, optimize for search engines.
--- a/skills/content-brief-generator/references/tone_voice_guide.md
+++ b/skills/content-brief-generator/references/tone_voice_guide.md
@@ -0,0 +1,690 @@
+# Tone & Voice Guide
+
+Complete guide to developing and maintaining consistent voice and tone in your content.
+
+---
+
+## Voice vs. Tone
+
+### Voice
+**Your brand's personality** - consistent across all content
+
+**Think of it as:**
+- Who you are as a brand
+- Your character
+- Never changes
+
+**Examples:**
+- Mailchimp: "Friendly, helpful, human"
+- Stripe: "Direct, technical, trustworthy"
+- Nike: "Inspirational, motivational, bold"
+
+### Tone
+**How voice adapts** to context - changes based on situation
+
+**Think of it as:**
+- Your emotional state
+- How you say something
+- Varies by context
+
+**Examples:**
+- **Error message:** Apologetic, helpful
+- **Success message:** Congratulatory, encouraging
+- **Technical docs:** Professional, precise
+- **Marketing:** Enthusiastic, persuasive
+
+**Analogy:**
+Voice = Your personality
+Tone = Your mood
+
+---
+
+## Defining Your Voice
+
+### Voice Attributes Framework
+
+Choose 3-4 core attributes that define your brand voice:
+
+**The Spectrum:**
+
+```
+Formal ←────────────→ Casual
+Serious ←────────────→ Funny
+Respectful ←────────────→ Irreverent
+Enthusiastic ←────────────→ Matter-of-fact
+Traditional ←────────────→ Innovative
+```
+
+### Example Voice Definitions
+
+**Mailchimp:**
+- Friendly but not silly
+- Clever but not overly witty
+- Helpful but not overbearing
+- Expert but not bossy
+
+**Slack:**
+- Professional but approachable
+- Technical but not intimidating
+- Playful but not childish
+- Direct but not cold
+
+**Atlassian:**
+- Straightforward and honest
+- Enthusiastically professional
+- Conversational yet informative
+- Smart but not condescending
+
+---
+
+## Voice Dimensions
+
+### 1. Formality
+
+**Formal:**
+- Professional language
+- Complete sentences
+- No contractions
+- Third person
+
+**Example:**
+"The application has been successfully deployed to the production environment."
+
+**Casual:**
+- Conversational language
+- Contractions okay
+- First/second person
+- Shorter sentences
+
+**Example:**
+"You're all set! Your app is live."
+
+**When to use:**
+- Formal: Legal, compliance, enterprise docs
+- Casual: Blogs, social media, onboarding
+
+---
+
+### 2. Enthusiasm
+
+**Highly Enthusiastic:**
+- Exclamation points
+- Superlatives (amazing, incredible)
+- Energy and excitement
+- Emojis (in appropriate contexts)
+
+**Example:**
+"This is amazing! You just saved 10 hours of work. Let's celebrate! 🎉"
+
+**Neutral/Matter-of-fact:**
+- Period instead of exclamation
+- Factual statements
+- No hyperbole
+- Professional tone
+
+**Example:**
+"The task has been completed successfully. You saved 10 hours."
+
+**When to use:**
+- Enthusiastic: Consumer products, celebrations, achievements
+- Neutral: Technical docs, business content, data reports
+
+---
+
+### 3. Technical Level
+
+**Highly Technical:**
+- Industry jargon
+- Assumes expert knowledge
+- Technical accuracy paramount
+- Detailed specifications
+
+**Example:**
+"The WebSocket connection establishes a persistent, full-duplex communication channel over a single TCP connection."
+
+**Accessible:**
+- Plain language
+- Explain jargon
+- Analogies and examples
+- Beginner-friendly
+
+**Example:**
+"WebSockets let your app and server talk back and forth in real-time, like a phone call instead of sending letters."
+
+**When to use:**
+- Technical: API docs, developer tools, architecture guides
+- Accessible: Getting started guides, general audience, marketing
+
+---
+
+### 4. Humor
+
+**Funny/Playful:**
+- Jokes and puns
+- Pop culture references
+- Light-hearted
+- Personality shines
+
+**Example:**
+"Oops! Looks like something went wrong. Our bad. We're on it faster than you can say 'Have you tried turning it off and on again?'"
+
+**Serious:**
+- Professional
+- No jokes
+- Straightforward
+- Business-like
+
+**Example:**
+"An error has occurred. Our team has been notified and is working to resolve the issue."
+
+**When to use:**
+- Playful: Consumer brands, creative industries, social media
+- Serious: Financial services, healthcare, legal, critical errors
+
+---
+
+## Writing in Your Voice
+
+### Voice Checklist
+
+For every piece of content, ask:
+
+- [ ] **Does this sound like us?** (matches voice attributes)
+- [ ] **Is it consistent** with previous content?
+- [ ] **Would our audience recognize us** without our logo?
+- [ ] **Does it feel authentic** or forced?
+
+### Voice Examples by Sentence
+
+**Same content, different voices:**
+
+**Topic: User made an error**
+
+**Mailchimp (friendly, helpful):**
+"Oops! It looks like that email address isn't quite right. Try checking for typos?"
+
+**Stripe (direct, technical):**
+"Invalid email format. Use format: user@example.com"
+
+**Innocent (playful, quirky):**
+"That email address looks a bit wonky. Give it another go?"
+
+**IBM (formal, professional):**
+"The email address entered is invalid. Please verify and try again."
+
+---
+
+## Adapting Tone
+
+### Tone Guidelines by Context
+
+| Context | Tone | Example |
+|---------|------|---------|
+| **Error message** | Apologetic, helpful | "Sorry about that! Here's how to fix it..." |
+| **Success** | Encouraging | "Nice work! You're all set." |
+| **Warning** | Urgent but calm | "Action required: Your payment failed." |
+| **Education** | Patient, clear | "Let's walk through this together." |
+| **Marketing** | Persuasive, exciting | "Transform your workflow in minutes!" |
+| **Legal** | Formal, precise | "By continuing, you agree to the terms." |
+| **Support** | Empathetic, solution-focused | "I understand this is frustrating. Let's solve it." |
+
+---
+
+## Person & Perspective
+
+### First Person (We, Our)
+
+**When to use:**
+- Brand speaking
+- Company announcements
+- Team perspective
+
+**Example:**
+"We're excited to announce our new feature. We built this based on your feedback."
+
+**Pros:**
+- Personal connection
+- Shows team behind brand
+- Takes ownership
+
+**Cons:**
+- Can feel self-focused
+- Less about user
+
+---
+
+### Second Person (You, Your)
+
+**When to use:**
+- Most common
+- User instructions
+- Direct communication
+- Marketing copy
+
+**Example:**
+"You can now collaborate in real-time. Your team will love it."
+
+**Pros:**
+- User-focused
+- Clear and direct
+- Creates connection
+
+**Cons:**
+- Can feel pushy if overused
+
+---
+
+### Third Person (They, User, Customer)
+
+**When to use:**
+- Documentation
+- Objective content
+- Case studies about others
+
+**Example:**
+"The user navigates to settings. The system validates their credentials."
+
+**Pros:**
+- Professional
+- Objective
+- Clear for documentation
+
+**Cons:**
+- Less personal
+- Can feel distant
+
+---
+
+## Active vs. Passive Voice
+
+### Active Voice (Preferred)
+
+**Structure:** Subject performs action
+
+**Examples:**
+- "You can deploy your app in minutes."
+- "The system processes your request."
+- "Click the button to continue."
+
+**Why use:**
+- Clearer
+- More direct
+- Easier to read
+- Stronger
+
+---
+
+### Passive Voice (Avoid Usually)
+
+**Structure:** Action performed on subject
+
+**Examples:**
+- "Your app can be deployed in minutes."
+- "Your request is processed by the system."
+- "The button should be clicked to continue."
+
+**When to use:**
+- Actor unknown: "The server was restarted."
+- Actor irrelevant: "The file was deleted."
+- Soften message: "An error was encountered."
+
+---
+
+## Sentence Structure
+
+### Short Sentences
+- Easy to read
+- Scannable
+- Mobile-friendly
+- Clear
+
+**Example:**
+"Deploy your app fast. No config needed. It just works."
+
+**When to use:**
+- Headlines
+- Key points
+- Mobile content
+- Emphasis
+
+---
+
+### Varied Length
+- More natural
+- Maintains interest
+- Provides rhythm
+
+**Example:**
+"Deploy your app fast. No configuration needed, no complicated setup process, no hours wasted on devops. It just works."
+
+**When to use:**
+- Blog posts
+- Long-form content
+- Storytelling
+
+---
+
+## Word Choice
+
+### Simple vs. Complex
+
+**Prefer simple:**
+- Use vs. utilize
+- Help vs. assist
+- Buy vs. purchase
+- Start vs. commence
+- Show vs. demonstrate
+
+**Exception:** Technical accuracy requires specific terms
+
+---
+
+### Positive vs. Negative
+
+**Positive framing (preferred):**
+- "Remember your password"
+- "Include your address"
+- "Make sure to save"
+
+**Negative framing (avoid):**
+- "Don't forget your password"
+- "Don't leave out your address"
+- "Don't lose your work"
+
+---
+
+### Concrete vs. Abstract
+
+**Concrete (preferred):**
+- "Save 10 hours per week"
+- "Deploy in 5 minutes"
+- "99.9% uptime"
+
+**Abstract (avoid):**
+- "Save time"
+- "Fast deployment"
+- "Reliable service"
+
+---
+
+## Common Writing Guidelines
+
+### Contractions
+
+**Use them for conversational tone:**
+- Don't vs. Do not
+- You're vs. You are
+- We've vs. We have
+
+**Skip them for:**
+- Legal content
+- Very formal contexts
+- When emphasis needed: "Do not delete this"
+
+---
+
+### Exclamation Points
+
+**Use sparingly:**
+- Celebrations and achievements
+- Very exciting news
+- Strong emphasis
+
+**Limit to:**
+- Once per paragraph max
+- Never multiple (!!!)
+- Not in B2B formal content
+
+---
+
+### Emojis
+
+**When appropriate:**
+- Consumer brands
+- Casual social media
+- Internal communications
+- In-app celebrations
+
+**Avoid in:**
+- Enterprise B2B
+- Documentation
+- Legal/compliance
+- Serious topics
+
+---
+
+## Brand Voice Examples
+
+### Technology/Developer Tools
+
+**Stripe:**
+- **Voice:** Direct, technical, trustworthy
+- **Example:** "Accept payments in minutes. Get started with a few lines of code."
+- **Why it works:** Developers want clarity and speed
+
+**Vercel:**
+- **Voice:** Modern, enthusiastic, technical
+- **Example:** "Deploy your Next.js app. It's crazy fast."
+- **Why it works:** Balances technical and excitement
+
+**Twilio:**
+- **Voice:** Friendly, technical, empowering
+- **Example:** "Build the future of communications. We make it simple."
+- **Why it works:** Technical but approachable
+
+---
+
+### Consumer Products
+
+**Mailchimp:**
+- **Voice:** Friendly, helpful, sometimes quirky
+- **Example:** "That email looks a bit wonky. Want to check it?"
+- **Why it works:** Makes tedious tasks feel human
+
+**Slack:**
+- **Voice:** Professional-casual, helpful, clear
+- **Example:** "Work, simplified. Your team will thank you."
+- **Why it works:** Professional without being stuffy
+
+**Headspace:**
+- **Voice:** Calm, supportive, encouraging
+- **Example:** "Take a moment for yourself. You deserve it."
+- **Why it works:** Matches meditation/wellness mission
+
+---
+
+### Enterprise/B2B
+
+**Salesforce:**
+- **Voice:** Professional, empowering, visionary
+- **Example:** "Transform your business. Connect with customers in a whole new way."
+- **Why it works:** Aspirational but credible
+
+**Atlassian:**
+- **Voice:** Straightforward, enthusiastic, smart
+- **Example:** "Teamwork doesn't have to be hard. Let's make it easier."
+- **Why it works:** Acknowledges real problems, offers solutions
+
+---
+
+## Developing Your Voice
+
+### Step 1: Define Core Attributes
+
+Choose 3-4 from these dimensions:
+
+**Formality:**
+- Formal, professional, casual, conversational
+
+**Humor:**
+- Serious, playful, witty, irreverent
+
+**Enthusiasm:**
+- Energetic, neutral, understated
+
+**Technical:**
+- Expert, accessible, simple
+
+**Empathy:**
+- Warm, neutral, distant
+
+---
+
+### Step 2: Create Voice Chart
+
+| Attribute | We are | We are not | Example |
+|-----------|---------|------------|---------|
+| Professional | Clear and helpful | Stuffy or robotic | "Here's how to..." not "One must..." |
+| Friendly | Warm and welcoming | Overly casual | "Welcome!" not "Sup!" |
+| Technical | Accurate and precise | Jargon-heavy | Explain terms first time |
+
+---
+
+### Step 3: Write Examples
+
+For each voice attribute, write before/after examples:
+
+**Before (generic):**
+"Our platform provides solutions for your business needs."
+
+**After (our voice - direct, technical, helpful):**
+"Deploy your apps faster with built-in CI/CD and automatic scaling."
+
+---
+
+### Step 4: Create Voice Guidelines
+
+Document:
+- [ ] Core voice attributes (3-4)
+- [ ] Do's and don'ts
+- [ ] Example sentences
+- [ ] Tone by context
+- [ ] Word choice preferences
+- [ ] Grammar rules (contractions, etc.)
+
+---
+
+## Testing Your Voice
+
+### Voice Consistency Check
+
+1. **Remove branding** from 5 pieces of content
+2. **Mix with competitors'** content
+3. **Can people identify yours?**
+
+If yes → Voice is distinctive
+If no → Need stronger voice
+
+---
+
+### Reader Feedback
+
+Ask your audience:
+- How would you describe our voice?
+- Does it match your expectations?
+- What do you like/dislike?
+
+---
+
+## Maintaining Voice
+
+### Team Alignment
+
+**Onboarding:**
+- Share voice guidelines
+- Review examples
+- Practice exercises
+
+**Review Process:**
+- Check content against voice guidelines
+- Provide specific feedback
+- Create a voice champion
+
+**Documentation:**
+- Voice guidelines in shared doc
+- Examples library
+- Regular updates
+
+---
+
+### Voice Evolution
+
+**When to evolve:**
+- Rebranding
+- New audience
+- Company maturity
+- Market shift
+
+**How to evolve:**
+- Document changes
+- Transition gradually
+- Update guidelines
+- Train team
+
+**What to keep:**
+- Core personality
+- Brand values
+- Recognition
+
+---
+
+## Voice Guidelines Template
+
+```markdown
+# [Brand] Voice & Tone Guide
+
+## Our Voice
+
+[Brand] sounds [attribute], [attribute], and [attribute].
+
+### Core Attributes
+
+**1. [Attribute Name]**
+- What it means: [Description]
+- We are: [Example]
+- We're not: [Counter-example]
+
+**2. [Attribute Name]**
+[Repeat]
+
+**3. [Attribute Name]**
+[Repeat]
+
+## Grammar & Mechanics
+
+- Contractions: [Yes/No]
+- Exclamation points: [Use sparingly/Never/Frequently]
+- Emojis: [Appropriate contexts]
+- Person: [First/Second/Third]
+- Active voice: [Always/Usually/Varies]
+
+## Tone by Context
+
+| Context | Tone | Example |
+|---------|------|---------|
+| Error | Apologetic | "Sorry about that..." |
+| Success | Encouraging | "Nice work!" |
+| Documentation | Clear | "Follow these steps:" |
+
+## Word Choices
+
+**Preferred:**
+- [Word 1] over [Word 2]
+- [Word 3] over [Word 4]
+
+**Avoid:**
+- [Words/phrases to avoid]
+
+## Examples
+
+### Good Examples
+[3-5 examples that nail the voice]
+
+### Before/After
+**Before:** [Generic version]
+**After:** [Our voice version]
+```
+
+---
+
+**Remember:** Your voice should feel authentic, not forced. If it doesn't feel like "you," it won't resonate with your audience.