brand-voice
关于
The brand-voice skill helps developers define and document a brand's complete writing personality, including voice attributes, tone shifts, and vocabulary rules. It is triggered for creating guidelines, auditing copy, or training AI on brand voice. Use it whenever a user needs to establish, refine, or enforce how a brand sounds in written content.
快速安装
Claude Code
推荐npx skills add rampstackco/claude-skills -a claude-code/plugin add https://github.com/rampstackco/claude-skillsgit clone https://github.com/rampstackco/claude-skills.git ~/.claude/skills/brand-voice在 Claude Code 中复制并粘贴此命令以安装该技能
技能文档
Brand Voice
Define how a brand sounds in writing. Document it in a way that anyone (writer, designer, founder, AI assistant) can apply it consistently.
This skill produces a standalone voice document that can either live in the brand style guide or feed into it.
When to use
- Defining brand voice for the first time
- Auditing existing copy for voice consistency
- Training a team, freelancer, or AI assistant on the brand voice
- Refining a voice that exists but is inconsistent across applications
- Adapting voice when a brand evolves (new audience, new positioning)
When NOT to use
- Writing specific copy (use
content-and-copy) - Brand visual identity work (use
brand-identity) - Documenting a complete brand system (use
brand-style-guide, which incorporates voice) - Initial brand exploration (use
brand-ideation)
Required inputs
- The brand and its positioning
- The audience and what they need to hear
- 5 to 10 examples of existing brand writing (if any)
- 3 to 5 reference brands whose voice resonates with where this brand should go
- Any voice attributes already specified in the brief
The framework: 4 layers
Voice has four layers, stacked. Each layer constrains the one below it.
Layer 1: Voice attributes
The constants. The personality traits that define how the brand sounds across every context.
Pick 3 to 5 attributes. Pair each with what it is NOT (the failure mode if overdone).
Common attribute pairings (NOT a menu - generate your own):
- Confident, not arrogant
- Direct, not blunt
- Warm, not saccharine
- Witty, not sarcastic
- Smart, not academic
- Honest, not harsh
- Playful, not silly
- Practical, not boring
- Bold, not loud
- Curious, not unfocused
The "not" half is what saves writers from overshooting. "Confident" alone produces swagger. "Confident, not arrogant" tells writers where the line is.
Layer 2: Tone shifts
Voice is constant. Tone adapts to context.
Map the major contexts the brand writes in. For each, document how voice expresses differently.
Common contexts:
| Context | Tone shift |
|---|---|
| Onboarding | Warmer, more enthusiastic, slightly slower pace |
| Hero / marketing | Confident, signature voice fully on |
| Product copy / UX | Direct, helpful, brief |
| Error messages | Calm, matter-of-fact, no apology theater |
| Success states | Brief celebration, redirect to next action |
| Empty states | Helpful, slightly playful, suggest action |
| 404 / not found | Self-aware, light, points the way home |
| Account deletion / cancellation | Quiet, respectful, no jokes |
| Pricing | Direct, transparent, confidence-inspiring |
| Legal / TOS | Plain language version sits next to the legal version |
| Support / help center | Patient, thorough, no condescension |
| Crisis communication | Calm, factual, accountable |
| Product announcements | Excited but not breathless |
| Email subject lines | Specific, never click-bait |
Voice stays consistent across all of these. Tone is what shifts.
Layer 3: Vocabulary and grammar
The granular dial settings.
Vocabulary preferences:
- Words and phrases the brand uses
- Words and phrases the brand avoids
- Words the brand has redefined (if any) - e.g., a SaaS product calling its features "huddles" instead of "meetings"
- Industry jargon: keep it (signals expertise) or strip it (signals approachability)
- Sentence-opening preferences (some brands lean on imperatives, some on questions, some on statements)
Grammar and style:
- Contractions (use them = casual, avoid them = formal)
- Sentence length default (short = punchy, medium = considered, long = literary)
- Punctuation marks favored or avoided (em dash is famously polarizing)
- Pronouns ("we" / "you" / "I")
- Capitalization style (title case, sentence case, all-lowercase deliberate)
- Number formatting (spell out under ten, or always digits)
- Oxford comma (use or skip)
- Active vs passive voice (most brands prefer active)
Layer 4: Examples and patterns
Voice is taught through examples, not rules. Build a library.
For each major content type, show:
- Bad example (off-voice)
- Good example (on-voice)
- Brief note on what changed
Common content types to cover:
- Headline
- Subheadline
- Hero CTA
- Feature description
- Testimonial intro
- Email subject line
- Email opening
- Push notification
- Error message
- Success message
- About page paragraph
- Social post
- Sales page paragraph
Aim for 15 to 25 paired examples. This is the most-used part of the voice doc in practice.
Workflow
- Audit existing copy if it exists. Identify what is on-brand, what is off, what patterns recur.
- Layer 1: Voice attributes. Generate 5 to 8 candidates with "we are X, not Y" framing. Pick 3 to 5.
- Layer 2: Tone shifts. List 8 to 15 contexts the brand writes in. Note the tone shift for each.
- Layer 3: Vocabulary and grammar. Define preferences. Skip default rules unless they actually distinguish the brand.
- Layer 4: Examples. Build the paired-example library. 15 to 25 minimum.
- Stress-test. Pick a fresh writing brief and apply the voice doc. Does it produce on-voice copy? If not, the doc is incomplete.
- Document. Use the template in
references/voice-document-template.md. - Distribute. Voice docs only work if they get used. Make the doc easy to reference inline (link to it from CMS templates, brief templates, AI assistant prompts).
Failure patterns
- Generic attributes ("friendly, professional, approachable"). Every brand says this. Means nothing. Pick attributes that genuinely distinguish.
- No "we are NOT" pairings. Without the rejection, attributes drift toward extremes.
- Voice doc with no examples. Rules without examples cannot be applied.
- Examples that are obviously bad and obviously good. Real voice work shows nuanced shifts, not cartoonish before/after.
- Skipping tone shifts. Treating voice as one-size-fits-all leads to a brand that sounds wrong in error states or legal contexts.
- Documenting aspirational voice. If the brand does not actually sound this way today and has no plan to shift, the doc is fiction.
- Voice without distribution. A perfect doc that no one references is worth nothing.
Output format
Default output is a markdown document at voice.md in the brand folder. Sections:
- Voice attributes (with we-are-not pairings)
- Tone shifts by context
- Vocabulary preferences
- Grammar and style rules
- Paired examples library (the most-used section)
- Anti-patterns (specific phrases or constructions to avoid)
- References (the brands and writers we are inspired by)
This doc can stand alone or feed into brand-style-guide.
Reference files
references/voice-document-template.md- Fillable template.references/voice-frameworks.md- Detailed walkthrough of the Nielsen Norman 4 dimensions, Jung archetypes, and the "we are X not Y" approach.
GitHub 仓库
相关推荐技能
brand-style-guide
其他该Skill用于创建或审核全面的品牌风格指南,涵盖品牌故事、标识系统、色彩、字体等完整体系。它适用于建立新品牌指南、记录现有品牌或审计现有指南完整性的场景,并能生成供团队长期参考的规范文档。当需要将已完成的品牌资产文档化并交接给设计师、开发人员或合作伙伴时,此Skill可被相关关键词触发使用。
brand-archetype-system
其他该Skill提供预设的品牌美学原型系统,帮助开发者快速启动品牌设计工作。当需要类似"像Stripe那样"的参考起点、从多个方向快速收敛或获取特定行业的可靠默认方案时,它可立即生成涵盖色彩、字体、版式、语调和图像方向的完整设计框架。其核心价值在于将设计需求映射到已知美学体系,避免从零开始设计。
logo-design
其他该Skill专门用于为品牌或组织生成多种生产级的Logo变体,涵盖文字标记、组合标志、独立符号等不同架构。它能提供设计原理、应用规格和可直接用于决策的演示方案,并特别关注从微小图标到大型标识等实际应用场景的生产规范。当开发者需要专注于Logo本身的设计、迭代或生产优化,而非完整的品牌系统时,应触发此Skill。
brand-identity
其他该Skill用于设计或评估品牌视觉识别系统,涵盖Logo、色彩、字体、图像、图标和动效。当开发者需要创建新品牌视觉资产或评估现有系统的一致性时即可触发使用。它能提供从概念到具体设计原则的完整指导,帮助将品牌方向转化为可执行的视觉方案。
