Brand Guidelines
Write user-facing copy following Sentry's brand guidelines.
When to Use
- You need to write or rewrite user-facing copy in Sentry's voice.
- The task involves UI text, onboarding, empty states, docs, marketing copy, or other branded content.
- You need guidance on when to use Plain Speech versus Sentry Voice.
Tone Selection
Choose the appropriate tone based on context:
| Use Plain Speech |
Use Sentry Voice |
| Product UI (buttons, labels, forms) |
404 pages |
| Documentation |
Empty states |
| Error messages |
Onboarding flows |
| Settings pages |
Loading states |
| Transactional emails |
"What's New" announcements |
| Help text |
Marketing copy |
Default to Plain Speech unless the context specifically calls for personality.
Plain Speech (Default)
Plain Speech is clear, direct, and functional. Use it for most UI elements.
Rules
- Be concise - Use the fewest words needed
- Be direct - Tell users what to do, not what they can do
- Use active voice - "Save your changes" not "Your changes will be saved"
- Avoid jargon - Use simple words users understand
- Be specific - "3 errors found" not "Some errors found"
Examples
| Instead of |
Write |
| "Click here to save your changes" |
"Save" |
| "You can filter results by date" |
"Filter by date" |
| "An error has occurred" |
"Something went wrong" |
| "Please enter a valid email address" |
"Enter a valid email" |
| "Are you sure you want to delete?" |
"Delete this item?" |
Sentry Voice
Sentry Voice adds personality in appropriate moments. It's empathetic, self-aware, and occasionally snarky.
Principles
- Empathetic snark - Direct frustration at the situation, never the user
- Self-aware - Acknowledge the absurdity of software
- Fun but functional - Personality should enhance, not obscure meaning
- Earned moments - Only use when users have time to appreciate it
Examples
404 Pages:
"This page doesn't exist. Maybe it never did. Maybe it was a dream. Either way, let's get you back on track."
Empty States:
"No errors yet. Enjoy this moment of peace while it lasts."
Onboarding:
"Let's get your first error. Don't worry, it's not as scary as it sounds."
Loading States:
"Crunching the numbers..."
"Fetching your data..."
When NOT to Use Sentry Voice
- Error messages (users are frustrated)
- Settings pages (users are focused)
- Documentation (users need information)
- Billing/payment flows (users need trust)
General Rules
Spelling and Grammar
- Use American English spelling (color, not colour)
- Use Title Case for headings and page titles
- Use Sentence case for body text, buttons, and labels
Punctuation
- No exclamation marks in UI text (exception: celebratory moments)
- No periods in short UI labels or button text
- Use periods in complete sentences and help text
- No ALL CAPS except for acronyms (API, SDK, URL)
Word Choices
| Avoid |
Prefer |
| Please |
(omit) |
| Sorry |
(be specific about the problem) |
| Error occurred |
Something went wrong |
| Invalid |
(explain what's wrong) |
| Success! |
(describe what happened) |
| Oops |
(be specific) |
Dash Usage
| Type |
Use |
Example |
| Hyphen (-) |
Compound words, ranges |
"real-time", "1-10" |
| En-dash (--) |
Ranges, relationships |
"2023--2024", "parent--child" |
| Em-dash (---) |
Interruption, emphasis |
"Errors---even small ones---matter" |
In most UI contexts, use hyphens. Reserve en-dashes for date ranges and em-dashes for longer prose.
UI Element Guidelines
Buttons
- Use action verbs: "Save", "Delete", "Create"
- Be specific: "Create Project" not just "Create"
- Max 2-3 words when possible
- No periods or exclamation marks
Error Messages
- Say what happened
- Say why (if helpful)
- Say what to do next
Good: "Could not save changes. Check your connection and try again."
Bad: "Error: Save failed."
Empty States
- Explain what would normally be here
- Provide a clear action to populate the state
- Sentry Voice is appropriate here
Good: "No projects yet. Create your first project to start tracking errors."
Confirmation Dialogs
- Make the action clear in the title
- Explain consequences if destructive
- Use specific button labels ("Delete Project", not "OK")
Tooltips and Help Text
- Keep under 2 sentences
- Explain the "why", not just the "what"
- Link to docs for complex topics
Anti-Patterns
Avoid these common mistakes:
- Robot speak: "Item has been successfully deleted" -> "Deleted"
- Passive voice: "Changes were saved" -> "Changes saved"
- Unnecessary words: "In order to" -> "To"
- Hedging: "This might cause..." -> "This will cause..."
- Double negatives: "Not unlike..." -> "Similar to..."
- Marketing speak in UI: "Supercharge your workflow" -> "Speed up your workflow"
References
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---2name: brand-guidelines-23description: 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.4risk: none5source: community6metadata:7 source: https://skillmd.com/skills/mhassan0000/brand-guidelines-28---910# Brand Guidelines1112Write user-facing copy following Sentry's brand guidelines.1314## When to Use15- You need to write or rewrite user-facing copy in Sentry's voice.16- The task involves UI text, onboarding, empty states, docs, marketing copy, or other branded content.17- You need guidance on when to use Plain Speech versus Sentry Voice.1819## Tone Selection2021Choose the appropriate tone based on context:2223| Use Plain Speech | Use Sentry Voice |24|------------------|------------------|25| Product UI (buttons, labels, forms) | 404 pages |26| Documentation | Empty states |27| Error messages | Onboarding flows |28| Settings pages | Loading states |29| Transactional emails | "What's New" announcements |30| Help text | Marketing copy |3132**Default to Plain Speech** unless the context specifically calls for personality.3334## Plain Speech (Default)3536Plain Speech is clear, direct, and functional. Use it for most UI elements.3738### Rules39401. **Be concise** - Use the fewest words needed412. **Be direct** - Tell users what to do, not what they can do423. **Use active voice** - "Save your changes" not "Your changes will be saved"434. **Avoid jargon** - Use simple words users understand445. **Be specific** - "3 errors found" not "Some errors found"4546### Examples4748| Instead of | Write |49|------------|-------|50| "Click here to save your changes" | "Save" |51| "You can filter results by date" | "Filter by date" |52| "An error has occurred" | "Something went wrong" |53| "Please enter a valid email address" | "Enter a valid email" |54| "Are you sure you want to delete?" | "Delete this item?" |5556## Sentry Voice5758Sentry Voice adds personality in appropriate moments. It's empathetic, self-aware, and occasionally snarky.5960### Principles61621. **Empathetic snark** - Direct frustration at the situation, never the user632. **Self-aware** - Acknowledge the absurdity of software643. **Fun but functional** - Personality should enhance, not obscure meaning654. **Earned moments** - Only use when users have time to appreciate it6667### Examples6869**404 Pages:**70> "This page doesn't exist. Maybe it never did. Maybe it was a dream. Either way, let's get you back on track."7172**Empty States:**73> "No errors yet. Enjoy this moment of peace while it lasts."7475**Onboarding:**76> "Let's get your first error. Don't worry, it's not as scary as it sounds."7778**Loading States:**79> "Crunching the numbers..."80> "Fetching your data..."8182### When NOT to Use Sentry Voice8384- Error messages (users are frustrated)85- Settings pages (users are focused)86- Documentation (users need information)87- Billing/payment flows (users need trust)8889## General Rules9091### Spelling and Grammar9293- Use **American English** spelling (color, not colour)94- Use **Title Case** for headings and page titles95- Use **Sentence case** for body text, buttons, and labels9697### Punctuation9899- **No exclamation marks** in UI text (exception: celebratory moments)100- **No periods** in short UI labels or button text101- **Use periods** in complete sentences and help text102- **No ALL CAPS** except for acronyms (API, SDK, URL)103104### Word Choices105106| Avoid | Prefer |107|-------|--------|108| Please | (omit) |109| Sorry | (be specific about the problem) |110| Error occurred | Something went wrong |111| Invalid | (explain what's wrong) |112| Success! | (describe what happened) |113| Oops | (be specific) |114115## Dash Usage116117| Type | Use | Example |118|------|-----|---------|119| Hyphen (-) | Compound words, ranges | "real-time", "1-10" |120| En-dash (--) | Ranges, relationships | "2023--2024", "parent--child" |121| Em-dash (---) | Interruption, emphasis | "Errors---even small ones---matter" |122123In most UI contexts, use hyphens. Reserve en-dashes for date ranges and em-dashes for longer prose.124125## UI Element Guidelines126127### Buttons128129- Use action verbs: "Save", "Delete", "Create"130- Be specific: "Create Project" not just "Create"131- Max 2-3 words when possible132- No periods or exclamation marks133134### Error Messages1351361. Say what happened1372. Say why (if helpful)1383. Say what to do next139140**Good:** "Could not save changes. Check your connection and try again."141**Bad:** "Error: Save failed."142143### Empty States1441451. Explain what would normally be here1462. Provide a clear action to populate the state1473. Sentry Voice is appropriate here148149**Good:** "No projects yet. Create your first project to start tracking errors."150151### Confirmation Dialogs152153- Make the action clear in the title154- Explain consequences if destructive155- Use specific button labels ("Delete Project", not "OK")156157### Tooltips and Help Text158159- Keep under 2 sentences160- Explain the "why", not just the "what"161- Link to docs for complex topics162163## Anti-Patterns164165Avoid these common mistakes:166167- **Robot speak:** "Item has been successfully deleted" -> "Deleted"168- **Passive voice:** "Changes were saved" -> "Changes saved"169- **Unnecessary words:** "In order to" -> "To"170- **Hedging:** "This might cause..." -> "This will cause..."171- **Double negatives:** "Not unlike..." -> "Similar to..."172- **Marketing speak in UI:** "Supercharge your workflow" -> "Speed up your workflow"173174## References175176- [Sentry Voice Guidelines](https://develop.sentry.dev/frontend/sentry-voice/)177- [Sentry Frontend Handbook](https://develop.sentry.dev/frontend/)178179## Limitations180- Use this skill only when the task clearly matches the scope described above.181- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.182- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.