Brand Voice Generator

Brand & Voice Generator

Generate complete brand configuration files for use with the PPTX Generator and other brand-aware skills. This skill guides users through an interactive process to define their brand identity and writing voice.

What This Creates

Output Location

Files are created in:

.claude/skills/pptx-generator/brands/{brand-name}/

---

Process Overview

1. Gather Brand Basics - Name, description, primary use case 2. Define Colors - 10 color values for the complete system 3. Define Typography - Heading, body, and code fonts 4. Define Assets - Logo and icon paths 5. Discover Voice - Personality, vocabulary, sentence patterns 6. Create Design Philosophy - Core principles and signature elements 7. Generate Files - Create all four files with gathered information 8. Verify Setup - Confirm files are correctly placed

---

Step 1: Gather Brand Basics

Ask the user for:

Suggested question:

"Let's set up your brand. What's your brand name? (This will be the folder name - use lowercase with hyphens, like 'my-brand')"

---

Step 2: Define Colors

Gather 10 color values. Colors should be hex codes WITHOUT the # prefix.

Required Colors

Color Discovery Questions

If user doesn't have a full color system, guide them:

1. "What's your signature brand color? (This becomes your primary accent)" 2. "Do you prefer a dark theme (dark background, light text) or light theme?" 3. "Do you have secondary colors, or should I suggest complements?"

Color Suggestions by Theme

For dark themes, suggest:

background: 0a0a0a to 1a1a2e range
text: f5f5f5 to ffffff range
card_bg: 1a1a1a to 2d2d44 range

For light themes, suggest:

background: ffffff to f8f9fa range
text: 1a1a1a to 333333 range
card_bg: f0f0f0 to e8e8e8 range

---

Step 3: Define Typography

Gather 3 font names:

Question:

"What fonts should we use? I need a heading font, body font, and code/monospace font. Common choices are Inter for both heading and body, and JetBrains Mono for code."

Default if unsure:

• Heading: Inter
• Body: Inter
• Code: JetBrains Mono

---

Step 4: Define Assets

Gather asset paths (relative to brand folder):

Question:

"Do you have a logo file? If so, you'll need to copy it to the brand folder. What's the filename? (e.g., 'logo.png')"

If they have a logo, set path to assets/logo.png (they'll copy it there). If no logo, set to null.

---

Step 5: Discover Voice

This is the most important step for content quality. Guide the user through voice discovery.

Voice Discovery Questions

Ask these questions to understand their voice:

1. Personality in 3 words:

"Describe your brand's personality in exactly 3 words. Examples: 'Bold, Technical, Approachable' or 'Calm, Authoritative, Helpful'"

2. Voice influences:

"Who are 2-3 creators, brands, or people whose communication style you admire? This helps me understand the vibe."

3. Vocabulary patterns:

"What words or phrases do you use often? Any pet phrases, intensifiers you like ('super', 'incredibly'), or words you naturally reach for?"

4. What to avoid:

"What kind of tone or phrases do you want to AVOID? (e.g., corporate speak, hype language, overly casual)"

5. Sentence style:

"Do you prefer: Short punchy sentences, longer flowing explanations, or a mix? Do you use contractions ('don't', 'can't') casually?"

6. Teaching style (if applicable):

"When explaining something complex, how do you approach it? Show process/iterations? Use analogies? Lead with practical then theory?"

Voice Templates Reference

Read references/voice-templates.md for example voice configurations to show the user.

---

Step 6: Create Design Philosophy

Based on gathered information, help define:

Core Principles (3-4)

Ask:

"What are 3-4 design principles that guide your visual choices? For example: 'Clean over flashy', 'Technical but approachable', 'Dark mode by default'"

Signature Elements

Ask:

"Do you have any signature visual elements? Examples: Glass card effects, specific shadow styles, gradient patterns, geometric shapes, glow effects"

If unsure, suggest based on their colors and theme.

---

Step 7: Generate Files

Create all four files using the gathered information.

brand.json

{
  "name": "{display_name}",
  "description": "{description}",

  "colors": {
    "background": "{background}",
    "background_alt": "{background_alt}",
    "text": "{text}",
    "text_secondary": "{text_secondary}",
    "accent": "{accent}",
    "accent_secondary": "{accent_secondary}",
    "accent_tertiary": "{accent_tertiary}",
    "code_bg": "{code_bg}",
    "card_bg": "{card_bg}",
    "card_bg_alt": "{card_bg_alt}"
  },

  "fonts": {
    "heading": "{heading_font}",
    "body": "{body_font}",
    "code": "{code_font}"
  },

  "assets": {
    "logo": "{logo_path}",
    "logo_dark": {logo_dark_path},
    "icon": {icon_path}
  }
}

config.json

{
  "output": {
    "directory": "output/{brand_name}",
    "naming": "{name}-{date}",
    "keep_parts": false
  },
  "generation": {
    "slides_per_batch": 5,
    "auto_combine": true,
    "open_after_generate": false
  },
  "defaults": {
    "slide_width_inches": 13.333,
    "slide_height_inches": 7.5
  }
}

tone-of-voice.md

Use the template in references/tone-template.md and fill with gathered voice information.

brand-system.md

Use the template in references/brand-template.md and fill with gathered design information.

---

Step 8: Verify Setup

After generating files:

1. List created files:

   Glob: .claude/skills/pptx-generator/brands/{brand-name}/*

2. Remind about assets:

"Don't forget to copy your logo file to .claude/skills/pptx-generator/brands/{brand-name}/assets/"

3. Suggest test:

"Try generating a simple presentation with: 'Create a 3-slide presentation for {brand-name} about [topic]'"

---

Quick Mode

If user just wants to get started quickly:

1. Ask only for: brand name, signature color, and light/dark preference 2. Generate sensible defaults for everything else 3. Create minimal but functional files 4. Tell them they can refine later

Quick mode trigger phrases:

• "quick setup"
• "just the basics"
• "minimal brand"
• "get started fast"

---

Updating Existing Brand

If a brand already exists:

1. Read existing files first 2. Ask what to update:

• Colors only?
• Voice only?
• Everything?

3. Preserve unchanged sections 4. Show diff of changes before writing

---

Checklist

• [ ] Gather brand name and description
• [ ] Collect all 10 color values (or suggest defaults)
• [ ] Collect 3 font names (or use defaults)
• [ ] Determine asset paths
• [ ] Discover voice through questions
• [ ] Define design principles
• [ ] Generate brand.json
• [ ] Generate config.json
• [ ] Generate tone-of-voice.md
• [ ] Generate brand-system.md
• [ ] Create assets folder
• [ ] Verify all files created
• [ ] Remind user about logo copying
• [ ] Suggest test generation

Brand System Template

Use this template to generate the brand-system.md file. Replace all {placeholder} values with gathered information.

---

# {brand_name} — Brand System

> {brand_tagline}

---

## Brand Philosophy

### Core Principles

1. **{principle_1_name}**
   {principle_1_description}

2. **{principle_2_name}**
   {principle_2_description}

3. **{principle_3_name}**
   {principle_3_description}

{additional_principles}

---

## Logo

### The {brand_name} Mark

{logo_description}

**Logo file**: `.claude/skills/pptx-generator/brands/{brand_folder}/assets/logo.png`

**Usage rules:**
- Maintain aspect ratio
- Minimum clear space: 20% of logo width on all sides
{additional_logo_rules}

---

## Color System

### Primary Accent — {accent_name}

The signature brand color. Used for primary actions, links, highlights.

| Name | Hex | Use |
|------|-----|-----|
| {accent_name} | `#{accent}` | Primary buttons, links, highlights |
| {accent_name} Dark | `#{accent_dark}` | Hover states, outlines |
| {accent_name} Light | `#{accent_secondary}` | Secondary accents |

**Rule:** {accent_usage_rule}

### Theme Base

**{theme_name} Theme (Default)**

Background: #{background} Background Alt: #{background_alt} Surface: #{card_bg} Text Primary: #{text} Text Secondary: #{text_secondary}

{additional_color_notes}

---

## Typography

### Font Stack

- **Heading:** {heading_font} — {heading_description}
- **Body:** {body_font} — {body_description}
- **Code:** {code_font} — {code_description}

### Typography Rules

| Element | Font | Weight | Size |
|---------|------|--------|------|
| Display/Hero | {heading_font} | 700 | 36px+ |
| H1 | {heading_font} | 700 | 30px |
| H2 | {heading_font} | 600 | 24px |
| Body | {body_font} | 400 | 16-18px |
| Code | {code_font} | 400 | 14px |

### Text Color Usage

| Context | Color | Notes |
|---------|-------|-------|
| Headings | #{text} | Full contrast |
| Body | #{text_secondary} | Comfortable reading |
| Links | #{accent} | With hover effect |

---

## Spacing System

**Base unit:** 4px

| Token | Value | Use |
|-------|-------|-----|
| `xs` | 4px | Tight spacing, icon gaps |
| `sm` | 8px | Related elements |
| `base` | 16px | Standard padding |
| `lg` | 24px | Section padding |
| `xl` | 32px | Card padding |
| `2xl` | 48px | Section margins |

**Rule:** When in doubt, use multiples of 8px.

---

## Buttons

### Button Types

| Type | Background | Text | Use |
|------|------------|------|-----|
| Primary | #{accent} | White | Main actions, CTAs |
| Secondary | #{card_bg} | #{text} | Secondary actions |
| Ghost | Transparent | #{text} | Tertiary actions |

### Button Specs

- **Font:** {heading_font}, 500 weight
- **Border radius:** 8px
- **Padding:** 8px 16px (standard), 12px 24px (large)

---

## Signature Elements

{signature_elements_description}

{signature_element_1}

{signature_element_2}

{signature_element_3}

---

## Diagrams

### Color Palette for Diagrams

| Semantic Purpose | Fill | Stroke |
|------------------|------|--------|
| Primary/Neutral | `#{accent}` | `#{accent_dark}` |
| Secondary | `#{accent_secondary}` | `#{accent_dark}` |
| Start/Trigger | `#FED7AA` | `#C2410C` |
| End/Success | `#A7F3D0` | `#047857` |
| Warning/Decision | `#FEF3C7` | `#B45309` |
| Error/Stop | `#FECACA` | `#B91C1C` |

### Diagram Rules

- **Background:** {diagram_bg} for maximum readability
- **Text color:** {diagram_text}
- **Stroke width:** 2px
- **Rule:** Always pair darker stroke with lighter fill

---

## Quick Reference

### When to Use Primary Accent

| Use {accent_name} | Don't Use |
|-------------------|-----------|
{accent_usage_table}

### Font Usage

| {heading_font} | {body_font} |
|----------------|-------------|
{font_usage_table}

---

*Last updated: {date}*

---

Filling the Template

brand_tagline

One-line brand description. Example: "A complete design system for AI education content, community, and products."

principle_1/2/3_name and description

Core design principles. Examples:

• "Technical but Approachable" - "Complex topics made accessible without dumbing them down."
• "Clean over Flashy" - "No unnecessary decoration. Every visual element has a purpose."
• "Dark Mode by Default" - "Modern, developer-focused aesthetic."

logo_description

Brief description of the logo. Example: "A stylized blue flame/droplet shape — fluid, dynamic, and modern."

If no logo, write: "No logo configured. Add a logo to assets/logo.png when available."

accent_name

A name for the primary accent color. Example: "Dynamous Blue", "Brand Orange", "Primary"

accent/accent_dark/accent_secondary

Hex values without # prefix.

accent_usage_rule

How to use the accent color. Example: "Dynamous Blue is the hero. Use for actions and emphasis. Don't dilute by overusing."

theme_name

"Dark" or "Light" depending on the background color.

heading_description/body_description/code_description

Brief description of each font's role. Example: "Clean, modern sans-serif for all UI and body text"

signature_elements_description

Introduction to signature visual elements. Example: "These patterns define the Dynamous visual identity."

signature_element_1/2/3

Descriptions of unique visual patterns. Examples:

• Glass card effect with backdrop blur
• Gradient backgrounds
• Glow effects around primary elements

If no signature elements defined, suggest based on colors:

• For dark themes: glass effects, subtle glows
• For light themes: clean shadows, crisp borders

diagram_bg

Background color for diagrams. Dark brands usually use white (#FFFFFF) for diagram backgrounds. Light brands can match the brand background.

diagram_text

Text color for diagrams. Usually a dark color for readability.

accent_usage_table

Table rows showing when to use/not use accent.

font_usage_table

Table rows showing when to use each font.

date

Current date in YYYY-MM-DD format.

Color Presets

Quick color configurations for common brand themes.

---

Dark Themes

Midnight Blue (Developer-focused)

"colors": {
  "background": "07090F",
  "background_alt": "080A13",
  "text": "FAFAFA",
  "text_secondary": "CCCCCC",
  "accent": "3B82F6",
  "accent_secondary": "60A5FA",
  "accent_tertiary": "0EA5E9",
  "code_bg": "0A0C12",
  "card_bg": "0D1117",
  "card_bg_alt": "161B22"
}

Good for: Tech, developer tools, AI/ML content

Catppuccin Mocha (Soft Dark)

"colors": {
  "background": "1e1e2e",
  "background_alt": "181825",
  "text": "cdd6f4",
  "text_secondary": "bac2de",
  "accent": "fab387",
  "accent_secondary": "89b4fa",
  "accent_tertiary": "a6e3a1",
  "code_bg": "11111b",
  "card_bg": "313244",
  "card_bg_alt": "45475a"
}

Good for: Creative, design, softer aesthetic

Pure Dark (High Contrast)

"colors": {
  "background": "000000",
  "background_alt": "0a0a0a",
  "text": "ffffff",
  "text_secondary": "a3a3a3",
  "accent": "f97316",
  "accent_secondary": "fb923c",
  "accent_tertiary": "fbbf24",
  "code_bg": "0d0d0d",
  "card_bg": "171717",
  "card_bg_alt": "262626"
}

Good for: Bold statements, high-impact content

GitHub Dark

"colors": {
  "background": "0d1117",
  "background_alt": "010409",
  "text": "c9d1d9",
  "text_secondary": "8b949e",
  "accent": "58a6ff",
  "accent_secondary": "79c0ff",
  "accent_tertiary": "a5d6ff",
  "code_bg": "161b22",
  "card_bg": "21262d",
  "card_bg_alt": "30363d"
}

Good for: Open source, developer communities

---

Light Themes

Clean White

"colors": {
  "background": "ffffff",
  "background_alt": "f9fafb",
  "text": "111827",
  "text_secondary": "4b5563",
  "accent": "2563eb",
  "accent_secondary": "3b82f6",
  "accent_tertiary": "60a5fa",
  "code_bg": "f3f4f6",
  "card_bg": "f9fafb",
  "card_bg_alt": "f3f4f6"
}

Good for: Professional, corporate, documentation

Warm Paper

"colors": {
  "background": "fffbeb",
  "background_alt": "fef3c7",
  "text": "292524",
  "text_secondary": "57534e",
  "accent": "d97706",
  "accent_secondary": "f59e0b",
  "accent_tertiary": "fbbf24",
  "code_bg": "f5f5f4",
  "card_bg": "fafaf9",
  "card_bg_alt": "f5f5f4"
}

Good for: Content, publishing, creative writing

Cool Gray

"colors": {
  "background": "f8fafc",
  "background_alt": "f1f5f9",
  "text": "0f172a",
  "text_secondary": "475569",
  "accent": "0ea5e9",
  "accent_secondary": "38bdf8",
  "accent_tertiary": "7dd3fc",
  "code_bg": "e2e8f0",
  "card_bg": "f1f5f9",
  "card_bg_alt": "e2e8f0"
}

Good for: SaaS, modern apps, tech products

---

Accent Color Options

By Brand Personality

Complementary Pairs

---

Font Pairings

Developer-Focused

• Heading: JetBrains Mono
• Body: Inter
• Code: JetBrains Mono

Professional/Corporate

• Heading: Montserrat
• Body: Open Sans
• Code: Fira Code

Modern/Clean

• Heading: Inter
• Body: Inter
• Code: JetBrains Mono

Creative/Friendly

• Heading: Poppins
• Body: Lato
• Code: Monaco

Bold/Impact

• Heading: Montserrat (Black weight)
• Body: Source Sans Pro
• Code: Consolas

---

Quick Start Combos

"Developer Content Creator"

• Theme: Midnight Blue (dark)
• Accent: 3B82F6 (blue)
• Fonts: Inter / Inter / JetBrains Mono

"Modern SaaS"

• Theme: Cool Gray (light)
• Accent: 0EA5E9 (cyan)
• Fonts: Inter / Inter / Fira Code

"Bold Tech Influencer"

• Theme: Pure Dark
• Accent: F97316 (orange)
• Fonts: Montserrat / Inter / JetBrains Mono

"Professional Services"

• Theme: Clean White
• Accent: 2563EB (blue)
• Fonts: Montserrat / Open Sans / Fira Code

"Creative Studio"

• Theme: Catppuccin Mocha
• Accent: FAB387 (peach)
• Fonts: Poppins / Lato / JetBrains Mono

Tone of Voice Template

Use this template to generate the tone-of-voice.md file. Replace all {placeholder} values with gathered information.

---

# {brand_name} — Tone of Voice

> {voice_tagline}

---

## Voice Character

{voice_character_description}

---

## Core Attributes

### 1. {attribute_1_name}
{attribute_1_description}

### 2. {attribute_2_name}
{attribute_2_description}

### 3. {attribute_3_name}
{attribute_3_description}

---

## Voice Influences

{brand_name}'s voice draws from:

{voice_influences_description}

---

## Vocabulary Patterns

### Signature Words & Phrases
{vocabulary_patterns}

### Intensifiers
{intensifiers}

### Connectors & Transitions
{connectors}

---

## Writing Guidelines

### Do
{do_guidelines}

### Don't
{dont_guidelines}

---

## Sentence Patterns

### Opening Hooks
{opening_hooks}

### Explanations
{explanation_style}

### Transitions
{transition_style}

---

## Example Phrases

### Headlines
{headline_examples}

### CTAs
{cta_examples}

### Descriptions
{description_examples}

---

## Voice Test

Before publishing, ask:

1. Does this sound like {brand_name} explaining this to a smart colleague?
2. Are we using our signature vocabulary naturally (not forced)?
3. Are we being direct and confident, not hedging?
4. Would our audience feel "{audience_feeling}"?
5. Is there a sharper, shorter way to say this?

---

## Quick Reference

| Always | Never |
| ------ | ----- |
{quick_reference_table}

---

*Last updated: {date}*

---

Filling the Template

voice_tagline

A one-line description of how this brand sounds. Example: "How Cole Medin sounds across all content."

voice_character_description

2-3 sentences describing the brand personality. Example: "Cole's voice is genuinely excited about AI without tipping into hype. He teaches by showing iterations, admits when things don't work, and always grounds advice in what he's actually built."

attribute_1/2/3_name and description

Three core attributes that define the voice. Examples:

• "Confident" - "Takes positions and backs them up with experience. Doesn't hedge for politeness."
• "Practical" - "Leads with what to do, then explains why. Every piece of advice is actionable."
• "Honest" - "Admits limitations. Shows the messy middle, not just polished results."

voice_influences_description

If the user mentioned influences, describe how they combine. Example: "Dan Koe's calm confidence + Network Chuck's energy + ThePrimeagen's developer credibility = {brand_name}"

If no influences, describe the voice as a standalone character.

vocabulary_patterns

Specific words and phrases this brand uses. Format as a bulleted list.

intensifiers

Words used for emphasis. Example: "Super", "Really", "Incredibly", "Just"

connectors

Transition words and phrases. Example: "So", "And here's the thing", "But honestly"

do_guidelines

Bulleted list of positive writing guidance. Example:

• Use contractions naturally
• Be direct and confident
• Include specific numbers

dont_guidelines

Bulleted list of what to avoid. Example:

• Don't hedge with qualifiers
• Don't use corporate speak
• Don't overpromise

opening_hooks

Examples of how to start content. Format as bulleted examples.

explanation_style

How to explain complex topics.

transition_style

How to move between ideas.

headline_examples

3-5 example headlines in the brand's voice. Format as bulleted list with quotes.

cta_examples

3-5 example calls-to-action. Format as bulleted list with quotes.

description_examples

2-3 example description/body copy samples.

audience_feeling

How the audience should feel after consuming content. Example: "I can actually do this" or "Finally, someone who gets it"

quick_reference_table

Table rows of always/never pairs. Example: | Be direct | Hedge excessively | | Use specific numbers | Make vague claims | | Admit limitations | Overpromise |

date

Current date in YYYY-MM-DD format.

Voice Templates

Example voice configurations to help users discover their own voice.

---

Example 1: Technical Educator

Voice Character: Enthusiastic expert who teaches by showing, not telling. Admits limitations openly. Grounds everything in real experience.

Core Attributes: 1. Practical - Leads with action, theory second 2. Honest - Shows the messy middle, not just results 3. Energetic - Genuine excitement without hype

Vocabulary Patterns:

• "Super" as intensifier (super easy, super powerful)
• "Honestly" / "Here's the thing" for authenticity
• Contractions throughout (don't, can't, it's)
• "So" to start sentences frequently

Do:

• Use specific numbers and examples
• Show iterations, not just final results
• Admit when something doesn't work
• Address the audience directly ("you")

Don't:

• Overpromise or hype
• Use corporate speak
• Hedge with endless qualifiers
• Hide limitations

Example Headlines:

• "The Simple Strategy to 100x AI Coding"
• "Stop Vibe Coding. Start Building Systems."
• "What NOT to Focus On When Building AI Agents"

---

Example 2: Calm Authority

Voice Character: Confident and measured. Lets expertise speak through specifics, not claims. Philosophical grounding beneath practical advice.

Core Attributes: 1. Confident - Takes positions without hedging 2. Measured - No unnecessary exclamation points 3. Deep - Connects practical to philosophical

Vocabulary Patterns:

• Minimal intensifiers
• "The reality is..." for directness
• Complete sentences, few fragments
• Strategic use of "we" for inclusion

Do:

• Make complex ideas feel inevitable
• Support claims with reasoning
• Acknowledge nuance where real
• Use rhythm and pacing intentionally

Don't:

• Shout or oversell
• Use trendy buzzwords
• Rush through explanations
• Ignore counterarguments

Example Headlines:

• "Why Most AI Implementations Fail"
• "The Difference Between Tools and Systems"
• "A Framework for Thinking About Automation"

---

Example 3: Builder's Perspective

Voice Character: Developer-to-developer communication. Unfiltered opinions backed by code. Humor that's natural, not forced.

Core Attributes: 1. Credible - You've built this stuff 2. Direct - No corporate filter 3. Real - Willing to call out BS

Vocabulary Patterns:

• Technical terms used casually
• "Look" / "Listen" to start points
• Informal contractions and slang OK
• Self-deprecating humor where natural

Do:

• Reference actual code and systems
• Share real numbers and metrics
• Disagree when warranted
• Use humor naturally

Don't:

• Pretend to know what you don't
• Polish away the rough edges
• Avoid controversy artificially
• Talk down to the audience

Example Headlines:

• "I Rewrote Our Entire Backend in a Weekend"
• "This Architecture Pattern is Wrong. Here's Why."
• "Stop Over-Engineering Your AI Agents"

---

Example 4: Approachable Expert

Voice Character: Makes the complex accessible without dumbing it down. Inclusive language that assumes intelligence but not prior knowledge.

Core Attributes: 1. Inclusive - Anyone can learn this 2. Clear - Explains the "why" behind the "what" 3. Encouraging - Progress over perfection

Vocabulary Patterns:

• "Let's" for collaborative feeling
• "Think of it like..." for analogies
• Questions to guide thinking
• "The good news is..." for encouragement

Do:

• Use analogies and examples
• Break complex topics into steps
• Celebrate small wins
• Anticipate confusion points

Don't:

• Use jargon without explaining
• Assume prior knowledge
• Rush through fundamentals
• Make people feel dumb

Example Headlines:

• "A Gentle Introduction to AI Agents"
• "Understanding RAG: A Complete Guide"
• "You Don't Need to Be a PhD to Build AI"

---

Example 5: Contrarian Thinker

Voice Character: Challenges conventional wisdom with evidence. Not contrarian for engagement, but because you've seen what actually works.

Core Attributes: 1. Challenging - Questions assumptions 2. Evidence-based - Backs up disagreements 3. Constructive - Offers alternatives, not just criticism

Vocabulary Patterns:

• "Here's what actually works..."
• "The conventional wisdom is wrong about..."
• "I used to believe X, then I learned..."
• Data and specific examples to support

Do:

• Challenge popular ideas with evidence
• Provide alternative approaches
• Show your work
• Acknowledge when conventional wisdom IS right

Don't:

• Be contrarian for engagement
• Attack people instead of ideas
• Ignore legitimate counterpoints
• Overclaim your alternative

Example Headlines:

• "RAG is Not the Answer. Here's What Is."
• "Why I Stopped Using [Popular Tool]"
• "The Uncomfortable Truth About AI Agents"

---

Using These Templates

1. Mix and match - Most voices combine elements from multiple templates 2. Find your ratio - Maybe 50% Technical Educator + 30% Builder + 20% Calm Authority 3. Adapt, don't copy - These are starting points, not scripts 4. Let your natural voice come through - The template should enhance, not replace