Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
Execute a specific task along with its sub-tasks systematically following a TDD development workflow. Use when implementing individual tasks from a spec.
TEST PHASE: Testing strategies, patterns, and quality assurance workflows. Provides test strategy frameworks, coverage guidelines, unit/integration/e2e patterns, performance testing approaches, and security testing checklists. Use when: designing test strategies, writing tests, evaluating coverage, planning QA workflows, implementing test automation.
Write reliable Playwright E2E tests following official best practices. Prioritizes user-facing locators, web-first assertions, and test isolation. NEVER mock application data. Avoid explicit waits unless component-specific. Use when writing, reviewing, or debugging Playwright tests.
Generate and configure Storybook 9 for any framework with automatic detection, SOTA best practices, and platform-specific optimizations (Web, Tauri, Electron)
Comprehensive guide to Rust automated testing covering unit, integration, and documentation tests. Includes practical patterns for async testing, property-based testing with proptest, mocking strategies using traits, and essential testing tools (cargo-nextest, criterion, tarpaulin). Emphasizes FIRST principles and CI/CD integration. Use this when: setting up new Rust projects, establishing testing standards for teams, improving existing test suites, implementing TDD workflows, or learning Rust testing ecosystem best practices. Particularly valuable for projects requiring high reliability and comprehensive test coverage.
Provides instructions to run the unit tests for project in a consistent and cost efficient way
Designs and implements pytest test suites for Python libraries with fixtures, parametrization, mocking, Hypothesis property-based testing, and CI configuration. Use when creating tests, improving coverage, setting up testing infrastructure, or implementing property-based testing.
Comprehensive Python testing with pytest framework, including test creation, fixtures, parameterized tests, and test execution. Use when Claude needs to work with Python testing for creating new tests, modifying existing tests, working with fixtures and test configuration, running tests with specific options, or debugging test failures.
Playwright MCPを使用してFirefox/WebKitなどChrome以外のブラウザでの動作確認を行います。クロスブラウザ互換性の問題を調査する際に使用します。
Generate comprehensive Pest test suites for Laravel projects including tests for controllers, services, Livewire components, commands, jobs, and models with proper describe blocks for organization, mocking setup, happy path and failure scenarios, RefreshDatabase trait, and coverage for all public methods. Use this skill when creating test files for new features, adding test coverage for controllers or services, writing tests for API endpoints, testing Livewire components, ensuring proper test structure with beforeEach and describe blocks, implementing mocking strategies, or writing dataset-driven tests. This skill applies when working on files in tests/Feature/ or tests/Unit/ directories, creating Pest test files, or ensuring comprehensive test coverage.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Analyze test failures and suggest fixes for Feature Swarm verification. Use when tests fail during the verification phase to diagnose root cause and determine if automatic recovery is possible.
Comprehensive guidance for writing high-quality unit tests in Java projects using JUnit 5 and AssertJ. Use when writing unit tests, creating test classes, or need guidance on mocking strategies, assertions, test builders, or JUnit 5 best practices. Requires JUnit 5, AssertJ, and Mockito dependencies.
Enforce test-first development with Red-Green-Refactor cycle. Use when (1) implementing new features in production code, (2) fixing bugs (write test that reproduces bug first), (3) refactoring code (ensure tests exist before changing behavior). Skip for exploratory research scripts or throwaway prototypes.
TDDサイクルを加速させるため、実装前に網羅的なテストシナリオとエッジケースを生成します。
Orchestrate evolution of educational demos through multi-agent exploration. NEW WORKFLOW: First develop test cases, then spawn builders, then evaluate with Chrome E2E testing. Test cases define LEARNING outcomes to verify.
Best practices for E2E testing. Use when writing or debugging Playwright tests.
Use when extracting structured data from websites using Playwright MCP tools, when handling login/authentication flows, when crawling paginated content, or when building scrapers that navigate dynamic SPAs with tabs, accordions, or React/HeadlessUI components
Standard procedure for creating reusable pytest fixtures in conftest.py files for the airline-discount-ml project.
Use when building Chrome extensions (Manifest V3). Covers floating panel architecture, sidepanel API, storage patterns, message passing, content scripts, SPA navigation detection, context menus, Vitest testing, Playwright E2E, and common pitfalls.
Browser automation for testing and verification. Use after building or modifying web UI to verify changes work. Uses Playwright's accessibility tree, not pixel-based input. LLM-friendly: no vision models needed, operates purely on structured data. Deterministic tool application avoids ambiguity common with screenshot-based approaches. Triggers: testing localhost, verifying UI changes, checking if a feature works, taking screenshots, debugging console errors, testing form submission, end-to-end verification, "does it work", "let me check the browser", "test the app", browser automation, web testing.
Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization
