brand-voice

GitHub

定义品牌语调系统,包括属性、语境语气转换及写作规范。用于创建或审计品牌声音指南,确保文案一致性,指导团队或AI助手统一输出风格。

skills/brand-voice/SKILL.md rampstackco/claude-skills

Trigger Scenarios

定义品牌语调 审计现有文案的一致性 培训团队或AI使用品牌声音 用户感觉文案‘不对劲’且源于语调问题

Install

npx skills add rampstackco/claude-skills --skill brand-voice -g -y
More Options

Use without installing

npx skills use rampstackco/claude-skills@brand-voice

指定 Agent (Claude Code)

npx skills add rampstackco/claude-skills --skill brand-voice -a claude-code -g -y

安装 repo 全部 skill

npx skills add rampstackco/claude-skills --all -g -y

预览 repo 内 skill

npx skills add rampstackco/claude-skills --list

SKILL.md

Frontmatter
{
    "name": "brand-voice",
    "category": "brand",
    "description": "Develop or document a complete brand voice and tone system covering voice attributes, tone shifts by context, vocabulary preferences, grammar rules, and copy examples. Use this skill whenever the user wants to define how a brand sounds, write a voice and tone document, audit existing copy for voice consistency, train a team or AI assistant on brand voice, or refine the personality of brand writing. Triggers on brand voice, voice and tone, tone of voice, writing voice, brand personality, copy voice, voice document, voice guidelines, how should we write, voice training, voice audit. Also triggers when the user has copy that 'feels off' and the underlying issue is voice, even if not stated explicitly.",
    "display_order": 4,
    "catalog_summary": "Voice attributes, tone shifts, vocabulary, paired-example library"
}

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

  1. Audit existing copy if it exists. Identify what is on-brand, what is off, what patterns recur.
  2. Layer 1: Voice attributes. Generate 5 to 8 candidates with "we are X, not Y" framing. Pick 3 to 5.
  3. Layer 2: Tone shifts. List 8 to 15 contexts the brand writes in. Note the tone shift for each.
  4. Layer 3: Vocabulary and grammar. Define preferences. Skip default rules unless they actually distinguish the brand.
  5. Layer 4: Examples. Build the paired-example library. 15 to 25 minimum.
  6. Stress-test. Pick a fresh writing brief and apply the voice doc. Does it produce on-voice copy? If not, the doc is incomplete.
  7. Document. Use the template in references/voice-document-template.md.
  8. 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:

  1. Voice attributes (with we-are-not pairings)
  2. Tone shifts by context
  3. Vocabulary preferences
  4. Grammar and style rules
  5. Paired examples library (the most-used section)
  6. Anti-patterns (specific phrases or constructions to avoid)
  7. References (the brands and writers we are inspired by)

This doc can stand alone or feed into brand-style-guide.


Reference files

Version History

  • f1bc195 Current 2026-07-06 00:12

Same Skill Collection

skills/domain-strategy/SKILL.md
skills/email-deliverability/SKILL.md
skills/experiment-design/SKILL.md
skills/experimentation-analytics/SKILL.md
skills/feature-flagging/SKILL.md
skills/monitoring-and-alerting/SKILL.md
skills/seo-audit-orchestration/SKILL.md
skills/vendor-evaluation/SKILL.md
skills/accessibility-audit/SKILL.md
skills/ads-creative-development/SKILL.md
skills/ads-performance-analytics/SKILL.md
skills/after-action-report/SKILL.md
skills/ai-content-collaboration/SKILL.md
skills/analytics-strategy/SKILL.md
skills/art-direction/SKILL.md
skills/backup-and-disaster-recovery/SKILL.md
skills/beta-program-management/SKILL.md
skills/brand-archetype-system/SKILL.md
skills/brand-discovery/SKILL.md
skills/brand-ideation/SKILL.md
skills/brand-identity/SKILL.md
skills/brand-style-guide/SKILL.md
skills/calculator-design/SKILL.md
skills/chatbot-flow-design/SKILL.md
skills/code-review-web/SKILL.md
skills/comparison-tool-design/SKILL.md
skills/competitor-experience-audit/SKILL.md
skills/content-and-copy/SKILL.md
skills/content-brief-authoring/SKILL.md
skills/content-distribution/SKILL.md
skills/content-migration/SKILL.md
skills/content-refresh-system/SKILL.md
skills/content-repurposing/SKILL.md
skills/content-strategy/SKILL.md
skills/cost-optimization/SKILL.md
skills/creative-brief-selector/SKILL.md
skills/creative-brief/SKILL.md
skills/creative-direction/SKILL.md
skills/cro-optimization/SKILL.md
skills/data-warehouse-experimentation/SKILL.md
skills/dependency-management/SKILL.md
skills/design-standards/SKILL.md
skills/design-system/SKILL.md
skills/discovery-research-synthesis/SKILL.md
skills/documentation-strategy/SKILL.md
skills/editorial-qa/SKILL.md
skills/email-sequences/SKILL.md
skills/evidence-based-reviews/SKILL.md
skills/experimentation-platform-orchestrator/SKILL.md

Metadata

Files
0
Version
e42ec5a
Hash
b9fdadbc
Indexed
2026-07-06 00:12

trang chủ - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-08-05 01:36
浙ICP备14020137号-1 $bản đồ khách truy cập$