Discover documentation testing skills, compare source repositories and read the instructions for each workflow.
Assist QA Engineers with test planning, test case generation from acceptance criteria, coverage analysis, and regression test identification. Use when creating test plans, generating test cases, analyzing test...
Mocks APIs with Mock Service Worker including request handlers, server/browser setup, and testing integration. Use when mocking APIs in tests, developing without backend, or simulating network conditions.
Generates test cases, creates mocks, identifies edge cases, analyzes coverage gaps, and supports property-based, mutation, and contract testing. Use when writing tests, improving coverage, detecting flaky tests...
Tests JavaScript and TypeScript applications with Jest test runner including mocking, snapshot testing, and code coverage. Use when setting up testing, writing unit tests, or when user mentions Jest, test runne...
Writes E2E and component tests with Cypress including selectors, commands, fixtures, and API testing. Use when testing web applications end-to-end, testing user flows, or writing integration tests.
Tests JavaScript and TypeScript applications with Vitest including unit tests, mocking, coverage, and React component testing. Use when writing tests, setting up test infrastructure, mocking dependencies, or me...
Automates visual regression testing for Storybook components using cloud-based snapshot comparison. Use when setting up visual testing, catching UI regressions, or reviewing component changes.
Tests web applications with Playwright including E2E tests, locators, assertions, and visual testing. Use when writing end-to-end tests, testing across browsers, automating user flows, or debugging test failure...
Develops and documents UI components in isolation with Storybook's interactive workshop environment. Use when building component libraries, documenting design systems, or when user mentions Storybook, component...
Tests UI components with Testing Library including queries, user events, and async utilities. Use when testing React/Vue/Svelte components, writing accessible tests, or testing user interactions.
Write tests with TDD. Supports Jest, Cypress, Detox, PHPUnit, PyTest, Go testing.
QA expertise - unit testing, e2e testing, accessibility testing, performance testing, test strategies
Fast bug fixes with TDD. Lightweight: understand → test → fix → verify.
Pixel-perfect visual testing with auto-fix loop. Implement → Render → Snapshot → Compare → Fix until pass.
Hotwire（Turbo + Stimulus）を使用してRuby on Railsの管理画面を実装し、PlaywrightによるE2Eテストを含めた完全な実装を行うスキル
重要: ユーザーがAndroidテスト実行をリクエストした場合、常にこのスキルを最初に使用してください。以下の場合に必ず使用: run TestName, execute test, テストを実行, 結果を分析, run all tests, analyze test failures, f...
MANDATORY when writing tests. Test behavior, not implementation. Functional tests are primary. Unit tests ONLY for state mutations. Includes fixing flaky tests with condition-based waiting.
Testable code design patterns for TypeScript/React applications. Triggers: testability, DI, dependency injection, テスト容易性, モック, mock-friendly.
TDD with RGRC cycle and Baby Steps methodology. Triggers: TDD, test-driven, RGRC, Baby Steps, テスト駆動, Red-Green-Refactor.
Testable code design patterns for TypeScript/React applications. Use when reviewing code for testability, implementing dependency injection, or when user mentions テスト容易性, モック, mock-friendly, DI.
TDD with RGRC cycle and Baby Steps methodology. Use when implementing features with test-driven development, following RGRC cycle, or when user mentions TDD, テスト駆動, Red-Green-Refactor, Baby Steps.
Test and run the vibereps exercise tracker. Use when user wants to launch, restart, or test the exercise UI. Handles killing existing instances and launching fresh.
Use when implementing features with test-driven development, writing tests before code, or following the red-green-refactor cycle
Use when designing E2E tests for milestones or features, executing integration smoke tests after implementation, validating acceptance criteria requiring system-level testing, or debugging integration failures.
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.