browser-testing
Browser automation for testing IntelliFill. Replaces puppeteer MCP to save ~4.8k tokens.
Discover data ai testing skills, compare source repositories and read the instructions for each workflow.
Browser automation for testing IntelliFill. Replaces puppeteer MCP to save ~4.8k tokens.
End-to-end testing with Cypress and Playwright for IntelliFill. Use when writing E2E tests, custom commands, or CI integration.
Write tests for IntelliFill using Jest (backend) and Vitest (frontend). Use when adding unit tests, integration tests, or component tests.
Expertise for writing XCTest tests for Swift/SwiftUI iOS and macOS apps in this project. Use when writing tests for HabitQuest, AvoidObstaclesGame, CodingReviewer, MomentumFinance, PlannerApp, or Shared-Kit. Fo...
Write and run tests with Vitest for Vite-based projects. Use when testing Astro components, JavaScript modules, or any Vite project requiring fast, modern testing.
End-to-end browser testing patterns with Playwright. Use when writing integration tests, user flow testing, or browser automation.
Wrap third-party libraries for testability and replaceability. Use when integrating external APIs, creating testable code, or building swappable implementations.
Write tests for backend services, APIs, and database access. Use when testing Express/Fastify handlers, services with database calls, or integration tests.
Write unit tests for JavaScript files using Node.js native test runner. Use when creating new scripts, fixing bugs, or when prompted about missing tests.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Automates end-to-end testing and debugging of terminal UIs using Termwright. Use when testing TUI apps (ratatui, crossterm, ncurses), automating terminal interactions, capturing screenshots, or debugging termin...
Focused workflow for TUI E2E testing with Termwright. Use for fast agent guidance when running step files, capturing artifacts, and debugging with trace output.
Write pytest unit tests for Python code changes. Use when adding tests for new or modified Python code in projects that use pytest.
TDD patterns, test writing strategies, coverage guidance, mocking patterns. Use when: write tests, TDD, test coverage, unit test, integration test, E2E test, mocking, test organization, pytest, vitest, jest.
Ensure backend build readiness for Espresso Engineered. Use when backend code/config changes are made or when a feature/task is wrapping up to suggest running `npm run build:backend` (and tests only if requeste...
Run the test suite and report results
Use when creating formal specifications with acceptance criteria. Covers spec structure, pre/post-conditions, invariants, interface definitions, and formal acceptance testing requirements.
TypeScript testing conventions and TDD practices. Use when writing tests, fixing bugs, or organizing test files.
Table-driven testing patterns using @kitz/test. Triggers on creating test cases, parameterized tests, or when writing .test.ts files.
Integration test for /resolve-review skill. Creates fixtures, guides manual testing, verifies results.
Type assertion patterns using @kitz/assert. Triggers on type-level tests, .test-d.ts files, or when asserting TypeScript types.
Improve acceptance criteria so they are testable, unambiguous, and complete.
Add an MCP integration section (tools, auth, error handling, observability, tests) to an existing spec.
Build a pragmatic unit/integration/e2e test strategy aligned with a spec.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.