playwright-test
Writing Playwright E2E tests following project patterns and fixtures. Use when creating new E2E tests, debugging test failures, or setting up test helpers and page objects.
Writing Playwright E2E tests following project patterns and fixtures. Use when creating new E2E tests, debugging test failures, or setting up test helpers and page objects.
Combines Ralph Wiggum loops with structured feature plans for automated TDD-driven development. Creates phase-based plans with quality gates, then executes each phase using Ralph loops with Beads for persistent state tracking. Includes E2E testing with Playwright agents. Use for automated overnight development, complex feature implementation, or when you want AI to iterate until tests pass.
Docker-based testing with testcontainers. Use when running tests with real databases.
Your approach to handling testing sybil. Use this skill when working on files where testing sybil comes into play.
Define comprehensive testing strategies, write tests with proper naming conventions, organize tests by type, and implement mocking strategies. Use when creating tests, refactoring test suites, or improving test coverage.
Expert-level C# unit testing skill based on ISTQB standards and best practices. Use this skill when creating, reviewing, or refactoring unit tests for C# applications (.NET/ASP.NET Core). Applies test design techniques, coverage strategies, and quality assurance principles from ISTQB Foundation and Advanced levels.
実装のテスト、リファクタリング、ポータビリティ、ディレクトリ階層について議論する際に、絶対パスが実装コードに存在しないことを確認する
Optimizes Playwright E2E tests by removing waitForTimeout anti-patterns, implementing smart waits, and enabling test sharding for parallel execution. Use when tests timeout, CI execution exceeds limits, or test reliability issues occur.
End-to-end testing patterns with Playwright. Use when writing or debugging E2E tests, focusing on reliability, isolation, and flakiness prevention.
Vue 3 and Nuxt 3 development with TDD workflow, QA gates, and E2E test generation. Enforces unit testing before implementation, generates Playwright E2E tests from Gherkin acceptance criteria, and produces JSON reports.
Software testing guidance with decision tree. Use when: (1) Writing or improving tests, (2) User asks about testing approaches, (3) Need guidance on test scope or assertions, (4) Working with specific test frameworks. Routes to specialized testing strategies via reference files.
Runs tests and explains results. Use when user asks to run tests, check tests, or verify code works.
Validate at every layer data passes through to make bugs impossible
How tests should be structured, named, and prioritized in this codebase.
Write effective tests with proper structure and coverage. Use when writing unit tests, integration tests, or improving test quality.
Create scenario files for testing migrated Output SDK workflows. Use to set up test inputs in the scenarios/ subfolder.
Generate an end-to-end test for a given feature or user story. Use when the user asks to create E2E tests, automate workflows, test user flows, or convert manual workflows into Playwright tests. Leverages Playwright MCP to perform the workflow interactively before generating test code.
Validate at every layer data passes through to make bugs impossible
Diagnose and resolve E2E test failures in Playwright. This skill should be used when E2E tests fail and need investigation, when Playwright test errors require root cause analysis, or when test failures need to be reproduced in the browser for debugging. Orchestrates MCP tools (Playwright, Chrome DevTools, Serena) and delegates code fixes to specialized agents.