playwright-expert
Playwright E2E testing expert for browser automation, cross-browser testing, visual regression, network interception, and CI integration. Use for E2E test setup, flaky tests, or browser automation challenges.
Discover documentation testing skills, compare source repositories and read the instructions for each workflow.
Playwright E2E testing expert for browser automation, cross-browser testing, visual regression, network interception, and CI integration. Use for E2E test setup, flaky tests, or browser automation challenges.
Expert in Jest testing framework, advanced mocking strategies, snapshot testing, async patterns, TypeScript integration, and performance optimization
Testing expert with comprehensive knowledge of test structure, mocking strategies, async testing, coverage analysis, and cross-framework debugging. Use PROACTIVELY for test reliability, flaky test debugging, fr...
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without unders...
Create and maintain comprehensive test coverage with 80%+ business logic coverage, following TDD principles and proper test organization. Use when adding or improving tests. Focus on test strategy, coverage tar...
Vitest testing framework patterns for test setup, async testing, mocking with vi.*, snapshots, and test performance (formerly test-vitest). This skill should be used when writing or debugging Vitest tests. This...
Playwright testing best practices for Next.js applications (formerly test-playwright). This skill should be used when writing, reviewing, or debugging E2E tests with Playwright. Triggers on tasks involving test...
Test-Driven Development methodology and red-green-refactor workflow (formerly test-tdd). This skill should be used when practicing TDD, writing tests first, designing tests before implementation, or reviewing t...
MSW (Mock Service Worker) best practices for API mocking in tests (formerly test-msw). This skill should be used when setting up MSW, writing request handlers, or mocking HTTP APIs. This skill does NOT cover ge...
Use when writing or changing tests, adding mocks - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
Use to audit test quality with Google Fellow SRE scrutiny - identifies tautological tests, coverage gaming, weak assertions, missing corner cases. Creates bd epic with tasks for improvements, then runs SRE task...
Use when implementing features or fixing bugs - enforces RED-GREEN-REFACTOR cycle requiring tests to fail before writing code
Systematically inspect unit and E2E tests to verify they test the right behavior, provide meaningful coverage, and catch real regressions
Automated webapp testing with Playwright. Server management, UI testing, visual debugging, and reconnaissance-first approach.
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
Write the test first, watch it fail, write minimal code to pass
Add new example use cases to the Examples feature
Run tests with local database setup and repository pattern
Use this skill for browser automation, E2E testing, visual regression testing, and web application testing with Playwright or similar tools.
Write tests for Dojo models and systems using spawn_test_world, cheat codes, and assertions. Use when testing game logic, verifying state changes, or ensuring system correctness.
Generate workflow templates with coherent node graphs and integration tests
Your approach to handling testing unit tests. Use this skill when working on files where testing unit tests comes into play.
Your approach to handling testing coverage. Use this skill when working on files where testing coverage comes into play.
Your approach to handling testing test writing. Use this skill when working on files where testing test writing comes into play.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.