What is the 'Golden Rule' of this skill?

The core principle is 'If it's not tested, it's not finished.' Claude will not consider a task complete until corresponding tests are written and passing.

Can it mock external APIs like Supabase?

Yes, it includes standardized patterns for mocking Supabase clients, authentication hooks, and asynchronous operations using Vitest.

Which testing frameworks are supported?

This skill is optimized for Vitest (unit/integration), Playwright (E2E), and node-mocks-http for API simulation.

How does it handle bug fixes?

For every bug fix, the skill mandates the creation of a regression test that specifically targets the reported issue to ensure it never returns.

Does it support TypeScript?

Yes, it includes mandatory TypeScript type-checking steps (npm run typecheck) as part of the validation checklist.

Rigorous Testing Protocol

Name: Rigorous Testing Protocol
Author: cityfish91159

bycityfish91159

Security & Testing

Enforces a strict testing-first methodology to ensure every code change is validated through unit, integration, and E2E tests.

About

The Rigorous Testing skill implements a comprehensive quality assurance framework for Claude Code, centered on the principle that code is not finished until it is tested. It provides a structured workflow for Test-Driven Development (TDD), covering everything from unit testing with Vitest and API mocking to end-to-end browser testing with Playwright. By automating pre-submission checklists and regression testing requirements, this skill ensures high-quality codebases with minimal technical debt and prevents bugs from reappearing after they've been fixed.

Key Features

Standardized unit testing patterns using Vitest and custom mocks
Automated regression testing requirements for every bug fix
End-to-End (E2E) testing protocols with Playwright for user flows
Enforces 'Test-First' development cycles (Red-Green-Refactor)
Comprehensive pre-commit checklists including coverage and type-checking
0 GitHub stars

Use Cases

Refactoring legacy code with a safety net of established test benchmarks
Preventing regressions by adding mandatory tests during bug fixes
Ensuring new features are fully covered by tests before deployment

About

Key Features

Standardized unit testing patterns using Vitest and custom mocks
Automated regression testing requirements for every bug fix
End-to-End (E2E) testing protocols with Playwright for user flows
Enforces 'Test-First' development cycles (Red-Green-Refactor)
Comprehensive pre-commit checklists including coverage and type-checking
0 GitHub stars

Use Cases

Refactoring legacy code with a safety net of established test benchmarks
Preventing regressions by adding mandatory tests during bug fixes
Ensuring new features are fully covered by tests before deployment