Agent skill · writing content · sickn33
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.
Why this skill is useful
Provides specific tone guidelines and examples for writing user-facing copy that align with Sentry's brand identity.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
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 1. Be concise - Use the fewest words needed 2. Be direct - Tell users what to do, not what they can do 3. Use active voice - "Save your changes" not "Your changes will be saved" 4. Avoid jargon - Use simple words users understand 5. 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 1. Empathetic snark - Direct frustration at the situation, never the user 2. Self-aware - Acknowledge the absurdity of software 3. Fun but functional - Personality should enhance, not obscure meaning 4. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/brand-guidelines--34458b