Brand Guidelines

If you're writing copy for Sentry or a product with similar voice guidelines, this gives you the full playbook. It breaks down when to use Plain Speech (most UI, docs, errors) versus Sentry Voice (404s, empty states, onboarding), with real examples for buttons, error messages, and confirmation dialogs. The guidance is opinionated in good ways: no exclamation marks in UI, be specific instead of saying "invalid", direct frustration at the situation not the user. It even covers dash usage and anti-patterns like robot speak. Worth having if you're maintaining consistent voice across a product, though the Sentry-specific examples mean you'll adapt rather than copy-paste.

skills.sh installs: 512
GitHub stars: 43.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add sickn33/antigravity-awesome-skills --skill brand-guidelines --agent claude-code

Installs into .claude/skills of the current project.

Files

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