[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-ee6c9ad3-a074-4c0b-afda-41e37de4d426":3,"$fyuDK2eptJhJnpkvlaXnB5qghvlqbDCg8_mkP6uIGYck":43},{"id":4,"title":5,"description":6,"categoryId":7,"moduleId":8,"tags":9,"prompt":10,"icon":11,"source":12,"sourceUrl":13,"authorId":14,"authorName":15,"isPublic":16,"stars":17,"runs":18,"createdAt":19,"updatedAt":19,"module":20,"category":27,"packages":34},"ee6c9ad3-a074-4c0b-afda-41e37de4d426","brand-guidelines","遵循Sentry品牌指南撰写文案。用于编写UI文本、错误消息、空状态、引导流程、404页面、文档、营销文案或任何面向用户的内容。涵盖标准口语（默认）和Sentry语气。","cat_design_graphic","mod_design","sickn33,design","---\nname: brand-guidelines\ndescription: 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.\nrisk: unknown\nsource: community\n---\n\n# Brand Guidelines\n\nWrite user-facing copy following Sentry's brand guidelines.\n\n## When to Use\n- You need to write or rewrite user-facing copy in Sentry's voice.\n- The task involves UI text, onboarding, empty states, docs, marketing copy, or other branded content.\n- You need guidance on when to use Plain Speech versus Sentry Voice.\n\n## Tone Selection\n\nChoose the appropriate tone based on context:\n\n| Use Plain Speech | Use Sentry Voice |\n|------------------|------------------|\n| Product UI (buttons, labels, forms) | 404 pages |\n| Documentation | Empty states |\n| Error messages | Onboarding flows |\n| Settings pages | Loading states |\n| Transactional emails | \"What's New\" announcements |\n| Help text | Marketing copy |\n\n**Default to Plain Speech** unless the context specifically calls for personality.\n\n## Plain Speech (Default)\n\nPlain Speech is clear, direct, and functional. Use it for most UI elements.\n\n### Rules\n\n1. **Be concise** - Use the fewest words needed\n2. **Be direct** - Tell users what to do, not what they can do\n3. **Use active voice** - \"Save your changes\" not \"Your changes will be saved\"\n4. **Avoid jargon** - Use simple words users understand\n5. **Be specific** - \"3 errors found\" not \"Some errors found\"\n\n### Examples\n\n| Instead of | Write |\n|------------|-------|\n| \"Click here to save your changes\" | \"Save\" |\n| \"You can filter results by date\" | \"Filter by date\" |\n| \"An error has occurred\" | \"Something went wrong\" |\n| \"Please enter a valid email address\" | \"Enter a valid email\" |\n| \"Are you sure you want to delete?\" | \"Delete this item?\" |\n\n## Sentry Voice\n\nSentry Voice adds personality in appropriate moments. It's empathetic, self-aware, and occasionally snarky.\n\n### Principles\n\n1. **Empathetic snark** - Direct frustration at the situation, never the user\n2. **Self-aware** - Acknowledge the absurdity of software\n3. **Fun but functional** - Personality should enhance, not obscure meaning\n4. **Earned moments** - Only use when users have time to appreciate it\n\n### Examples\n\n**404 Pages:**\n> \"This page doesn't exist. Maybe it never did. Maybe it was a dream. Either way, let's get you back on track.\"\n\n**Empty States:**\n> \"No errors yet. Enjoy this moment of peace while it lasts.\"\n\n**Onboarding:**\n> \"Let's get your first error. Don't worry, it's not as scary as it sounds.\"\n\n**Loading States:**\n> \"Crunching the numbers...\"\n> \"Fetching your data...\"\n\n### When NOT to Use Sentry Voice\n\n- Error messages (users are frustrated)\n- Settings pages (users are focused)\n- Documentation (users need information)\n- Billing\u002Fpayment flows (users need trust)\n\n## General Rules\n\n### Spelling and Grammar\n\n- Use **American English** spelling (color, not colour)\n- Use **Title Case** for headings and page titles\n- Use **Sentence case** for body text, buttons, and labels\n\n### Punctuation\n\n- **No exclamation marks** in UI text (exception: celebratory moments)\n- **No periods** in short UI labels or button text\n- **Use periods** in complete sentences and help text\n- **No ALL CAPS** except for acronyms (API, SDK, URL)\n\n### Word Choices\n\n| Avoid | Prefer |\n|-------|--------|\n| Please | (omit) |\n| Sorry | (be specific about the problem) |\n| Error occurred | Something went wrong |\n| Invalid | (explain what's wrong) |\n| Success! | (describe what happened) |\n| Oops | (be specific) |\n\n## Dash Usage\n\n| Type | Use | Example |\n|------|-----|---------|\n| Hyphen (-) | Compound words, ranges | \"real-time\", \"1-10\" |\n| En-dash (--) | Ranges, relationships | \"2023--2024\", \"parent--child\" |\n| Em-dash (---) | Interruption, emphasis | \"Errors---even small ones---matter\" |\n\nIn most UI contexts, use hyphens. Reserve en-dashes for date ranges and em-dashes for longer prose.\n\n## UI Element Guidelines\n\n### Buttons\n\n- Use action verbs: \"Save\", \"Delete\", \"Create\"\n- Be specific: \"Create Project\" not just \"Create\"\n- Max 2-3 words when possible\n- No periods or exclamation marks\n\n### Error Messages\n\n1. Say what happened\n2. Say why (if helpful)\n3. Say what to do next\n\n**Good:** \"Could not save changes. Check your connection and try again.\"\n**Bad:** \"Error: Save failed.\"\n\n### Empty States\n\n1. Explain what would normally be here\n2. Provide a clear action to populate the state\n3. Sentry Voice is appropriate here\n\n**Good:** \"No projects yet. Create your first project to start tracking errors.\"\n\n### Confirmation Dialogs\n\n- Make the action clear in the title\n- Explain consequences if destructive\n- Use specific button labels (\"Delete Project\", not \"OK\")\n\n### Tooltips and Help Text\n\n- Keep under 2 sentences\n- Explain the \"why\", not just the \"what\"\n- Link to docs for complex topics\n\n## Anti-Patterns\n\nAvoid these common mistakes:\n\n- **Robot speak:** \"Item has been successfully deleted\" -> \"Deleted\"\n- **Passive voice:** \"Changes were saved\" -> \"Changes saved\"\n- **Unnecessary words:** \"In order to\" -> \"To\"\n- **Hedging:** \"This might cause...\" -> \"This will cause...\"\n- **Double negatives:** \"Not unlike...\" -> \"Similar to...\"\n- **Marketing speak in UI:** \"Supercharge your workflow\" -> \"Speed up your workflow\"\n\n## References\n\n- [Sentry Voice Guidelines](https:\u002F\u002Fdevelop.sentry.dev\u002Ffrontend\u002Fsentry-voice\u002F)\n- [Sentry Frontend Handbook](https:\u002F\u002Fdevelop.sentry.dev\u002Ffrontend\u002F)\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","","imported","https:\u002F\u002Fgithub.com\u002Fsickn33\u002Fantigravity-awesome-skills","user_system_seed","SkillOPIC",true,237,1490,"2026-05-16 13:09:17",{"id":8,"name":21,"slug":22,"icon":23,"description":24,"sort":25,"createdAt":26},"设计创意","design","mdi-palette-outline","UI 设计、生成艺术、品牌视觉等创意 Skill",3,"2026-05-16 12:53:40",{"id":7,"name":28,"slug":29,"icon":30,"description":31,"moduleId":8,"sort":32,"skillCount":33,"createdAt":26},"视觉创意","graphic","mdi-brush","海报、Logo、插画等视觉创作",2,48,[35],{"id":36,"skillId":4,"version":37,"fileName":38,"fileSize":39,"filePath":40,"fileHash":41,"manifest":42,"createdAt":19},"e5ac547d-2f02-4eb9-a61f-6f2bf88be9da","1.0.0","brand-guidelines.zip",2751,"uploads\u002Fskills\u002Fee6c9ad3-a074-4c0b-afda-41e37de4d426\u002Fbrand-guidelines.zip","9c2aee9a1899ac6df2a2158800b0601a247f6f655bb6f35c6c077e03e818d314","[{\"path\":\"SKILL.md\",\"isDirectory\":false,\"size\":5844}]",{"code":44,"message":45,"data":46},200,"success",{"items":47,"stats":48,"page":51},[],{"averageRating":49,"totalRatings":49,"ratingCounts":50},0,[49,49,49,49,49],{"limit":52,"offset":49,"hasMore":53,"nextOffset":52,"ratedOnly":16},15,false]