
--- name: sentry description: Guide for using the Sentry CLI to interact with Sentry from the command line. Use when the user asks about viewing issues, events, projects, organizations, making API calls, or authenticating with Sentry via CLI. Primary workflow: given a short issue ID (e.g. PROJECT-123), fetch full bug report with description and stack trace. --- # Sentry CLI Skill This skill handles Sentry CLI operations: authentication, issue lookup by short ID, event details, and bug report g
Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection.
Build a robust backend system with databases, APIs, and server-side logic. Use when designing and implementing APIs, database query optimization, handle security vulnerabilities and other backend system tasks.
This skill focuses on writing/designing effective and comprehensive tests for code. It emphasizes the importance of covering various scenarios, including happy cases, error cases, edge cases, and input validation. The skill also highlights the need to write tests based on expected correct behavior rather than current implementation, and to maintain a high level of coverage (at least 80%).
MUST use whenever you do everything related to git, such as commit message, branch naming, create PR etc.
Use when user asks to clone a GitHub Pull Request locally using the GitHub CLI.
Use when user asks to clone code changes from local repository to a new directory for review or testing.
Build a robust backend system with databases, APIs, and server-side logic. Use when designing and implementing APIs, database query optimization, handle security vulnerabilities and other backend system tasks.
Use when doing tasks related to markdown files, such as editing README.md or other documentation files.
Use when user asks to work with any tasks related to GitHub, including repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.
Use when user asks to work for any tasks related to Jira, Confluence, Bitbucket, Trello, Opsgenie, and all Atlassian operations from the command line.
Use when user asks to work with any tasks related to GitHub, including repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.
Use when user asks to clone a GitHub Pull Request locally using the GitHub CLI.
Use when doing tasks related to markdown files, such as editing README.md or other documentation files.
Use when user asks to clone a GitHub Pull Request locally using the GitHub CLI.
Use when complex problems require systematic step-by-step reasoning with ability to revise thoughts, branch into alternative approaches, or dynamically adjust scope. Ideal for multi-stage analysis, design planning, problem decomposition, or tasks with initially unclear scope. DO NOT use when single-step answers suffice.
Use when user asks to clone code changes from local repository to a new directory for review or testing.
Use when user asks to clone code changes from local repository to a new directory for review or testing.
--- name: docs-seeker description: Search library/framework documentation via llms.txt (context7.com). Use for API docs, GitHub repository analysis, technical documentation lookup, latest library features. Common pattern use case: "How to use [component] in [library]?", "How can I integrate [component] in [library]?", "How to setup [component] in [library]?". --- # docs-seeker Skill ## Prerequisites - Setup CONTEXT7_API_KEY in .env file with your API key from context7.com. - Setup `context7-m
--- name: docs-seeker description: Search library/framework documentation via llms.txt (context7.com). Use for API docs, GitHub repository analysis, technical documentation lookup, latest library features. Common pattern use case: "How to use [component] in [library]?", "How can I integrate [component] in [library]?", "How to setup [component] in [library]?". --- # docs-seeker Skill ## Prerequisites - Setup CONTEXT7_API_KEY in .env file with your API key from context7.com. - Setup `context7-m
Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection.
MUST use whenever you do everything related to git, such as commit message, branch naming, create PR etc.
Use when doing tasks related to markdown files, such as editing README.md or other documentation files.
MUST use whenever you do everything related to git, such as commit message, branch naming, create PR etc.
--- name: sentry description: Guide for using the Sentry CLI to interact with Sentry from the command line. Use when the user asks about viewing issues, events, projects, organizations, making API calls, or authenticating with Sentry via CLI. Primary workflow: given a short issue ID (e.g. PROJECT-123), fetch full bug report with description and stack trace. --- # Sentry CLI Skill This skill handles Sentry CLI operations: authentication, issue lookup by short ID, event details, and bug report g
Use when complex problems require systematic step-by-step reasoning with ability to revise thoughts, branch into alternative approaches, or dynamically adjust scope. Ideal for multi-stage analysis, design planning, problem decomposition, or tasks with initially unclear scope. DO NOT use when single-step answers suffice.
This skill focuses on writing/designing effective and comprehensive tests for code. It emphasizes the importance of covering various scenarios, including happy cases, error cases, edge cases, and input validation. The skill also highlights the need to write tests based on expected correct behavior rather than current implementation, and to maintain a high level of coverage (at least 80%).
This skill focuses on writing/designing effective and comprehensive tests for code. It emphasizes the importance of covering various scenarios, including happy cases, error cases, edge cases, and input validation. The skill also highlights the need to write tests based on expected correct behavior rather than current implementation, and to maintain a high level of coverage (at least 80%).
Build a robust backend system with databases, APIs, and server-side logic. Use when designing and implementing APIs, database query optimization, handle security vulnerabilities and other backend system tasks.
Use when user asks to work with any tasks related to GitHub, including repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.
--- name: docs-seeker description: Search library/framework documentation via llms.txt (context7.com). Use for API docs, GitHub repository analysis, technical documentation lookup, latest library features. Common pattern use case: "How to use [component] in [library]?", "How can I integrate [component] in [library]?", "How to setup [component] in [library]?". --- # docs-seeker Skill ## Prerequisites - Setup CONTEXT7_API_KEY in .env file with your API key from context7.com. - Setup `context7-m
Use when complex problems require systematic step-by-step reasoning with ability to revise thoughts, branch into alternative approaches, or dynamically adjust scope. Ideal for multi-stage analysis, design planning, problem decomposition, or tasks with initially unclear scope. DO NOT use when single-step answers suffice.
--- name: sentry description: Guide for using the Sentry CLI to interact with Sentry from the command line. Use when the user asks about viewing issues, events, projects, organizations, making API calls, or authenticating with Sentry via CLI. Primary workflow: given a short issue ID (e.g. PROJECT-123), fetch full bug report with description and stack trace. --- # Sentry CLI Skill This skill handles Sentry CLI operations: authentication, issue lookup by short ID, event details, and bug report g
Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection.