e2e-testing
End-to-end testing with Cypress and Playwright for IntelliFill. Use when writing E2E tests, custom commands, or CI integration.
testing-test-writing
Write unit and integration tests following the project's testing patterns with Jest. Use this skill when creating test files (*.spec.ts), writing unit tests for DTOs and domain entities, writing integration tests for use cases and queries, setting up test fixtures, or using test utilities. This includes organizing tests in test/unit/ and test/integration/ directories, using proper test naming conventions, mocking external dependencies, and testing with real database transactions for integration tests. Apply when working with any *.spec.ts file, test fixtures, or implementing the project's test-behavior-not-implementation philosophy.
playwright-testing
Enforces Test-Driven Development workflow using Playwright. Use when user requests tests, validation, E2E testing, or implementation tasks.
condition-based-waiting
Use when tests fail intermittently. Replace arbitrary timeouts with condition polling. Eliminates flaky tests caused by timing assumptions.
core-tester
Comprehensive testing and quality assurance specialist for ensuring code quality through testing strategies
webapp-testing
Docker 환경에서 Playwright E2E 테스트 실행. 브라우저 미종료 문제 해결, 스크린샷, 로그 캡처 지원.
visual-testing
Design and implement visual regression testing for UI changes. Defines screenshot coverage, rendering stabilization, baseline management, and CI integration (e.g., Playwright screenshots, Percy/Chromatic). Use when UI/styling/layout changes need protection against regressions, or when adding screenshot-based tests to a web/WASM/desktop UI.
shannon-execution-verifier
Comprehensive post-build verification of Shannon Framework's application outputs using three-layer methodology: Flow Verification (execution trace analysis), Artifact Verification (physical output inspection), and Functional Verification (runtime testing). Verifies Shannon built production-ready applications across all domains (Frontend, Backend, Database, Mobile, DevOps). Ensures NO MOCKS compliance, cross-platform functionality, and complete integration. Use after: Shannon builds any application via /shannon:wave, need to verify build quality, production readiness assessment.
writing-skills
Use when creating reusable process documentation. Apply TDD: baseline without skill → document failures → write skill → test → iterate. Four types: Discipline, Technique, Pattern, Reference. Iron Law: No skill without failing test first.
test-routes
Test route configurations with integration-style tests. Use when testing complete request/response cycles through routes. Triggers on "test routes", "test note routes", "integration test".
lorairo-test-generator
Generate pytest unit, integration, and GUI tests for LoRAIro with proper fixtures, mocks, and 75%+ coverage using pytest-qt for PySide6 testing
plan-review
Use after plan is written to validate implementation plans across completeness, quality, feasibility, and scope dimensions - spawns specialized validators for failed dimensions and refines plan interactively before execution
playwright
End-to-end testing automation with Playwright for web applications
pytest-testing
Master test-driven development with pytest, fixtures, mocking, and CI/CD integration
test-repository
Guide for testing repository layer. Use when asked to test repositories or data access layer. Directs to implementation-specific testing skills.
browsing-with-playwright
Browser automation using Playwright MCP. Navigate websites, fill forms, click elements, take screenshots, and extract data. Use for web browsing, form submission, web scraping, or UI testing. NOT for static content (use curl/wget).
test-data-generation
Test data generation patterns using Bogus, test builders, and ABP seeders. Use when: (1) creating realistic test data, (2) implementing test data seeders, (3) building test fixtures, (4) generating fake data for development.
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
testing-patterns
Test design patterns, best practices, and examples for comprehensive Solidity testing. Use when writing tests for smart contracts or improving test coverage.
synpress-e2e
End-to-end testing with wallet automation using Synpress. Use this skill for testing dApp flows that require MetaMask/wallet interactions, transaction signing, and on-chain verification.
security-validation
Runtime security validation including secret scanning, PII detection, prompt injection defense, audit logging, and output validation for AI agents. Use when validating user input, scanning for secrets, detecting PII, preventing data exfiltration, or implementing security guardrails.
