brand-voice
Framework for documenting, applying, and enforcing brand voice and style guidelines across marketing content.
- Covers seven core documentation areas: brand personality, voice attributes, audience awareness, messaging pillars, tone spectrum, style rules, and terminology management
- Includes practical templates for defining voice attributes with "we are / we are not" statements and tone adaptation tables across channels (blog, social, email, support) and situations (launches, incidents, bad news)
- Provides detailed style guide enforcement checklists for grammar, formatting, punctuation, and inclusive language rules
- Offers terminology management guidance including preferred terms, product naming conventions, jargon handling, and competitor framing strategies
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
More from anthropics/knowledge-work-plugins
data-visualization
Create effective data visualizations with Python (matplotlib, seaborn, plotly). Use when building charts, choosing the right chart type for a dataset, creating publication-quality figures, or applying design principles like accessibility and color theory.
6.4Kcode-review
Review code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection risks, missing edge cases, or error handling gaps.
4.2Ktask-management
Simple task management using a shared TASKS.md file. Reference this when the user asks about their tasks, wants to add/complete tasks, or needs help tracking commitments.
3.5Ksystem-design
Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.
3.3Kdocumentation
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
3.3Kmemory-management
Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.
3.3K