[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CSBJSWAJSF7GEVJWH6T9J6":3,"skill-same:01M6CSBJSWAJSF7GEVJWH6T9J6":94},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":62,"ownerHtmlUrl":63,"ownerBlogUrl":6,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M6CSBJSWAJSF7GEVJWH6T9J6","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.","Sam-06060\u002Fjarvis-assistant","Sam-06060","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F208600848?v=4","01M6CRKT7C7FXD21V6HXF293S0","Samson Frank Ganta","01M6CRKTBEKYFD8YX5Z1GT99EE",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fbrand-guidelines\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"brand guidelines","guidelines","brand","community","writing","default","use","user","write","text","voice","marketing","messages","error messages","ui","content","onboarding","speech","sentry","documentation","2026-11-10 10:12:30",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\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","# Brand Guidelines\n\nWrite user-facing copy following Sentry's brand guidelines.\n\n## When to Use\n\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",{"name":5,"risk":57,"source":35,"description":7},"unknown","main","a50a3aa6b39fb0e1b7db88bef1bfc9c93606e126","modules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fbrand-guidelines",0,"https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant","https:\u002F\u002Fgithub.com\u002FSam-06060","Mobile Application Developer | Kotlin | Flutter, KMP, Swfit, Android,Swift UI | Building at Saar It Resources | Creator of Jarvis (AI Assistant)","2026-06-23 05:13:38",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add Sam-06060\u002Fjarvis-assistant --skill brand-guidelines",{"tool":72,"command":73},"bunx","bunx skills add Sam-06060\u002Fjarvis-assistant --skill brand-guidelines",{"tool":75,"command":76},"pnpm","pnpm dlx skills add Sam-06060\u002Fjarvis-assistant --skill brand-guidelines","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fbrand-guidelines\u002FSKILL.md",true,[80,86,90],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"alternatives.md","REFERENCE","参考文档",5866,"https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Freact-useeffect\u002Falternatives.md",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"anti-patterns.md",6146,"https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Freact-useeffect\u002Fanti-patterns.md",{"path":91,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":92,"sourceHtmlUrl":93},"README.md",10085,"https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Freact-useeffect\u002FREADME.md",[95,106,122,149,168,195],{"skillNo":96,"name":97,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":103,"publishedAt":52},"01M6GDRVS6FXX3ESH0C9DW01C0","test_skill","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fscratch\u002Ftest_skill\u002FSKILL.md",[100],{"categoryNo":101,"categoryName":102,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[104,105],"Test Skill","test",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":52},"01M6GDRQ40HX22MA6XWC31RHHK","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzustand-store-ts\u002FSKILL.md",[],[113,114,115,116,117,118,119,35,120,121],"zustand store ts","zustand","store","with","types","middleware","patterns","create","typescript",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":131,"publishedAt":52},"01M6GDRKEA0WE670SPFWX5GKCN","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\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoom-automation\u002FSKILL.md",[128],{"categoryNo":129,"categoryName":130,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[132,133,134,135,136,137,138,139,140,141,142,143,144,145,35,146,147,148],"automation","zoom automation","zoom","first","Tools","search","MCP","via","meeting","automate","critical","creation","webinars","composio","recordings","management","tracking",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":156,"publishedAt":52},"01M6GDRFS1452PC71JQ38S24HR","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\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoho-crm-automation\u002FSKILL.md",[155],{"categoryNo":129,"categoryName":130,"taxonomyType":21,"taxonomyTypeDesc":22},[157,132,158,159,160,161,162,35,137,163,145,164,142,141,136,165,120,166,138,167],"crm automation","zoho crm","crm","zoho crm automation","zoho","leads","contacts","records","update","tasks","manage",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":177,"publishedAt":52},"01M6GDRCKQBAVTGHX5XBH26KPZ","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\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzod-validation-expert\u002FSKILL.md",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[178,179,180,181,182,121,183,184,185,186,187,188,116,189,190,191,192,35,193,194],"expert","zod","zod validation expert","validation","react","safe","parsing","errors","schema validation","react hook form","hook","trpc","form","type","next","schema","Next.js",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":202,"publishedAt":52},"01M6GDR658B08K4MY0RWD4A6EH","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\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzeroize-audit\u002FSKILL.md",[201],{"categoryNo":129,"categoryName":130,"taxonomyType":21,"taxonomyTypeDesc":22},[203,204,40,205,206,207,208,209,35,210,211,212,213,214,215,216,217,218,219,138],"zeroize audit","audit","passwords","get","project","c++","activate","assembly","read","Bash","secrets","analysis","data","flow","verification","code","rust"]