brand-voice

43
12
Source

Apply and enforce brand voice, style guide, and messaging pillars across content. Use when reviewing content for brand consistency, documenting a brand voice, adapting tone for different audiences, or checking terminology and style guide compliance.

Install

mkdir -p .claude/skills/brand-voice && curl -L -o skill.zip "https://mcp.directory/api/skills/download/905" && unzip -o skill.zip -d .claude/skills/brand-voice && rm skill.zip

Installs to .claude/skills/brand-voice

About this skill

Brand Voice Skill

Frameworks for documenting, applying, and enforcing brand voice and style guidelines across marketing content.

Brand Voice Documentation Framework

A complete brand voice document should cover these areas. Use this framework to help users define their brand voice or to understand an existing brand voice configuration.

1. Brand Personality

Define the brand as if it were a person. What are its defining traits?

Example: "If our brand were a person, they would be a knowledgeable colleague who explains complex things simply, celebrates your wins genuinely, and never talks down to you."

2. Voice Attributes

Select 3-5 attributes that define how the brand communicates. Each attribute should be defined with:

  • What it means in practice
  • What it does NOT mean (to prevent misinterpretation)
  • An example demonstrating the attribute

3. Audience Awareness

  • Who the brand is speaking to (primary and secondary audiences)
  • What the audience cares about
  • What level of expertise the audience has
  • How the audience expects to be addressed

4. Core Messaging Pillars

  • 3-5 key themes the brand consistently communicates
  • The hierarchy of these messages (which comes first)
  • How each pillar connects to audience needs

5. Tone Spectrum

How the voice adapts across contexts while remaining recognizably the same brand.

6. Style Rules

Specific grammar, formatting, and language rules. See the Style Guide Enforcement section below.

7. Terminology

Preferred and avoided terms. See the Terminology Management section below.

Voice Attributes

Common Voice Attribute Pairs

When defining brand voice, it helps to position attributes on a spectrum. Here are common attribute spectrums:

SpectrumOne EndOther End
FormalityFormal, institutionalCasual, conversational
AuthorityExpert, authoritativePeer-level, collaborative
EmotionWarm, empatheticDirect, matter-of-fact
ComplexityTechnical, preciseSimple, accessible
EnergyBold, energeticCalm, measured
HumorPlayful, wittySerious, earnest
InnovationCutting-edge, forward-lookingEstablished, proven

Defining an Attribute

For each chosen attribute, document it in this format:

[Attribute name]

  • We are: [what this means in practice]
  • We are not: [common misinterpretation to avoid]
  • This sounds like: [example sentence demonstrating the attribute]
  • This does NOT sound like: [example sentence violating the attribute]

Example:

Approachable

  • We are: friendly, clear, jargon-free, welcoming to beginners and experts alike
  • We are not: dumbed-down, overly casual, or lacking substance
  • This sounds like: "Here's how to get started — it takes about five minutes."
  • This does NOT sound like: "Yo! This is super easy, even a noob can do it lol."

Tone Adaptation Across Channels and Contexts

The brand voice stays consistent, but tone adapts to context. Tone is the emotional inflection applied to the voice.

Tone by Channel

ChannelTone AdaptationExample
BlogInformative, conversational, educational"Let's walk through how this works and why it matters for your team."
Social media (LinkedIn)Professional, thought-provoking, concise"Three things we learned from running 50 campaigns this quarter."
Social media (Twitter/X)Punchy, direct, sometimes witty"Your landing page has 3 seconds. Make them count."
Email marketingPersonal, helpful, action-oriented"We put together something we think you'll find useful."
Sales collateralConfident, benefit-driven, specific"Teams using our platform reduce reporting time by 40%."
Support/Help docsClear, patient, step-by-step"If you see this error, here's how to fix it."
Press releaseFormal, factual, newsworthy"The company today announced the launch of..."
Error messagesEmpathetic, helpful, blame-free"Something went wrong on our end. We're looking into it."

Tone by Situation

SituationTone Adaptation
Product launchExcited, confident, forward-looking
Incident or outageTransparent, empathetic, accountable
Customer success storyCelebratory, specific, crediting the customer
Thought leadershipAuthoritative, nuanced, evidence-based
OnboardingWelcoming, encouraging, clear
Bad news (price increase, deprecation)Honest, respectful, solution-oriented
Competitive comparisonConfident but fair, fact-based, not disparaging

Tone Adaptation Rule

The voice attributes remain fixed. Tone dials them up or down based on context. For example, if a brand is "bold and warm":

  • In a product launch, dial up boldness
  • In an incident response, dial up warmth
  • Neither attribute disappears; the balance shifts

Style Guide Enforcement

Grammar and Mechanics

Document and enforce these choices consistently:

RuleOptionsExample
Oxford commaYes / No"fast, reliable, and secure" vs. "fast, reliable and secure"
Sentence case vs. title case (headings)Sentence / Title"How to get started" vs. "How to Get Started"
ContractionsUse / Avoid"we're" vs. "we are"
Em dash spacingNo spaces / Spaces"this—and more" vs. "this — and more"
NumbersSpell out 1-9, numerals 10+ / Always numerals"five features" vs. "5 features"
Percent% / percent"50%" vs. "50 percent"
Date formatMonth DD, YYYY / DD/MM/YYYY / etc."January 15, 2025"
Time format12-hour / 24-hour"3:00 PM" vs. "15:00"
ListsPeriods / No periods on fragments"Set up your account." vs. "Set up your account"

Formatting Conventions

  • Heading hierarchy (when to use H1, H2, H3)
  • Bold and italic usage (bold for emphasis, italic for titles/terms)
  • Link text (descriptive vs. "click here" — always descriptive)
  • Image alt text requirements
  • Code formatting (for technical brands)
  • Callout or highlight box usage

Punctuation and Emphasis

  • Exclamation mark policy (limited use, never more than one)
  • Ellipsis usage (avoid in most professional contexts)
  • ALL CAPS policy (avoid; use bold for emphasis instead)
  • Emoji usage by channel (professional channels: minimal or none; social: where appropriate)

Terminology Management

Preferred Terms

Maintain a list of preferred terms and their incorrect alternatives:

Use ThisNot ThisNotes
sign up (verb)signup (verb)"signup" is the noun form
log in (verb)login (verb)"login" is the noun/adjective form
set up (verb)setup (verb)"setup" is the noun/adjective form
emaile-mailNo hyphen
websiteweb siteOne word
data is (singular)data areUnless the publication requires plural

Product and Feature Names

  • Official capitalization for product names
  • When to use the full product name vs. shorthand
  • Whether to use "the" before product names
  • How to handle versioning in copy
  • Trademark and registration symbols (when required and when to omit)

Inclusive Language

  • Use gender-neutral language (they/them for unknown individuals)
  • Avoid ableist language ("crazy", "blind spot", "lame")
  • Use person-first language where appropriate
  • Avoid culturally specific idioms that may not translate
  • Use "simple" or "straightforward" instead of "easy" (what is easy varies by person)

Industry Jargon Management

  • Define which technical terms the audience understands without explanation
  • List jargon that should always be defined or replaced with plain language
  • Specify which acronyms need to be spelled out on first use
  • Audience-specific glossary for terms that mean different things to different readers

Competitor and Category Terms

  • How to refer to your product category (use your preferred framing)
  • How to refer to competitors (by name or generically)
  • Terms competitors have coined that you should avoid (to prevent reinforcing their positioning)
  • Your preferred differentiation language

More by anthropics

View all →

frontend-design

anthropics

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

12381

mcp-builder

anthropics

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

12843

skill-creator

anthropics

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

12126

webapp-testing

anthropics

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

11320

xlsx

anthropics

Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify existing spreadsheets while preserving formulas, (4) Data analysis and visualization in spreadsheets, or (5) Recalculating formulas

10216

pptx

anthropics

Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks

12915

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

286790

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

213415

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

211295

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

218234

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

171200

rust-coding-skill

UtakataKyosui

Guides Claude in writing idiomatic, efficient, well-structured Rust code using proper data modeling, traits, impl organization, macros, and build-speed best practices.

165173

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.