junit-extensions
Use when jUnit extensions including custom extensions, rules, and conditional test execution.
junit-fundamentals
Use when jUnit fundamentals including annotations, assertions, and test lifecycle for Java testing.
junit-parameterized
Use when jUnit parameterized tests with various value sources and test factories.
kubernetes-manifests
Use when writing and deploying Kubernetes manifests for container orchestration.
kubernetes-resources
Use when managing Kubernetes resources including deployments, services, configmaps, and secrets.
kubernetes-security
Use when implementing Kubernetes security best practices including RBAC, pod security policies, and network policies.
kustomize-basics
Use when customizing Kubernetes configurations without templates using Kustomize overlays and patches.
kustomize-generators
Use when generating ConfigMaps and Secrets with Kustomize for Kubernetes configuration management.
kustomize-overlays
Use when managing environment-specific Kubernetes configurations with Kustomize overlays and patches.
maven-build-lifecycle
Use when working with Maven build phases, goals, profiles, or customizing the build process for Java projects.
maven-dependency-management
Use when managing Maven dependencies, resolving dependency conflicts, configuring BOMs, or optimizing dependency trees in Java projects.
maven-plugin-configuration
Use when configuring Maven plugins, setting up common plugins like compiler, surefire, jar, or creating custom plugin executions.
mise-environment-management
Use when managing environment variables and project settings with Mise. Covers env configuration, direnv replacement, and per-directory settings.
mise-task-configuration
Use when defining and configuring Mise tasks in mise.toml. Covers task definitions, dependencies, file tasks, and parallel execution.
mise-tool-management
Use when managing development tool versions with Mise. Covers installing tools, version pinning, and replacing language-specific version managers.
mocha-assertions
Use when assertion libraries for Mocha including Chai with expect, should, and assert styles.
mocha-configuration
Use when mocha configuration including reporters, config files, plugins, and CI integration.
mocha-fundamentals
Use when mocha test structure, hooks, and async testing patterns for JavaScript testing.
playwright-bdd-configuration
Use when configuring Playwright BDD projects, setting up defineBddConfig(), configuring feature and step file paths, and integrating with Playwright config.
playwright-bdd-gherkin-syntax
Use when writing Gherkin feature files, using Scenario Outline with Examples, applying tags for test organization, and leveraging Background sections for shared setup.
playwright-bdd-step-definitions
Use when creating step definitions with Given, When, Then, using createBdd() for step functions, implementing Page Object Model patterns, and sharing fixtures between steps.
playwright-fixtures-and-hooks
Use when managing test state and infrastructure with reusable Playwright fixtures and lifecycle hooks for efficient test setup and teardown.
playwright-page-object-model
Use when creating page objects or refactoring Playwright tests for better maintainability with Page Object Model patterns.
playwright-test-architecture
Use when setting up Playwright test projects and organizing test suites with proper configuration and project structure.
pulumi-basics
Use when writing infrastructure-as-code with Pulumi using programming languages for cloud resource provisioning.
pulumi-components
Use when building reusable infrastructure components with Pulumi for modular, composable cloud resources.
pulumi-stacks
Use when managing multiple environments with Pulumi stacks for development, staging, and production deployments.
develop
Comprehensive 8-phase workflow for developing new features with quality enforcement
document
Generate or update documentation for code, APIs, or systems
documentation
Use when creating or updating documentation including READMEs, API docs, inline comments, or technical guides. Focuses on clarity and usefulness for the intended audience.
explain
Explain code, concepts, or technical decisions in clear, understandable terms
explainer
Use when explaining code, technical concepts, or implementation decisions. Provides structured approach to creating clear, understandable explanations tailored to the audience.
fix
Debug and fix bugs, errors, or unexpected behavior
legacy-code-safety
Use when modifying, removing, or refactoring code that lacks test coverage. Emphasizes the danger of untested changes and the RGR workflow to add characterization tests before modifications.
optimize
Optimize code for performance, readability, or efficiency
orthogonality-principle
Use when designing modules, APIs, and system architecture requiring independent, non-overlapping components where changes in one don't affect others.
performance-optimization
Use when optimizing code for performance, reducing bundle size, improving load times, or fixing performance bottlenecks. Emphasizes measurement-driven optimization.
plan
Create tactical implementation plan for a feature or task
professional-honesty
Use when responding to questions or providing information requiring professional honesty and directness over excessive agreeableness.
project-memory
Use when setting up or organizing Claude Code project memory (CLAUDE.md, .claude/rules/) for better context awareness, consistent behavior, and project-specific instructions.
proof-of-work
Use automatically during development workflows when making claims about tests, builds, verification, or code quality requiring concrete evidence to ensure trust through transparency.
refactor
Restructure code to improve quality without changing behavior
refactoring
Use when restructuring code to improve quality without changing external behavior. Emphasizes safety through tests and incremental changes.
review
Multi-agent code review with confidence-based filtering
simplicity-principles
Use when designing solutions, adding features, or refactoring by applying KISS, YAGNI, and Principle of Least Astonishment to write simple, predictable code.
solid-principles
Use during implementation when designing modules, functions, and components requiring SOLID principles for maintainable, flexible architecture.
structural-design-principles
Use when designing modules and components requiring Composition Over Inheritance, Law of Demeter, Tell Don't Ask, and Encapsulation principles that transcend programming paradigms.
technical-planning
Use when creating implementation plans for features or tasks. Focuses on tactical execution planning with clear tasks, dependencies, and success criteria.
test
Write tests for code using test-driven development principles
sre-incident-response
Use when responding to production incidents following SRE principles and best practices.
Page 1308 of 1434 · 71656 results