Skip to content

rampstackco/claude-skills / skills/brand-voice

brand-voice

Verified

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. On a voice consistency check, this skill owns defining and documenting the voice system; use `editorial-qa` when a specific draft needs checking against an existing system before it publishes.

FileKindSize
README.mdmarkdown1.1 KB
SKILL.mdskill md8.7 KB
references/voice-document-template.mdmarkdown5.5 KB
references/voice-frameworks.mdmarkdown7.5 KB

references/voice-document-template.md

View on GitHub
# [Brand Name] Voice and Tone

**Version:** [X.Y]
**Last updated:** [YYYY-MM-DD]
**Maintained by:** [Team or person]

---

## How to use this doc

[1 to 2 paragraphs. Who this is for, when to reference it, where to ask questions.]

For most writers, the section that gets used most is the **paired examples library** at the end. When unsure how to write something, find the closest example and pattern-match.

---

## Voice attributes

We sound:

- **[Adjective 1]**, not [opposite]
- **[Adjective 2]**, not [opposite]
- **[Adjective 3]**, not [opposite]
- **[Adjective 4]**, not [opposite]
- **[Adjective 5]**, not [opposite]

### What each attribute means

**[Adjective 1]**
[2 to 3 sentences. What this looks like in practice. Include one specific example phrase.]
Failure mode: when [Adjective 1] tips into [opposite], we sound [bad outcome].

**[Adjective 2]**
[Same structure.]

**[Adjective 3]**
[Same structure.]

**[Adjective 4]**
[Same structure.]

**[Adjective 5]**
[Same structure.]

---

## Tone shifts by context

Voice stays constant. Tone adjusts based on what the user is doing and feeling.

| Context | Tone |
|---|---|
| Hero / marketing | [How tone shifts] |
| Onboarding | [How tone shifts] |
| Product copy / UX labels | [How tone shifts] |
| Empty states | [How tone shifts] |
| Error messages | [How tone shifts] |
| Success states | [How tone shifts] |
| 404 / not found | [How tone shifts] |
| Account deletion / cancellation | [How tone shifts] |
| Pricing | [How tone shifts] |
| Legal / TOS | [How tone shifts] |
| Support / help center | [How tone shifts] |
| Crisis communication | [How tone shifts] |
| Email subject lines | [How tone shifts] |
| Social posts | [How tone shifts] |

---

## Vocabulary preferences

### Words and phrases we use

[Bulleted list of vocabulary that fits the brand. Be specific.]

- [Word or phrase]
- [Word or phrase]
- [Word or phrase]

### Words and phrases we avoid

[Bulleted list of vocabulary that does not fit. Often these are category cliches or fluff words.]

- [Word or phrase] - [optional note on why]
- [Word or phrase]
- [Word or phrase]

### Redefined words (if any)

If the brand uses standard words in non-standard ways, document here.

| Standard term | We say | Why |
|---|---|---|
| [Standard] | [Our term] | [Reasoning] |

### Industry jargon

We [keep / strip] industry jargon. [1 to 2 sentences explaining the call.]

---

## Grammar and style

| Decision | Our standard |
|---|---|
| Contractions | [Use / avoid] |
| Default sentence length | [Short / medium / long] |
| Em dashes | [Use / avoid] |
| Oxford comma | [Yes / no] |
| Pronouns | [we / you / I patterns] |
| Capitalization (headlines) | [Title / sentence / lowercase] |
| Numbers under 10 | [Spell out / digits] |
| Active vs passive | [Active default] |
| Hashtags (in social) | [In body / in comment / not used] |
| Exclamation points | [Frequency rule] |
| Emoji | [Use / avoid / context-specific] |

---

## Paired examples library

The most-used part of this doc. When in doubt, find the closest example and pattern-match.

### Headlines

**Off-voice:**
> [Bad example]

**On-voice:**
> [Good example]

[Brief note on what changed and why.]

---

### Subheadlines

**Off-voice:**
> [Bad example]

**On-voice:**
> [Good example]

---

### Hero CTA

**Off-voice:**
> [Bad example]

**On-voice:**
> [Good example]

---

### Feature description

**Off-voice:**
> [Bad example, 2 to 3 sentences]

**On-voice:**
> [Good example, 2 to 3 sentences]

---

### Testimonial intro

**Off-voice:**
> [Bad example]

**On-voice:**
> [Good example]

---

### Email subject line

**Off-voice:**
> [Bad example]

**On-voice:**
> [Good example]

---

### Email opening

**Off-voice:**
> [Bad example]

**On-voice:**
> [Good example]

---

### Push notification

**Off-voice:**
> [Bad example]

**On-voice:**
> [Good example]

---

### Error message

**Off-voice:**
> "An error has occurred. Please try again later."

**On-voice:**
> [Good example specific to this brand]

---

### Success message

**Off-voice:**
> [Bad example]

**On-voice:**
> [Good example]

---

### Empty state

**Off-voice:**
> "No items found."

**On-voice:**
> [Good example specific to this brand]

---

### About page paragraph

**Off-voice:**
> [Bad example]

**On-voice:**
> [Good example]

---

### Social post

**Off-voice:**
> [Bad example]

**On-voice:**
> [Good example]

---

### Sales page paragraph

**Off-voice:**
> [Bad example]

**On-voice:**
> [Good example]

---

### 404 page

**Off-voice:**
> "404. Page not found."

**On-voice:**
> [Good example specific to this brand]

---

### Cancellation flow copy

**Off-voice:**
> [Bad example]

**On-voice:**
> [Good example]

---

## Anti-patterns

Specific phrases or constructions that NEVER appear in our writing:

- [Anti-pattern, with a brief example]
- [Anti-pattern, with a brief example]
- [Anti-pattern, with a brief example]

---

## References

Brands and writers whose voice we admire and learn from:

- **[Brand or writer]** - [What we learn from them]
- **[Brand or writer]** - [What we learn from them]
- **[Brand or writer]** - [What we learn from them]

We are not copying these voices. We are calibrating against them.

---

## Version history

| Version | Date | Changes |
|---|---|---|
| 1.0 | YYYY-MM-DD | Initial publication |

---

## How to evolve this doc

[1 paragraph on how the team proposes voice updates, who reviews, who approves.]

Voice should be reviewed:
- Annually as a minimum
- After any major audience shift
- After any major positioning change
- When it consistently fails the "stress test" (writing produced from this doc no longer feels right)
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall