performance-test-generator
ๅบไบNFRๆง่ฝ่ฆๆฑ๏ผ็ๆๆง่ฝๆต่ฏๅบๆฏๅๅ ณ้ฎๆง่ฝๆๆ ๏ผKPI๏ผใL3็บงๅซไธ็จ๏ผๅฝๆง่ฝ้ๆฑๆ็กฎๅไฝฟ็จใ
ๅบไบNFRๆง่ฝ่ฆๆฑ๏ผ็ๆๆง่ฝๆต่ฏๅบๆฏๅๅ ณ้ฎๆง่ฝๆๆ ๏ผKPI๏ผใL3็บงๅซไธ็จ๏ผๅฝๆง่ฝ้ๆฑๆ็กฎๅไฝฟ็จใ
Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization
You are the quality assurance architect ensuring Leavn's critical paths are protected by tests.
Execute Baldrick iterations on existing specs. Use when: run baldrick, execute specs, implement features, start working. Triggers on: baldrick run, run specs, implement, execute features.
Creating Storybook documentation with proper stories, argTypes, model instances, and variations
Writes comprehensive test cases following testing best practices. Use when writing tests, creating unit tests, or asking about test coverage.
Compares code implementation against specifications and requirements. Verifies functional requirements, non-functional requirements, acceptance criteria, and technical specifications are met. Returns structured reports of specification gaps and misalignments.
Use when developing tests or refactoring test suites - run tests in watch mode with focused file patterns to get instant feedback on specific test files without running the entire suite
Evaluate browser screenshots and page state for errors. Use when verifying features work correctly, detecting error conditions, or validating UI state during browser testing.
API integration testing with Supertest and Vitest. Use when testing API endpoints.
Use when implementing features/bugfixes to enforce strict TDD discipline - enforces RED (write failing test), GREEN (minimal code), REFACTOR cycle with no exceptions. Prevents "test after" trap, catches rationalizations. Activates when user says "implement", "let's code", "write this feature", mentions "TDD", or during spec-driven execution phase.
Python 3.13+ ๊ฐ๋ฐ ์ ๋ฌธ๊ฐ๋ก์ FastAPI, Django, async ํจํด, ๋ฐ์ดํฐ ๊ณผํ, pytest๋ฅผ ์ฌ์ฉํ ํ ์คํ , ๊ทธ๋ฆฌ๊ณ ํ๋์ Python ๊ธฐ๋ฅ์ ๋ค๋ฃธ. Python API, ์น ์ ํ๋ฆฌ์ผ์ด์ , ๋ฐ์ดํฐ ํ์ดํ๋ผ์ธ ๊ฐ๋ฐ ๋๋ ํ ์คํธ ์์ฑ ์ ์ฌ์ฉ.
Guide for writing Go tests following this project's patterns including httptest, test organization, and coverage requirements.
Level 1 patterns - test-watch, integration-test, complexity, loc, duplicates, slowtests
Strict TDD state machine with Result types. 7-state workflow (PLANNING, RED, GREEN, REFACTOR, VERIFY, BLOCKED, VIOLATION). Every message MUST announce state. Integrates with fn(args, deps), vitest-mock-extended, and typed error handling.
Use when designing or refactoring automated tests to make them high-signal, reliable, and maintainable across unit, integration, and end-to-end suites.
Use when the user asks to run performance tests, check for performance regressions, validate performance, or stress test event sourcing. Handles LOCAL mode (runs API locally) and REMOTE mode (targets deployed servidor API). Supports concurrent update tests, high-volume throughput tests, and combined stress tests. Delegates to the perf-test-runner sub-agent. Trigger phrases include "run perf test", "run remote perf test", "run concurrent perf tests", "run high-volume tests", "stress test event sourcing", "test concurrent updates", "validate throughput".
Cypress E2E testing standards including framework adaptations, test organization, and best practices
Use when implementing any feature or bugfix. Write the test first, watch it fail, write minimal code to pass. Red-Green-Refactor cycle.
Webๅบ็จๆต่ฏๅทฅๅ ทๅ ใไฝฟ็จ Playwright ่ฟ่กๅ็ซฏ่ชๅจๅๆต่ฏใUI ่ฐ่ฏใๆชๅพๆ่ทใๆต่งๅจๆฅๅฟๆฅ็ใๅฝ้่ฆๆต่ฏๆฌๅฐ Web ๅบ็จใ้ช่ฏๅ็ซฏๅ่ฝใ่ฐ่ฏ UI ่กไธบๆถไฝฟ็จๆญคๆ่ฝใ