Skip to content

The-AI-Directory-Company/agents-and-skills / skills/brand-guidelines

brand-guidelines

Verified

Create brand guidelines documents — defining logo usage, color palettes, typography, voice/tone, imagery style, and application rules that maintain brand consistency across all touchpoints.

references/voice-tone-patterns.md

View on GitHub
# Voice and Tone Patterns

## "We Say / We Don't Say" Pattern Library

Use this table as a living reference. Add entries whenever new copy patterns emerge.

| Context | We Say | We Don't Say | Why |
|---|---|---|---|
| Encouraging action | "Get started" | "Submit" | Active and inviting vs. bureaucratic |
| Describing ease | "Takes about 2 minutes" | "Quick and easy!" | Specific beats vague enthusiasm |
| Acknowledging limits | "We don't support X yet" | "Unfortunately, X is not available" | Direct without over-apologizing |
| Explaining errors | "That email is already registered. Try signing in." | "Error: duplicate entry" | Guides the user instead of reporting a database state |
| Referring to users | "You" / "Your team" | "The user" / "One" | Second person is warmer and clearer |
| Talking about competitors | "We take a different approach" | "Unlike [Competitor], we actually..." | Confident without attacking |
| Announcing features | "You can now..." | "We're thrilled to announce..." | Focuses on user benefit, not company excitement |
| Admitting mistakes | "We got this wrong. Here's what we're doing about it." | "We apologize for any inconvenience" | Takes ownership instead of hiding behind formality |

## Tone-by-Context Matrix

Voice stays constant. Tone shifts based on the emotional stakes and user state.

| Context | Energy Level | Formality | Empathy Level | Example |
|---|---|---|---|---|
| Onboarding | High | Low | Medium | "Welcome! Let's set up your first project." |
| Marketing landing page | High | Low-Medium | Low | "Ship faster with confidence." |
| Documentation | Neutral | Medium | Low | "Run `npm install` to add the package." |
| Error / failure state | Low | Medium | High | "Something went wrong saving your file. Your changes are safe locally — try again in a moment." |
| Destructive action confirmation | Low | High | High | "This will permanently delete 12 projects. This cannot be undone." |
| Security / compliance | Low | High | Medium | "Your data is encrypted at rest and in transit." |
| Changelog / release notes | Medium | Medium | Low | "You can now export dashboards as PDF." |
| Crisis communication | Low | High | High | "On March 5 at 14:00 UTC, a database failure caused 23 minutes of downtime. Here is what happened and what we've changed." |
| Internal team communication | Medium | Low | Medium | "Heads up — we're changing the deploy flow next sprint." |
| Sales / proposals | Medium-High | Medium-High | Medium | "Here's how we'd approach your migration." |

## Common Voice Anti-Patterns

### 1. The Hype Machine
**Problem**: Every sentence uses superlatives and exclamation marks.
**Example**: "Our AMAZING new feature is here! You'll LOVE it!!!"
**Fix**: State what changed and why it matters. "You can now bulk-export reports as CSV — no more exporting one at a time."

### 2. The Apology Loop
**Problem**: Over-apologizing for normal product behavior.
**Example**: "Sorry, but you'll need to verify your email before continuing."
**Fix**: Frame requirements as steps, not impositions. "Verify your email to continue — check your inbox for a code."

### 3. The Robot
**Problem**: Copy reads like a system log.
**Example**: "Operation completed successfully. 14 records processed."
**Fix**: Write for a human. "Done — 14 contacts imported."

### 4. The Jargon Wall
**Problem**: Using internal or technical terms the audience does not understand.
**Example**: "Your webhook payload failed schema validation."
**Fix**: Translate to user language. "The data we received didn't match the expected format. Check the field names in your request."

### 5. The Hedger
**Problem**: Softening every statement to avoid commitment.
**Example**: "This might potentially help improve your workflow somewhat."
**Fix**: Be direct. "This cuts your export time from 5 minutes to 30 seconds."

### 6. The Passive Voice Abuser
**Problem**: Hiding agency behind passive constructions.
**Example**: "Your account has been suspended."
**Fix**: State who did what. "We suspended your account because of repeated policy violations. Here's how to appeal."

## How to Use This Reference

1. When writing new copy, scan the "We Say / We Don't Say" table for applicable patterns.
2. Identify the context from the tone matrix, then match energy, formality, and empathy levels.
3. Review drafts against the anti-patterns list — if a draft matches any pattern, rewrite.
4. Add new entries to the table as the brand voice evolves. This is a living document.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall