tdd-workflow

This skill ensures all code development follows TDD principles with comprehensive test coverage. ALWAYS write tests first, then implement code to make tests pass. For each user journey, create comprehensive test cases: Write minimal code to make tests pass: Improve code quality while keeping tests green: Remember : Tests are not optional. They are the safety net that enables confident refactoring, rapid development, and production reliability. - Writing new features or functionality - Fixing bugs or issues - Refactoring existing code - Adding API endpoints - Creating new components - Minimum 80% coverage (unit + integration + E2E) - All edge cases covered - Error scenarios tested - Boundary conditions verified - Individual functions and utilities - Component logic - Pure functions - Helpers and utilities - API endpoints - Database operations - Service interactions - External API calls - Critical user flows - Complete workflows - Browser automation - UI interactions - Remove duplication - Improve naming - Optimize performance - Enhance readability - Write Tests First - Always TDD - One Assert Per Test - Focus on single behavior - Descriptive Test Names - Explain what's tested - Arrange-Act-Assert - Clear test structure - Mock External Dependencies - Isolate unit tests - Test Edge Cases - Null, undefined, empty, large - Test Error Paths - Not just happy paths - Keep Tests Fast -...