brand-guidelines
Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.
Security Assessment
About brand-guidelines
The brand-guidelines skill is a writing reference that helps produce user-facing copy consistent with Sentry's brand voice. It solves the common problem of inconsistent, wordy, or off-tone product text by codifying two distinct tones and a decision table for when each applies: Plain Speech (the clear, direct, functional default for buttons, labels, forms, documentation, error messages, and settings) and Sentry Voice (an empathetic, self-aware, occasionally snarky tone reserved for 404 pages, empty states, onboarding, loading states, and marketing copy).
The skill supplies concrete rules and before/after examples for concision, active voice, jargon avoidance, and specificity, plus general conventions covering American English spelling, Title Case versus Sentence case, punctuation (no exclamation marks or ALL CAPS except acronyms), word choices to avoid, and hyphen/en-dash/em-dash usage. It also gives targeted guidance for UI elements such as buttons, error messages (say what happened, why, and what to do next), empty states, confirmation dialogs, and tooltips, and lists anti-patterns like robot speak, passive voice, hedging, and marketing speak in UI. It links to Sentry's public voice and frontend handbook references.
It is aimed at product designers, frontend engineers, technical writers, and anyone authoring interface text, error messages, onboarding flows, or marketing copy who needs it to read as Sentry. The content is purely a prose/style reference with no scripts, commands, or external calls.
FAQ
When should I use Sentry Voice instead of Plain Speech?
Default to Plain Speech for most UI, docs, error messages, and settings. Reserve Sentry Voice for moments where users have time to appreciate personality: 404 pages, empty states, onboarding, loading states, and marketing copy. Avoid it in error messages, settings, docs, and billing flows.
Does this skill require any tools or setup?
No. It is a self-contained Markdown style guide with rules and examples. There are no scripts, dependencies, or API calls to configure.
What conventions does it enforce for spelling and punctuation?
American English spelling, Title Case for headings and Sentence case for body/buttons/labels, no exclamation marks or ALL CAPS (except acronyms like API, SDK, URL), and no periods in short UI labels.
Is this specific to Sentry or reusable elsewhere?
The tone examples and voice principles are Sentry-branded, but the underlying rules (concision, active voice, specificity, anti-patterns) are general copywriting best practices applicable to most product UI.
Install brand-guidelines
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
getsentry/skills