আপনার এজেন্টের জন্য উপযুক্ত সক্ষমতা খুঁজে নিন।
Use when writing pytest tests, creating fixtures, mocking dependencies, or testing async code - provides patterns that verify actual behavior with proper fixtures and parametrization; prevents testing mocks instead of code (plugin:dev-python@pproenca)
Comprehensive testing strategies with Vitest, Jest, and Testing Library
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
Guides Rust backend test development with testcontainers, mockall, and axum-test. Use when writing integration tests, mocking dependencies, testing HTTP handlers, or setting up test infrastructure for Axum/SQLx projects.
Scala 3.6+ best practices with ScalaTest 3.2, sbt 1.10, functional programming
Run quick HTTP health/readiness smoke checks against one or more endpoints. Use to validate a service is up before running deeper E2E tests.
Parse ctest and sanitizer output, summarize failures, identify root causes, and track test coverage for Orpheus SDK builds.
Gates สำหรับ enforce API contract testing ระหว่าง services ด้วย Pact หรือ OpenAPI validation
Replace arbitrary timeouts with condition polling for reliable async tests
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
Write comprehensive tests following project conventions (tiers, patterns, anti-patterns). Use when writing tests, improving test coverage, fixing failing tests, or reviewing test quality.
Orchestrates test execution for the Nomos monorepo following TESTING_GUIDE.md standards. Use this when running tests, debugging test failures, validating coverage, or executing verification checklists from AGENTS.md files.
Enforces test-driven development (TDD) following Kent Beck's methodology. MANDATORY micro-cycle approach - write ONE test, watch it fail, write minimal implementation, refactor, then NEXT test. NEVER write all tests first or implementation first. Use for ANY code writing task.
Generates valid and invalid JSON fixtures for CommandDTO and DecisionDTO based on current contract schemas.
Creates and optimizes MSW (Mock Service Worker) handlers for Playwright E2E tests, implementing handler caching, fixture management, and AI Gateway mocking patterns. Use when mock setup is slow or test data needs centralization.
技術検証（Tech Spike）ワークフロー。ライブラリ選定やアーキテクチャ判断の前に最小限の実験コードで技術的妥当性を検証。 使用タイミング: (1) 複数の技術選択肢がある場合（ライブラリA vs B） (2) 新しいライブラリ・技術の学習コストが高い場合 (3) パフォーマンス・互換性の懸念がある場合 (4) 既存システムとの統合リスクがある場合 (5) 「技術検証」「ライブラリ調査」「スパイク」リクエスト 使用しない場合: 技術スタック確定済み、既知のパターン、単純なCRUD操作
Unit testing patterns for .NET applications using EF Core In-Memory Provider, AAA structure, test data helpers, and TDD workflows. Use when writing unit tests for Application Services, domain logic, or data access.
Validates API contracts for correctness, compatibility, and compliance. Tests REST APIs against OpenAPI/Swagger specifications. Detects breaking changes between versions, validates runtime responses against schemas, and ensures backward compatibility before deployment.
