testing-guide
Testing architecture and best practices for the Flare Stack Blog. Use when writing, debugging, or refactoring tests with Vitest and Cloudflare Workers pool.
Discover blockchain testing skills, compare source repositories and read the instructions for each workflow.
Testing architecture and best practices for the Flare Stack Blog. Use when writing, debugging, or refactoring tests with Vitest and Cloudflare Workers pool.
A fake test skill for production registry publishing integration tests
Web/React interrogation using HAR + Playwright trace and endpoint mapping (behavior-first when sourcemaps absent).
Compile multiple run findings into a single report with cross-run diffs and stable conclusions.
Comprehensive testing guidance for RSSVibe project using TUnit framework, test organization, and HTTP client patterns. Use this skill when writing tests, running tests, or reviewing testing practices.
Integration testing patterns for API endpoints using real database and services with WebApplicationFactory and testcontainers. Use this skill when writing integration tests for endpoints.
Unit, integration, E2E testing and TDD practices
API testing, documentation, and development tools
Researches implementation approaches using browser automation via /chrome, then implements the best solution. Use when building new features, solving unfamiliar problems, or need to find best practices before i...
Generates TDD-ready acceptance criteria from screen spec.md. Extracts requirements from features, interactions, flows, and API mappings in Given-When-Then format. Use when creating implementation task specifica...
Guide Test-Driven Development using Kent Beck's Red-Green-Refactor cycle. Use when writing tests, implementing features via TDD, or following plan.md test instructions.
Component documentation, visual testing, interaction testing
TDD and unit testing guidance for Crispy CRM. Use when writing tests, implementing TDD, debugging test failures, or setting up test infrastructure. Covers Vitest patterns, React Admin component testing, Zod sch...
Evidence-based completion claims - BLOCKS claiming tests pass, builds succeed, features work, or tasks are done without running verification commands first. Enforces TDD for implementation tasks. Triggers on do...
Guide experienced developers on test structure, patterns, assertions, and test doubles for effective test-driven development
Guide experienced developers through TDD failure scenarios and recovery procedures when tests behave unexpectedly
Guide experienced developers through RED phase of TDD cycle - writing failing tests and verifying expected failures
Web application testing skill using Antigravity browser and Playwright CLI. Use for E2E testing, visual debugging, interaction testing, accessibility checks, and deep audit strategies. Supports both live browse...
Use when encountering any bug, test failure, or unexpected behavior before proposing fixes
Testing strategies for the 3SC widget host. Covers unit tests, integration tests, ViewModel testing, mocking patterns, and test organization.
Jest testing strategies, test organization, factory patterns for test data, mocking strategies for authentication and external services, real-time message processor testing, test-driven development workflow, un...
Visual QA checkpoint for conductor gates. Uses tabz MCP tools to check browser console errors, take screenshots, and identify obvious UI issues. Returns structured result with pass/fail status and captured scre...
Test runner checkpoint for conductor gates. Detects test framework (jest, pytest, cargo test, go test, etc.), runs tests, and captures output. Returns structured result with pass/fail status and failed test det...
Guides development, updates, and refactoring across the entire MCP server codebase. Use when adding features, updating categories, refactoring code, checking test coverage, or making any code changes. Enforces...
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.