ssheleg/super-ux / plugins/super-ux/skills/brand-voice
brand-voice
VerifiedUse when defining or checking how a product speaks: tone of voice, terminology, canonical facts, register. Triggers: "tone of voice" / "тон оф войс", "brand voice" / "голос бренда", "брендбук", "наша терминология". Not for writing the text (copywriting). Refusal phrase "no brand" / «без бренда».
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.8 KB |
| references/ai-tells.md | markdown | 20.6 KB |
| references/brand-contract.md | markdown | 25.4 KB |
| references/channel-playbooks.md | markdown | 20.0 KB |
| references/hooks.md | markdown | 26.4 KB |
| references/localization.md | markdown | 5.2 KB |
| references/marketing-copy.md | markdown | 8.1 KB |
| references/research-outliers.md | markdown | 5.4 KB |
| references/seo-aeo-safety.md | markdown | 9.9 KB |
| references/store-copy.md | markdown | 7.4 KB |
| references/surface-registers.md | markdown | 9.1 KB |
| references/system-map.md | markdown | 12.4 KB |
| references/video-script.md | markdown | 14.6 KB |
| references/voice-packs.md | markdown | 15.9 KB |
| templates/brand/README.md | markdown | 2.3 KB |
| templates/brand/channels.md | markdown | 4.2 KB |
| templates/brand/copy-brief.md | markdown | 187 B |
| templates/brand/facts.md | markdown | 1.3 KB |
| templates/brand/locale.md | markdown | 2.2 KB |
| templates/brand/strings.md | markdown | 1.7 KB |
| templates/brand/terminology.md | markdown | 1.2 KB |
| templates/brand/voice.md | markdown | 2.2 KB |
references/surface-registers.md
View on GitHub# Surface registers: one voice, many surfaces
A product has **one** voice and roughly two dozen surfaces. The mistake this
reference exists to prevent is solving that with two dozen voices, which is
how a product ends up reading like three different companies, and is the
verbal twin of the visual drift a style pack prevents.
## Contents
- [The model](#the-model)
- [Rule 1: a register moves the axes, never the invariants](#rule-1-a-register-moves-the-axes-never-the-invariants)
- [Rule 2: platform physics and brand choice are different fields](#rule-2-platform-physics-and-brand-choice-are-different-fields)
- [Rule 3: humor is forbidden where the user is losing something](#rule-3-humor-is-forbidden-where-the-user-is-losing-something)
- [Product surfaces](#product-surfaces)
- [Marketing surfaces](#marketing-surfaces)
Field names and the surface list come from
[brand-contract.md](brand-contract.md). The axes being shifted are the five
fixed axes in `voice.md`, filled by a pack from
[voice-packs.md](voice-packs.md).
## The model
A **register** is the voice with per-axis deltas applied. Nothing else
changes: the vocabulary in `terminology.md`, the numbers in `facts.md`, and
the invariants declared in `voice.md` hold on every surface.
```
voice.md axes + invariants (one per product)
│
└── channels.md register = axes ± deltas (one record per surface)
```
Deltas are written as signed steps on named axes: `humor -2, density +1`.
A step is a perceptible shift, not a percentage. Three steps in either
direction is the practical range before the voice stops being recognisable.
## Rule 1: a register moves the axes, never the invariants
`voice.md` lists what is invariant. A Reddit post may run long, drop the CTA,
and turn self-deprecating; if the brand does not hedge, it does not hedge
there either.
This is the rule that keeps per-surface freedom from becoming per-surface
improvisation. When a surface seems to need an invariant broken, the answer
is one of two things, and neither is breaking it quietly: the invariant was
wrong and `voice.md` changes for the whole product, or the surface is wrong
for this product and is not used. Both are decisions with an owner.
## Rule 2: platform physics and brand choice are different fields
"A link in the post body suppresses reach" is a fact about an algorithm.
"We do not post links" is a decision someone made. Written on one line they
become indistinguishable within a quarter, and then nobody can tell which one
is safe to revisit when the platform changes its ranking.
So `Forbidden:` always carries both halves, and one of them may be `none`:
```
Forbidden: physics: link in body, max 5 hashtags, fold 125, one ask
| brand: no engagement bait, no fake urgency
```
The linter enforces the physics half (`B040`, `B042`, `B043`, `B045`,
`B046`) because it is mechanical; the tokens it reads are listed in the brand
contract. The brand half is judged by the `copy` audit scope, because it is
a decision.
## Rule 3: humor is forbidden where the user is losing something
On `error`, `destructive confirm`, `billing and receipts` and
`paywall and upgrade`, humor, exclamation marks and emoji are banned in every
pack, `playful-consumer` included. The user is losing data, access or money
at that moment, and levity reads as mockery of a loss the product caused.
This is `B061` and it blocks. It is not a register delta, because a delta is
negotiable and this is not.
---
## Product surfaces
The register notes below are defaults. A pack's own `Register deltas` field
overrides them where the two disagree, and the project's `channels.md`
overrides both.
### primary action
The button that carries the screen. Verb phrase naming the outcome, not the
mechanism: `Publish`, not `Submit`. One action keeps one name across the
whole flow: button `Publish`, toast `Published`, history entry `Published`.
Two names for one action is `B020` and it is the single most common copy
defect in a product built screen by screen.
### empty state
Teaches, never apologises. Three jobs in order: what belongs here, why it is
worth putting there, and the one action that starts it. An empty state that
only says "Nothing here yet" wastes the highest-attention moment a feature
gets.
Register: humor unchanged. This is where a warm pack earns its keep.
### error
Three facts, in this order: what happened, what was **not** affected, and the
one next step. The middle one is the one products skip and users need most:
"your draft was saved" turns a failure into an interruption.
Never blame the user, never say "unexpected", never show a code without a
sentence. Register: humor −3, density +1, distance −1.
### loading
If it is under 400ms, say nothing. If it is longer, say what is happening in
the product's own words. If it is longer than about ten seconds, say what the
user can do meanwhile, and never let the copy claim progress the system
cannot observe.
### success / toast
The past tense of the action's own verb, and nothing else. `Published.` A
toast is not a place for a sentence.
### onboarding
Density −1 from base for every pack. Terseness that reads as confident to an
expert reads as withholding to someone on their first screen. Name the
first-value moment in the user's terms and get there; explain the model only
where the next step is impossible without it.
### paywall and upgrade
Say what is being sold, what it costs, what happens at the end of the term,
and how to leave. Humor −3, absolute. A joke while asking for money reads as
a trick, and the read is not unfair.
### destructive confirm
Name the object, the consequence, and whether it is reversible. `Delete
project "Atlas" and its 340 files. This cannot be undone.` The confirming
verb matches the destructive verb: `Delete`, never `OK`. Humor −3.
### billing and receipts
Numbers, dates, and what happens next. Every figure traceable to `facts.md`
or to the account itself. Humor −3.
### settings and legal
Labels label, help text explains, examples demonstrate. One job per string.
Plain language applies to legal text too: a consent notice nobody understands
is not consent.
### transactional email and push
One purpose per message, named in the first line. Push has no room for a
register: state the fact and the object. A notification that says "Something
happened" is a notification that gets disabled.
### docs and help
Humor −2, density −1. Ground a term before leaning on it; see the grounding
model in [marketing-copy.md](marketing-copy.md). The reader is here because
something did not work; every sentence either moves them forward or is cut.
---
## Marketing surfaces
Per-platform mechanics (limits, what suppresses reach, what each surface
rewards) live in [channel-playbooks.md](channel-playbooks.md). This section
covers only the register.
### landing hero
The one surface where every pack drops density by a step: the reader has not
opted in yet. One claim, checkable, in the reader's own words. Confidence +1.
### landing body
Base register. One idea per section, each advancing a single argument.
### pricing
Density +1 and confidence +1 in every pack. Anxiety here is about choosing
wrong, not about the number: make the recommended plan obvious and say what
happens at the boundary between plans.
### blog
Distance −1, density −1. Long enough to ground its terms, and no longer.
### changelog
Distance −1, humor +1 where the pack allows. Users who read changelogs are
the ones who stayed; write to them as such. Every entry says what changed for
the reader, not which module was refactored.
### X
Density +1, distance −1. One idea per post; the first line decides whether
the rest is read.
### Instagram, TikTok and YouTube Shorts
Distance −1. The caption under the video: the first line is the window the
feed shows, so it carries the hook or the context, never a tag. One ask,
spoken in the video as well as written.
### short video
Distance −1, density +1, confidence +1. Spoken, so written for the ear: short
sentences, one idea per beat, figures said aloud. The on-screen text and the
spoken line are two sentences about one thing. Craft is in the `copywriting`
skill's `video-script.md` and `hooks.md`.
### Reddit
Distance −2, humor +1, CTA dropped entirely. The register that works
elsewhere reads as marketing intrusion here. A post that would work unchanged
on the landing page should not be posted.
### LinkedIn
Distance −1, density −1. The platform rewards a specific claim with a
consequence; it punishes the abstract lesson.
### HN and Product Hunt
Confidence +1, humor −1, density +1. State what it is, what it does not do,
and what it costs, in the first three sentences. Anything that reads as
positioning gets answered as positioning.
### App Store and Google Play
Density +2, because the field limits leave no room for register at all. Craft rules
are in [store-copy.md](store-copy.md).
### ads
Density −1 in every pack. One claim and one action; an ad has no room to
ground a term, so any term needing grounding is the wrong term for an ad.
### lifecycle email
Distance +1. One purpose per email, named in the subject line, delivered in
the first sentence.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| 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: 196k | Updated | Claude CodeCodex | Verified | Install |