cypress-test-generator
Generate Cypress E2E test files and configuration for web application testing. Triggers on "create cypress test", "generate cypress config", "e2e test for", "cypress setup".
writing-tests
Principles for writing effective, maintainable tests. Covers naming conventions, assertion best practices, and comprehensive edge case checklists. Based on BugMagnet by Gojko Adzic.
prd-to-test
PRD(์๊ตฌ์ฌํญ)๋ฅผ ๋ถ์ํ์ฌ ํ ์คํธ ์ผ์ด์ค๋ฅผ ๋์ถํฉ๋๋ค. TDD์ ์์์ ์ผ๋ก, ๊ตฌํ ์ ์ ํ ์คํธ ์๋๋ฆฌ์ค๋ฅผ ์ ์ํฉ๋๋ค. Inside-Out TDD ์ ๊ทผ๋ฒ ์ ์ฉ.
cui-java-unit-testing
CUI Java unit testing standards and patterns with JUnit 5, generators, and value object testing
user-simulation-test
Rules and patterns for simulating real user behavior in E2E tests. Covers UI interactions, API flows, and scenario-based testing strategies.
test-generator
Generate comprehensive test cases for code. Use when writing unit tests, integration tests, or test suites. Creates tests that cover happy paths, edge cases, error conditions, and follow testing best practices for the project's testing framework.
multi-ai-testing
Test-driven development with independent verification to prevent test gaming. TDD workflows, test generation, coverage validation (โฅ80% gate, โฅ95% target), property-based testing, edge case discovery. Use when implementing TDD workflows, generating comprehensive test suites, validating test coverage, or preventing test gaming through independent multi-agent verification.
playwright-skill
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
openwebf-app-testing-vitest
Set up and improve WebF app tests with Vitest and React Testing Library. Use when the user mentions Vitest, React Testing Library, unit tests, component tests, โtesting trophyโ, or asks to add/fix tests in a Vite/React/TS WebF app.
write-unit-test
Generate behavioral unit tests from functional specifications using PreDB/PostDB pattern. Use when user provides specs with Preconditions/Workflow/Postconditions structure or asks to write tests for a specification before implementation (TDD approach).
tdd
AL test development patterns with telemetry verification. MANDATORY when: (1) planning test implementation, (2) creating new tests, (3) modifying existing tests. Invoke proactively at ALL three stages. PLANNING: Structure plans with Red-Green-Refactor phases and use TodoWrite to track progress through each phase. CRITICAL RULE: DEBUG-* telemetry must be ZERO at both task START and END.
app-test-workflow
Flutter ์ฑ ํ ์คํธ ์ํฌํ๋ก์ฐ๋ฅผ ์์ํฉ๋๋ค. ํ ์คํธ ๊ณํ ์๋ฆฝ -> ์๋ฎฌ๋ ์ดํฐ ํ ์คํธ -> ์คํจ ์ ๋๋ฒ๊ทธ ์์ -> ์ฌํ ์คํธ ์์๋ก ์งํํฉ๋๋ค. "์ฑ ํ ์คํธ ์ํฌํ๋ก์ฐ", "/app-test-workflow", "์ฑ ํ ์คํธ" ๋ฑ์ ๋ช ๋ น์ผ๋ก ํ์ฑํ๋ฉ๋๋ค.
qt-unittest-make
Use when users request generating unit tests for Qt modules or classes, completing test cases, or creating test files. Supports module batch generation and incremental completion.
testing
REQUIRED for ANY interaction with test files (.test.ts, .test.tsx). Use when creating tests, modifying tests, debugging test failures, reviewing test code, refactoring tests, or implementing TDD workflow. Must invoke before writing, reading, or changing any test file.
playwright
How to make good playwright (e2e) tests for this project.
mock-authoring
Writing effective dry_run.py mocks for workflow testing without external dependencies
test-driven-development
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
integration-test-patterns
Best practices for writing integration tests using Testcontainers and EF Core. Use when creating or modifying integration tests.
unit-testing
Writing unit tests with vitest and vue-test-utils following project patterns. Use when creating tests for components, composables, utilities, or stores.
bitzero-methodology
Strategies for exploring and testing tightly-coupled BitZero code. Use when code seems untestable, has singleton dependencies, or you need to understand complex game logic before writing tests.