Product Content Style Guide
This skill grounds GUI copy decisions in Bitwarden's product content style guide. Apply it to
end-user-facing strings only — button labels, error messages, toasts, modals, onboarding flows,
empty states, form labels, helper text, link text, and similar. Do not apply to design tokens,
code comments, internal/dev-facing strings, or marketing copy.
When in doubt about a specific case, ask before changing copy.
Voice and tone
Voice is constant. Tone flexes with context.
Product voice is approachable, encouraging, and transparent — consistent across platforms.
Tone conveys mood and depends on who you're talking to and what's happening. Security is serious
stuff. Users aren't looking for humor or fluff — they want to know their information is safe. So
Bitwarden's product tone is almost always serious and respectful.
Tone spectrums:
- Casual ↔ formal
- Enthusiastic ↔ matter-of-fact
Where common content types land on the tone map (axes: casual ↔ formal × matter-of-fact ↔ enthusiastic):
| Content type |
Casual / Formal |
Matter-of-fact / Enthusiastic |
| Success messages |
Casual |
Enthusiastic |
| Onboarding copy |
Casual |
Enthusiastic |
| Dialogs |
Casual |
Matter-of-fact |
| Empty states |
Casual |
Matter-of-fact (slightly) |
| Labels |
Neutral |
Matter-of-fact |
| Community |
Formal |
Enthusiastic |
| Confirmations |
Formal |
Matter-of-fact |
| Help articles |
Formal (slightly) |
Neutral |
| Warnings |
Formal |
Matter-of-fact |
| Error states |
Formal |
Matter-of-fact |
Examples
Error message — formal, matter-of-fact:
- Good: An error occurred. Please try again.
- Avoid: Uh oh! We goofed. Go ahead and refresh!
Onboarding message — casual, enthusiastic:
- Good: Hey there! 👋 Welcome to Bitwarden. We'll show you around!
- Avoid: This is your vault. Get started now.
Applying this skill
During explicit copy critique ("review this copy", "is this error message ok"):
- Identify the content type (error, onboarding, button, etc.) and the expected tone using the
tone map above.
- Check voice consistency (approachable, encouraging, transparent).
- Walk grammar and mechanics rules relevant to the snippet — see
references/grammar-mechanics.md.
- Walk accessibility rules relevant to the snippet — see
references/accessibility-rules.md.
- Return specific, actionable rewrites — not just "this is wrong."
Inside figma-to-angular runs (external skill in the clients repo, not bundled here):
When the Figma design includes copy strings, validate them against this guide before emitting
them into the Angular template. If a string clearly violates a rule (e.g., title-case button,
ampersand, "Click here" link), surface the issue and propose a compliant alternative — do not
silently rewrite. Ask the user which to use.
Inside design-review critiques:
If the stage is 60% or 90%, include content observations alongside visual feedback (90% is the
right stage for "nitty-gritty grammar, finalizing copy"). Skip content nitpicks at 30% — the
copy will change. Frame content feedback the same way as visual feedback: tied to user/product
goals, not personal taste.
Output format for copy critique
- Content type and expected tone — name what this string is and where it should land on
the tone spectrum.
- What's working — what to keep.
- Issues — each tied to a specific rule from this guide (cite the section name, including
the references file if the rule lives there).
- Proposed rewrite(s) — concrete alternatives the user can pick from.
Keep critique specific. "The button uses title case; sentence case per
references/grammar-mechanics.md (Capitalization)" beats "the capitalization is off."
Additional resources
The detailed rules live in two references files. Load them when the critique needs them — most
copy issues touch only one or two rules.
references/grammar-mechanics.md — Acronyms, ampersands, capitalization (sentence case,
product names, features, lowercase objects), dates and months, days of the week, e.g. / i.e.,
ellipsis, file sizes and formats, money, numbers, Oxford comma, times and time zones, versus.
references/accessibility-rules.md — Reading level and directness, scannable layouts,
non-English and ESL considerations, spelling out acronyms, avoiding "easy" and "simple"
framings, text styling, spatial language, alt text, meaningful link text, gender-neutral
pronouns.
1---2name: content-style-guide3description: Bitwarden's product content style guide for end-user-facing GUI copy — voice, tone, AP-style-with-exceptions grammar, sentence case in UI, and accessibility-first language at a U.S. 7th-grade reading level.4when_to_use: Use when end-user-facing GUI strings are being authored or critiqued — button labels, error messages, toasts, modal copy, onboarding, empty states, form labels, helper text, link text. Triggers — "review this copy", "is this error message ok", "rewrite this button label", "check the wording", "what should this say". Composed by `design-review` at 60%/90% stages and by `figma-to-angular` (external, not bundled) during code generation. Not for developer-facing strings, code comments, design tokens, or marketing/long-form content.5allowed-tools: Skill6metadata:7 source: https://skillmd.com/skills/bitwarden/content-style-guide8---910# Product Content Style Guide1112This skill grounds GUI copy decisions in Bitwarden's product content style guide. Apply it to13end-user-facing strings only — button labels, error messages, toasts, modals, onboarding flows,14empty states, form labels, helper text, link text, and similar. Do not apply to design tokens,15code comments, internal/dev-facing strings, or marketing copy.1617When in doubt about a specific case, ask before changing copy.1819## Voice and tone2021**Voice is constant. Tone flexes with context.**2223Product voice is **approachable, encouraging, and transparent** — consistent across platforms.2425Tone conveys mood and depends on who you're talking to and what's happening. Security is serious26stuff. Users aren't looking for humor or fluff — they want to know their information is safe. So27Bitwarden's product tone is **almost always serious and respectful**.2829Tone spectrums:3031- Casual ↔ formal32- Enthusiastic ↔ matter-of-fact3334Where common content types land on the tone map (axes: casual ↔ formal × matter-of-fact ↔ enthusiastic):3536| Content type | Casual / Formal | Matter-of-fact / Enthusiastic |37| ---------------- | ----------------- | ----------------------------- |38| Success messages | Casual | Enthusiastic |39| Onboarding copy | Casual | Enthusiastic |40| Dialogs | Casual | Matter-of-fact |41| Empty states | Casual | Matter-of-fact (slightly) |42| Labels | Neutral | Matter-of-fact |43| Community | Formal | Enthusiastic |44| Confirmations | Formal | Matter-of-fact |45| Help articles | Formal (slightly) | Neutral |46| Warnings | Formal | Matter-of-fact |47| Error states | Formal | Matter-of-fact |4849### Examples5051**Error message — formal, matter-of-fact:**5253- Good: An error occurred. Please try again.54- Avoid: Uh oh! We goofed. Go ahead and refresh!5556**Onboarding message — casual, enthusiastic:**5758- Good: Hey there! 👋 Welcome to Bitwarden. We'll show you around!59- Avoid: This is your vault. Get started now.6061## Applying this skill6263**During explicit copy critique** ("review this copy", "is this error message ok"):64651. Identify the content type (error, onboarding, button, etc.) and the expected tone using the66 tone map above.672. Check voice consistency (approachable, encouraging, transparent).683. Walk grammar and mechanics rules relevant to the snippet — see69 `references/grammar-mechanics.md`.704. Walk accessibility rules relevant to the snippet — see `references/accessibility-rules.md`.715. Return specific, actionable rewrites — not just "this is wrong."7273**Inside `figma-to-angular` runs** (external skill in the clients repo, not bundled here):7475When the Figma design includes copy strings, validate them against this guide before emitting76them into the Angular template. If a string clearly violates a rule (e.g., title-case button,77ampersand, "Click here" link), surface the issue and propose a compliant alternative — do not78silently rewrite. Ask the user which to use.7980**Inside design-review critiques:**8182If the stage is 60% or 90%, include content observations alongside visual feedback (90% is the83right stage for "nitty-gritty grammar, finalizing copy"). Skip content nitpicks at 30% — the84copy will change. Frame content feedback the same way as visual feedback: tied to user/product85goals, not personal taste.8687## Output format for copy critique88891. **Content type and expected tone** — name what this string is and where it should land on90 the tone spectrum.912. **What's working** — what to keep.923. **Issues** — each tied to a specific rule from this guide (cite the section name, including93 the references file if the rule lives there).944. **Proposed rewrite(s)** — concrete alternatives the user can pick from.9596Keep critique specific. "The button uses title case; sentence case per97`references/grammar-mechanics.md` (Capitalization)" beats "the capitalization is off."9899## Additional resources100101The detailed rules live in two references files. Load them when the critique needs them — most102copy issues touch only one or two rules.103104- **`references/grammar-mechanics.md`** — Acronyms, ampersands, capitalization (sentence case,105 product names, features, lowercase objects), dates and months, days of the week, e.g. / i.e.,106 ellipsis, file sizes and formats, money, numbers, Oxford comma, times and time zones, versus.107- **`references/accessibility-rules.md`** — Reading level and directness, scannable layouts,108 non-English and ESL considerations, spelling out acronyms, avoiding "easy" and "simple"109 framings, text styling, spatial language, alt text, meaningful link text, gender-neutral110 pronouns.