MCP HubMCP Hub
스킬 목록으로 돌아가기

brand-voice

rampstackco
업데이트됨 6 days ago
322
42
322
GitHub에서 보기
기타wordaidesign

정보

이 스킬은 개발자들이 속성, 어조 변화, 어휘, 예시를 포함한 완전한 브랜드 보이스 시스템을 정의하고 문서화하는 데 도움을 줍니다. 가이드라인 작성, 카피 일관성 감사, 브랜드 개성에 대한 AI 교육을 위해 트리거됩니다. 사용자가 브랜드의 글쓰기 방향을 수립해야 하거나 기존 카피가 어색한 이유를 진단할 필요가 있을 때마다 활용하세요.

빠른 설치

Claude Code

추천
기본
npx skills add rampstackco/claude-skills -a claude-code
플러그인 명령대체
/plugin add https://github.com/rampstackco/claude-skills
Git 클론대체
git 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:

ContextTone shift
OnboardingWarmer, more enthusiastic, slightly slower pace
Hero / marketingConfident, signature voice fully on
Product copy / UXDirect, helpful, brief
Error messagesCalm, matter-of-fact, no apology theater
Success statesBrief celebration, redirect to next action
Empty statesHelpful, slightly playful, suggest action
404 / not foundSelf-aware, light, points the way home
Account deletion / cancellationQuiet, respectful, no jokes
PricingDirect, transparent, confidence-inspiring
Legal / TOSPlain language version sits next to the legal version
Support / help centerPatient, thorough, no condescension
Crisis communicationCalm, factual, accountable
Product announcementsExcited but not breathless
Email subject linesSpecific, 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

GitHub 저장소

rampstackco/claude-skills
경로: dist/pi/.agents/skills/brand-voice
0
agent-skillsai-agentsanthropicclaudeclaude-aiclaude-code

연관 스킬

brand-style-guide

기타

이 Claude Skill은 개발자가 로고, 색상, 타이포그래피, 보이스를 포함한 전체 시스템을 문서화하는 포괄적인 브랜드 스타일 가이드를 제작하거나 감사하는 데 도움을 줍니다. 브랜드 북을 구축해야 할 때, 기존 가이드라인을 검토할 때, 또는 인계용 지속적인 참조 자료를 생성할 때 작동합니다. 이를 사용하여 팀과 협력사 간 일관된 브랜드 적용을 보장하는 표준 문서를 생성하세요.

스킬 보기

brand-voice

기타

브랜드 보이스 스킬은 개발자가 브랜드의 전체적인 글쓰기 개성을 정의하고 문서화하는 데 도움을 줍니다. 여기에는 보이스 속성, 어조 변화, 어휘 규칙 등이 포함됩니다. 이 스킬은 가이드라인 작성, 카피 감사, 또는 브랜드 보이스에 대한 AI 훈련 시에 트리거됩니다. 사용자가 브랜드의 글쓰기 방식과 어조를 수립, 정제 또는 적용해야 할 때마다 활용하세요.

스킬 보기

brand-identity

기타

이 스킬은 로고, 색상, 타이포그래피, 이미지를 포함한 완전한 브랜드 시각 정체성 시스템을 설계하거나 평가하는 데 도움을 줍니다. 사용자가 이러한 시각적 요소를 새로 만들거나 기존 시스템의 일관성을 평가해야 할 때 작동합니다. 색상 팔레트 구축, 타이포그래피 선택, 로고 시스템 개발과 같은 작업에 활용하세요.

스킬 보기

brand-ideation

기타

이 스킬은 브랜드 개발의 초기 창의적 과정을 지원하며, 이름, 포지셔닝, 무드 방향과 같은 컨셉을 생성하고 다듬는 데 도움을 줍니다. 초기 탐색, 브레인스토밍, 또는 여러 개의 미완성 아이디어를 일관된 방향으로 수렴할 때 작동합니다. 개발자는 브랜드 네이밍, 포지셔닝 영역 설정, 내러티브 각도 창출과 관련된 작업을 지원하는 데 이 스킬을 사용해야 합니다.

스킬 보기