Найдите подходящую возможность для вашего агента.
Integration testing patterns for ABP Framework APIs using xUnit and WebApplicationFactory. Use when: (1) testing API endpoints end-to-end, (2) verifying HTTP status codes and responses, (3) testing authorization, (4) database integration tests.
Write failing unit tests for feature requirements (TDD style)
Writes unit tests for JavaScript/TypeScript and frontend projects using Vitest or Jest. Use when writing or running tests.
Use when capturing screenshots, automating browser interactions, or scraping web content. Covers Playwright Python API for page navigation, screenshots, element selection, form filling, and waiting strategies.
实现任何功能或修复 bug 时使用，在编写实现代码之前先写测试。Use when implementing any feature or bugfix - write the test first, watch it fail, write minimal code to pass. TDD 红绿重构循环。
Test and validate API contracts against specifications
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when writing UI tests, recording interactions, tests have race conditions, timing dependencies, inconsistent pass/fail behavior, or XCTest UI tests are flaky - covers Recording UI Automation (WWDC 2025), condition-based waiting, network conditioning, multi-factor testing, crash debugging, and accessibility-first testing patterns
Use when encountering any bug, test failure, or unexpected behavior before proposing fixes
Implements user stories by reading requirements, following coding standards, and executing tasks with comprehensive testing. Updates story files with implementation details and test results.
Verify web application changes work by launching the app stack and testing in a real browser. This skill should be used when the user asks to "verify the change", "test in browser", "check if it works", or after completing a PR to validate the implementation. Requires Playwright MCP server. MUST exit if Playwright MCP is unavailable.
Reproduce, isolate, and fix a bug (or failing build/test), then summarize root cause, fix, and verification steps.
Phase 4 of disciplined development. Verifies implementation against design through unit and integration testing. Builds traceability matrices, tracks coverage, and loops defects back to originating left-side phases.
Use when implementing any feature or bugfix, before writing implementation code - write the test first using REAL systems (NO MOCKS), watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first and real system integration
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.
Use when tests fail intermittently. Replace arbitrary timeouts with condition polling. Eliminates flaky tests caused by timing assumptions.
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.
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.
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.
