Orchestrates test planning pipeline: research, manual testing, automated test planning. Use when Story needs comprehensive test coverage planning.
Performs manual testing of Story AC via executable bash scripts in tests/manual/. Use when Story implementation needs hands-on AC verification.
Plans automated tests (E2E/Integration/Unit) using Risk-Based Testing after manual testing. Use when Story needs a test task with prioritized scenarios. — from engineering/testing
Use when auditing the test surface through the evaluation platform with mandatory research, coordinated test audit workers, and structured summaries.
Detects tests validating framework/library behavior instead of project code. Use when auditing test business logic focus.
Validates E2E coverage for critical paths (money, security, data integrity). Risk-based prioritization. Use when auditing E2E test coverage.
Scores each test by Impact x Probability, returns KEEP/REVIEW/REMOVE decisions. Use when auditing test value and pruning low-value tests.
Identifies missing tests for critical paths (money, security, data integrity, core flows). Use when auditing test coverage gaps.
Checks test isolation (API/DB/FS/Time/Network), determinism, flaky tests, order-dependency, anti-patterns. Use when auditing test isolation.
Checks manual test scripts for harness adoption, golden files, fail-fast, config sourcing, idempotency. Use when auditing manual test quality.
Checks test file organization, directory layout, test-to-source mapping, domain grouping, co-location. Use when auditing test structure.
Audits assertion strength and test oracles that prove real defects. Use when finding weak tests that execute code but prove little.
Sets up test infrastructure with Vitest, xUnit, and pytest. Use when adding testing frameworks and sample tests to a project.
Executes all test suites and reports results with coverage. Use when verifying that test infrastructure works after bootstrap.
Executes optimization hypotheses with keep/discard testing loop. Use when applying validated performance improvements.
Replaces custom modules with OSS packages using atomic keep/discard testing. Use when migrating custom code to established libraries.
Disposable Lightning wallets via lncurl.lol. Use for temporary wallets, testing, or bootstrapping child agents.
Design a defensible load test — a realistic workload model, a deliberate test type, and SLO-tied pass/fail thresholds — instead of a meaningless tight-loop script that hammers one…
Planifie et exécute des tests de charge et performance. Se déclenche avec "test de charge", "load test", "stress test", "performance test", "k6", "JMeter", "Gatling", "be — from…
Creates comprehensive load test plans with realistic scenarios, traffic models, k6 scripts, and success criteria.
Load Test Scenario Planner - Auto-activating skill for Performance Testing. Triggers on: load test scenario planner, load test scenario planner Part of the Performance Testing…
Tester les performances sous charge. Utiliser quand on mesure la capacité du système ou optimise les temps de réponse.
Run load tests and profile applications with Locust, py-spy, and database query analysis
Execute comprehensive load and stress testing to validate API performance and scalability. Use when validating API performance under load.
k6 script templates, load profiles, response time thresholds, SLO validation, and performance testing strategies.
Write a load and performance testing plan for a service. Use when asked to create a performance test plan, write load testing documentation, define stress or soak test sc — from…
부하 테스트 자동화 하네스(loadtest-harness)를 end-to-end 실행한다 — 사전 점검 → run.py 실행(시나리오·회차 선택) → 생성된 리포트 요약까지. 사용자가 "부하 테스트 돌려줘", "하네스 실행", "knee-point 테스트 실행", "loadtest 돌려" 등을 요청할 때 사용.
Manage local Ollama LLM models for development and testing. Use when: running local models, configuring Ollama, switching between fast/quality models, optimizing VRAM usage,…
Use Clipboard's internal CLI to link and unlink @clipboard-health packages across repositories for local development.
Local testing setup - start dev server with mock Claude and run tests (unit tests, CLI E2E)
Internationalization (i18n) and localization (l10n) testing for global products including translations, locale formats, RTL languages, and cultural appropriateness.
Use Lockplane for safe database schema management - define schemas in .lp.sql files, validate, and apply with shadow DB testing
Locust Test Creator - Auto-activating skill for Performance Testing. Triggers on: locust test creator, locust test creator Part of the Performance Testing skill category.
Run the Lofn image/visual pipeline (steps 00–10) backed by Codex — contest-grade, render-ready image prompts (Flux noun-first by default, GPT-Image-2 directive mode optional).
Pure logic and math testing with Vitest. Use for single-point assertions on functions, state transitions, and physics calculations.
Create a minimal working Lokalise example. Use when starting a new Lokalise integration, testing your setup, or learning basic Lokalise API patterns.
Use when a browser-run UI or client claim needs real runtime observation: visual state, DOM, accessibility tree, console, network, CORS, viewport, screenshot, or browser…
End-to-end testing for web applications with Playwright, Cypress, Selenium, and Puppeteer. Use for setting up E2E tests, debugging failures, improving reliability, and…
Performance and load testing with k6, locust, JMeter, Gatling, and artillery. Use for load/stress/spike/soak tests, API and database benchmarking, profiling, p95/p99 latency…
Use when implementation should be driven by test-first verification: a focused executable check can fail before the change, pass after it, and provide evidence for a behavior,…
Test strategy guidance — test pyramid design, coverage goals, categorization, flaky test diagnosis, infrastructure architecture, and risk-based prioritization.
Triage and analyze any LUCI build results (including tests and compile). Supports finding builds by CL, failure listing, and log fetching.
Create Lunar policy plugins that enforce engineering standards. Use when building policies (Python scripts) that evaluate Component JSON data and produce pass/fail checks.
Call Apex methods imperatively from LWC — on button click, lifecycle hooks, or conditional logic. Covers import syntax, cacheable vs non-cacheable, async/await patterns, error…
Use when setting up or reviewing Lightning Web Component unit tests with Jest, including `@salesforce/sfdx-lwc-jest`, wire adapter mocks, imperative Apex mocks, async rerender…
One-shot XCUITest scaffolding for macOS SwiftUI apps. Audits the project, generates ranked TIER-1/2/3 test stubs, suggests accessibility identifiers with batch confirmation, and…
Triage failing macOS tests across Xcode and SwiftPM workflows. Use when asked to run macOS tests, narrow failing scopes, explain assertion or crash failures, or separate — from…
Mobile E2E testing and live device control with Maestro MCP. Use when: implementing mobile features, debugging React Native apps, verifying UI on simulators/emulators, writing E2E…
Multi-perspective deliberation (Logos/Pathos/Sophia) for architecture arbitration, trade-offs, Go/No-Go, and strategic decisions. Does not write code.
Multi-perspective decision support using three AI agents (Scientist, Mother, Realist). Use when facing difficult decisions, trade-offs, comparing alternatives, choosing between…
MailDev is a local SMTP server with a web UI and REST API for capturing application email during development.
MailDev is a local SMTP server with a browser UI for viewing test emails during development. It catches outgoing mail, exposes a REST API, supports attachments and relay options,…
Uses MailHog to capture outbound email in development and test environments through a local SMTP server, browser UI, and JSON API.
Guides agents through integrating transactional email sending via Mailtrap's Email API, including sandbox testing, domain verification, and API authentication.
Capture outbound email in Mailtrap Email Sandbox for development, staging, CI, HTML inspection, spam checks, and fake inbox tests.
Keeps the Dev Playground current with the application. Use when editing UI components in apps/client/src/ — assesses playground candidacy, checks existing playground coverage, and…
Integrate MaintainX API testing into CI/CD pipelines. Use when setting up automated testing, configuring CI workflows, or implementing continuous integration for MaintainX…
Create a minimal working MaintainX example - your first work order. Use when starting a new MaintainX integration, testing your setup, or learning basic MaintainX API patterns.
Set up a local development loop for MaintainX integration development. Use when configuring dev environment, testing API calls locally, or setting up a sandbox workflow for…
Generate Makefiles with testing, linting, formatting, and automation targets for new projects.