Loading...
Loading...
Found 1,588 Skills
D2 Diagram Creator - Auto-activating skill for Visual Content. Triggers on: d2 diagram creator, d2 diagram creator Part of the Visual Content skill category.
General coding best practices and software engineering principles to build robust, maintainable, and scalable software.
Automatically scan and execute all skills ending with best-practice to check if the project complies with best practices. Ensure all relevant best practices are checked through the auto-discovery mechanism, and enforce standardized validation instructions to improve output stability.
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
Automatically detect code quality issues and provide improvement recommendations
Prompt engineering standards and context engineering principles for AI agents based on Anthropic best practices. Covers clarity, structure, progressive discovery, and optimization for signal-to-noise ratio.
Provides insights and techniques from renowned songwriters across different genres to help users improve their own lyrical compositions.
Use when designing API endpoints. Use when using wrong HTTP methods. Use when POST is used for reads.
Use when working with C#, F#, .NET libraries, ASP.NET Core, Blazor, Entity Framework Core, and the broader .NET ecosystem. USE FOR: .NET language features, choosing libraries and frameworks, project structure, package selection, architecture decisions DO NOT USE FOR: specific library configuration details (use the sub-skills: web, data, testing, eventing, cloud, etc.)
Websocket Client Creator - Auto-activating skill for API Integration. Triggers on: websocket client creator, websocket client creator Part of the API Integration skill category.
Use when advanced Pytest features including markers, custom assertions, hooks, and coverage configuration.
Write behavior-focused tests following Testing Trophy model with real dependencies, avoiding common anti-patterns like testing mocks and polluting production code. Use when writing new tests, reviewing test quality, or improving test coverage.