Testing & Security

Use when adding interaction testing to Storybook stories. Enables automated testing of component behavior, user interactions, and state changes directly in stories.

Use when managing test state and infrastructure with reusable Playwright fixtures and lifecycle hooks for efficient test setup and teardown.

Use when writing shell scripts following modern best practices. Covers portable scripting, Bash patterns, error handling, and secure coding.

Use when implementing Kubernetes security best practices including RBAC, pod security policies, and network policies.

Use when working with TestNG annotations, assertions, test lifecycle, and configuration for Java testing.

Use when pytest plugin ecosystem including pytest-cov, pytest-mock, and custom plugin development.

Use when working on Claude Code plugins (creating, modifying, testing, releasing, or maintaining) - provides streamlined workflows, patterns, and examples for the complete plugin lifecycle

Use when writing new functions, adding features, fixing bugs, or refactoring by applying TDD principles - write failing tests before implementation code, make them pass, then refactor.

Use when creating custom Ameba rules for Crystal code analysis including rule development, AST traversal, issue reporting, and rule testing.

Use when applying Behavior-Driven Development patterns including Given-When-Then structure, feature files, and acceptance criteria. Use when writing BDD-style tests and specifications.

Use when Effect dependency injection patterns including Context, Layer, service definitions, and dependency composition. Use for managing dependencies in Effect applications.

Use when vitest configuration, Vite integration, workspace setup, and test environment configuration for modern testing.

Use when building modular Angular applications requiring dependency injection with providers, injectors, and services.

Use when mocha configuration including reporters, config files, plugins, and CI integration.

Use when assertion libraries for Mocha including Chai with expect, should, and assert styles.

Use when implementing data-driven tests with TestNG DataProviders, factory methods, and parameterization patterns.

Fix bugs, add features to completed plugins. Includes versioning, backups, regression testing, changelog automation. Auto-detects deep-research handoffs to preserve investigation context. Trigger terms - improve, fix, add feature, modify plugin, version bump, rollback

Use when configuring parallel test execution with TestNG including thread pools, suite configuration, and synchronization.

Use when configuring Docker environments for act, selecting runner images, managing container resources, or troubleshooting Docker-related issues with local GitHub Actions testing.

Use when rSpec fundamentals including describe, context, it blocks, let, and basic matchers for BDD testing.