tdd

Test-driven development requires writing a failing test for a new feature first, then writing minimal code to pass it, and finally refactoring safely. This Skill guides you through that exact workflow to ensure reliable, maintainable code from the outset.

To avoid horizontal slicing during TDD workflows, focus on building vertical slices that deliver complete, testable functionality. This Skill helps identify and prevent such anti-patterns by enforcing robust test design and disciplined module structuring.

Refactoring in a test-driven development cycle is needed immediately after writing minimal code to pass a test. This Skill provides best practices for safely modifying your code structure while maintaining software quality and ensuring existing tests continue passing.

Yes, you can use this TDD guidance to maintain existing software quality by structuring your test-first approach to verify code changes. It ensures refactors are safely performed and code modifications are validated through effective tests.

Shallow module design causes problems in test-driven development by creating weak abstractions and harder-to-test code. This Skill helps prevent such pitfalls by emphasizing best practices for writing effective tests and maintaining robust vertical slices.

No, this test-driven development workflow does not require specific testing frameworks or dependencies. It provides language-agnostic best practices for planning, writing, and refactoring tests aligned with core TDD principles.