security-testing-patterns
Security testing patterns including SAST, DAST, penetration testing, and vulnerability assessment techniques. Use when implementing security testing pipelines, conducting security audits, or validating application security controls.
test-driven
TDD methodology for production-quality tests. Write tests FIRST driven by PRD, Tech Spec, Implementation Plan. Covers minimal mocking, realistic test data, strong assertions, test independence.
hono-testing
Hono testing patterns - app.request(), test client, mocking environment, and integration testing strategies
scrum-event-sprint-review
Verify Definition of Done and acceptance criteria for Sprint increments. Use when completing sprints, running verification commands, or preparing for acceptance.
load-test-scenario-builder
Creates comprehensive load test plans with realistic scenarios, traffic models, k6 scripts, and success criteria. Use for "load testing", "performance testing", "capacity validation", or "stress testing".
validator-role-skill
Professional software QA and code review skill for ensuring code quality, comprehensive test coverage, standards compliance, and security through rigorous testing and validation workflows.
dev-swarm-code-test
Create and execute comprehensive tests including unit tests, integration tests, CLI tests, web/mobile UI tests, API tests, and log analysis. Find bugs, verify requirements, identify improvements, and create change/bug/improve backlogs. Use when testing implementations or ensuring quality.
testing-test-writing
Write focused tests for core user flows and critical business logic, testing behavior rather than implementation, with clear names and fast execution. Use this skill when writing unit tests, integration tests, or end-to-end tests. When testing critical user workflows and primary application features. When creating tests that focus on what code does rather than how it does it. When mocking external dependencies like databases, APIs, or file systems. When naming tests to clearly describe the scenario and expected outcome. When keeping tests fast and independent. When completing feature implementation and adding strategic tests at logical completion points. When working with test files or test frameworks.
route-tester
Test authenticated routes in the your project using cookie-based authentication. Use this skill when testing API endpoints, validating route functionality, or debugging authentication issues. Includes patterns for using test-auth-route.js and mock authentication.
qa-engineer
QA Automation Engineer skill. Use this to write or refactor unit tests. Ensures tests follow the project's xUnit, FluentAssertions, and Moq standards.
quality-assurance
Comprehensive quality assurance combining testing strategy, code quality enforcement, and validation gates. Consolidated from testing-strategist, code-quality-enforcer, and validation-gate-checker.
test
Test strategy and execution. Create test plans, run test suites, or fix failing tests. Use when asked to "run tests", "create test strategy", "fix failing tests", "check coverage", or when you need to verify code works. Supports vitest, playwright, jest, and cypress.
testing-workflows-with-subagents
Use when creating or editing commands, orchestrator prompts, or workflow documentation before deployment - applies RED-GREEN-REFACTOR to test instruction clarity by finding real execution failures, creating test scenarios, and verifying fixes with subagents
analyzing-unit-tests
Use when analyzing unit test coverage, patterns, and test code for isolated component testing
rbac-policy-tester
Creates comprehensive permission tests ensuring RBAC doesn't regress with test matrices, CI gating, and authorization coverage. Use for "RBAC testing", "permission tests", "authorization testing", or "access control tests".
vitest-dom
Use vitest + jsdom for fast, lightweight unit tests for front-end apps
playwright-browser-run-code
To run a custom Playwright script on the page, execute a code snippet for advanced interactions.
data-seeding-fixtures-builder
Generates deterministic seed data for development and testing with factory functions, realistic fixtures, and database reset scripts. Use for "data seeding", "test fixtures", "database seeding", or "mock data generation".
storybook-setup
Sets up Storybook for component documentation with controls, actions, accessibility testing, and visual regression. Use when users request "Storybook setup", "component documentation", "UI library", "component stories", or "design system docs".
component-testing
Guide for testing C components in the SPLED environment using GTest/GMock. Use when user needs to design test cases, write tests, debug test failures, add test traceability, or understand testing strategy for a component. Covers test design, traceability to requirements, mock setup, and debugging patterns.
laravel-tdd
Test-Driven Development specifically for Laravel applications using Pest PHP. Use when implementing any Laravel feature or bugfix - write the test first, watch it fail, write minimal code to pass.
integration-test-authoring
This skill should be used when creating new integration tests for Breenix kernel features. Use for writing shared QEMU tests with checkpoint signals, creating xtask test commands, adding test workflows, and following Breenix testing patterns.
