Loading...
Loading...
Found 58 Skills
Use this skill when writing Playwright tests, implementing visual regression, testing APIs, or automating browser interactions. Triggers on Playwright, page object model, browser automation, visual regression, API testing with Playwright, codegen, trace viewer, and any task requiring Playwright test automation.
Generates bash/curl commands for fetching sample data from Hyperliquid API. Use when user wants curl examples, bash commands to test the API, or sample data fetch commands for mainnet.
Minimal smoke test for Security Center SAS skill. Validate read-only query flow.
Smoke test for alicloud-ai-search-milvus. Validate minimal authentication, API reachability, and one read-only query path.
Generate realistic mock API responses with fake data. Use for testing, prototyping, or creating sample data for frontend development.
Guide for adding new AI function examples, for testing specific features against the actual provider APIs.
Testing frameworks for web, mobile, API, and unit testing
Guides creation and modification of ASP.NET Core Web API endpoints with correct HTTP semantics, OpenAPI metadata, and error handling. USE FOR: adding new API endpoints (controllers or minimal APIs), wiring up OpenAPI/Swagger, creating .http test files, setting up global error handling middleware. DO NOT USE FOR: general C# coding style, EF Core data access or query optimization (use optimizing-ef-core-queries), frontend/Blazor work, gRPC services, or SignalR hubs.
Creates integration tests for API endpoints with database flows, including test harness setup, fixtures, setup/teardown, database seeding, and CI-friendly strategies. Use for "integration testing", "API tests", "database tests", or "test harness".
Use when asked to identify and fix errors in an OpenAPI specification that are preventing it from running as mock or test
Generate a Syndicate Links merchant test link and fire a synthetic test conversion using the shipped merchant test-link API. Avoids draft-only sandbox endpoints and avoids touching real affiliate payouts.
Surface-aware end-to-end verification of a change — determine whether it touches a FRONTEND surface (rendered UI) or an API/backend surface, then validate the right way. Frontend → chrome-devtools MCP (open the affected page, screenshot, confirm it renders, check console/network/accessibility). API → a Playwright request script that hits the affected endpoints and asserts status + response shape. Use after implementing a change, or in the harness Validate step, to confirm it actually works in the running app — not just that unit tests pass. Requires the chrome-devtools-mcp plugin (frontend) and/or Playwright (API); both are wired up by the kit installer.