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.
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill brand-guidelines