Does this skill work with Event Sourcing patterns?

Yes, it includes specialized patterns for testing deciders (decide/evolve functions) and projections, ensuring your event-sourced architecture is fully verified.

Can I write multiple tests at once with this skill?

No, this skill strictly enforces the 'one test at a time' rule. You must write a single test, watch it fail, and pass it before moving to the next one to ensure incremental design.

When should I avoid using this TDD skill?

TDD enforcement is not required for non-functional files such as configuration (package.json), view templates, documentation, or basic build scripts.

What test runners does this skill support?

It is configured to work with 'bun test' and the native Node.js test runner using 'tsx' for TypeScript support.

Kent Beck TDD Enforcer

Name: Kent Beck TDD Enforcer
Author: narcisobenigno

bynarcisobenigno

セキュリティとテスト

Enforces strict test-driven development following Kent Beck’s micro-cycle methodology for robust code implementation.

概要

The TDD Enforcement skill transforms Claude into a disciplined software engineer by mandating the Red-Green-Refactor cycle. It strictly prevents writing implementation before testing and requires a micro-cycle approach where exactly one test is written and failed before any production code is touched. This process ensures high test coverage, drives better architectural decisions, and is particularly optimized for complex logic like event sourcing deciders and projections.

主な機能

Mandatory 'one test at a time' workflow to prevent over-engineering
0 GitHub stars
Automated test execution via Bun and Node.js test runners
Strict Red-Green-Refactor micro-cycle enforcement
Standardized naming conventions for implementation and spec files
Specific patterns for Event Sourcing deciders and projections

ユースケース

Refactoring legacy code while maintaining behavioral integrity through continuous testing
Developing new business logic and features with guaranteed test coverage
Systematically fixing bugs by creating a failing reproduction test first

概要

主な機能

Mandatory 'one test at a time' workflow to prevent over-engineering
0 GitHub stars
Automated test execution via Bun and Node.js test runners
Strict Red-Green-Refactor micro-cycle enforcement
Standardized naming conventions for implementation and spec files
Specific patterns for Event Sourcing deciders and projections

ユースケース

Refactoring legacy code while maintaining behavioral integrity through continuous testing
Developing new business logic and features with guaranteed test coverage
Systematically fixing bugs by creating a failing reproduction test first