testing-patterns
Testing strategies, patterns, and best practices across test types. Auto-triggers when writing tests, setting up test infrastructure, or improving test coverage.
Découvrez les skills Développement, comparez leurs dépôts et consultez leurs instructions.
Testing strategies, patterns, and best practices across test types. Auto-triggers when writing tests, setting up test infrastructure, or improving test coverage.
Asynchronous programming patterns for Python, JavaScript/TypeScript, and other languages. Auto-triggers when implementing concurrent code, handling promises, or optimizing I/O operations.
Kubernetes operations, deployment patterns, and cloud-native best practices. Auto-triggers when working with containers, K8s manifests, or cloud infrastructure.
Analyze a Java class and scaffold a JUnit 5 test with proper structure and assertions
RESTful API and GraphQL design best practices. Auto-triggers when designing endpoints, handling HTTP methods, or structuring API responses.
Autonomous development loop patterns for iterative self-improvement. Auto-triggers when implementing features autonomously, fixing bugs in a loop, or running until completion. Based on frankbria/ralph-claude-co...
Test-Driven Development patterns and red-green-refactor workflow. Auto-triggers when writing tests first, implementing TDD, or discussing test coverage.
Observability patterns including logging, metrics, tracing, and alerting. Auto-triggers when implementing monitoring, debugging production issues, or setting up alerts.
Security audit patterns and OWASP Top 10 vulnerability detection. Auto-triggers when reviewing code for security, handling authentication, or processing user input.
Review and lightly edit a single blog post under _posts/ for prose quality and source hygiene, without changing code examples or post structure.
Perform comprehensive code reviews with actionable feedback. Use when reviewing pull requests, checking code quality, analyzing changes, or when the user mentions "review", "PR", "pull request", "check code", "...
Create domain entities following DDD principles. Use when the user wants to create a new entity, add a domain model, implement domain logic, or mentions "entity", "domain", "model", "aggregate".
Create domain entities following DDD principles. Use when the user wants to create a new entity, add a domain model, implement domain logic, or mentions "entity", "domain", "model", "aggregate".
Guide for implementing Clean Architecture patterns in .NET projects. Use when creating new features, refactoring code structure, or when the user mentions "clean architecture", "layers", "domain-driven", "CQRS"...
Generate code documentation, API docs, and technical guides. Use when documenting code, creating API documentation, writing technical specs, or when the user mentions "document", "docs", "README", "API docs", "...
Generate code documentation, API docs, and technical guides. Use when documenting code, creating API documentation, writing technical specs, or when the user mentions "document", "docs", "README", "API docs", "...
Create complete API endpoints following Clean Architecture. Use when the user wants to add a new endpoint, create an API, implement CRUD operations, or mentions "endpoint", "controller", "API", "REST".
Guide for implementing Clean Architecture patterns in .NET projects. Use when creating new features, refactoring code structure, or when the user mentions "clean architecture", "layers", "domain-driven", "CQRS"...
Perform comprehensive code reviews with actionable feedback. Use when reviewing pull requests, checking code quality, analyzing changes, or when the user mentions "review", "PR", "pull request", "check code", "...
Create complete API endpoints following Clean Architecture. Use when the user wants to add a new endpoint, create an API, implement CRUD operations, or mentions "endpoint", "controller", "API", "REST".
Use this skill when implementing any feature, bug fix, or plan task. Triggers on "write tests", "add a test", "do TDD", "test-driven", "implement with tests", "implement task", or when dispatched as a subagent...
This skill should be used when processing code review feedback, responding to reviewer comments, or when feedback seems unclear or technically questionable. Requires verification before implementing.
C++ debugging for segfaults, memory corruption, threading issues, and linker/ABI problems. Use when encountering crashes (exit code 139/SIGSEGV), memory leaks, data races, undefined behavior, or when debugging...
This skill should be used when claiming a task is "done", "complete", "finished", "fixed", "passing", or before committing. Requires running verification commands before making success claims.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.