[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78B0Z9R2YG9QWSTS0C0SYFN":3,"skill-same:01M78B0Z9R2YG9QWSTS0C0SYFN":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M78B0Z9R2YG9QWSTS0C0SYFN","brand-guidelines",null,"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.","princepatel04477-web\u002Ftrivoxa-group","princepatel04477-web","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F227740714?v=4","01M788ZAJ2KECD5KXVP55PZXKS","Prince Patel","01M788ZAJTCN8YSD737MRSKC5Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fbrand-guidelines\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\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","# 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",{"name":5,"risk":24,"source":25,"description":7},"unknown","community","master","877653a671c51fae6476bd9f0d34ee6c408d68b9",".github\u002Fskills\u002Fbrand-guidelines","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group","https:\u002F\u002Ftrivoxa-group.vercel.app","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web","2026-08-01 17:29:31",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add princepatel04477-web\u002Ftrivoxa-group --skill brand-guidelines",{"tool":39,"command":40},"bunx","bunx skills add princepatel04477-web\u002Ftrivoxa-group --skill brand-guidelines",{"tool":42,"command":43},"pnpm","pnpm dlx skills add princepatel04477-web\u002Ftrivoxa-group --skill brand-guidelines","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fbrand-guidelines\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M78G4Z5RFJ72G536XYPC77PG","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M78G4WQMHRST36KDP7AV3NR3","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M78G4T37F4SPS7M4KT0A8JJB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M78G4QAJMF71KD1G38MNDQYK","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M78G4MS3WE96MH5P561KFY95","zipai-optimizer","Adaptive token optimizer: intelligent filtering, surgical output, ambiguity-first, context-window-aware, VCS-aware, MCP-aware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzipai-optimizer\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M78G4GZ0T47C6929V9CVH1AK","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[]]