Enforce a TDD workflow requiring unit, integration, and E2E tests before implementation.
npx skills add https://github.com/dopiotrek/dotclaude --skill tdd-workflow-dopiotrek
Please help me install this Agent Skill. Skill: tdd-workflow Source: https://github.com/dopiotrek/dotclaude/tree/main/skills/tdd-workflow Command: npx skills add https://github.com/dopiotrek/dotclaude --skill tdd-workflow-dopiotrek
This Skill enforces a rigorous Test-Driven Development (TDD) process, ensuring high code quality and comprehensive test coverage for all new features, bug fixes, and refactors.
Activate this skill when starting any new feature development to ensure tests are written first.
High-intent search queries and answers about installing and using this skill.
To enforce test-driven development, you must define user journeys and generate unit, integration, and E2E tests first. This TDD workflow mandates writing tests before implementation, iteratively coding until tests pass and achieving at least 80% code coverage.
Writing integration tests for a new API endpoint using TDD involves defining expected behavior first. You create integration tests to specify the endpoint's responses, then implement the code to satisfy those tests, ensuring reliability and meeting the 80% coverage mandate.
Yes, this TDD workflow supports Playwright for E2E tests. It guides developers through multi-type testing, supporting various testing frameworks and patterns including Jest, Vitest, and Playwright to ensure comprehensive coverage before code implementation.
The minimum code coverage required when following this testing workflow is 80%. This coverage mandate applies across all generated test types, including unit, integration, and E2E tests, ensuring high code quality for new features and refactors.
Yes, you can use mocking strategies for external services during unit test generation. The workflow supports various testing patterns, including mocking external services, to isolate components and ensure tests accurately validate code before implementation.
You should not use a strict TDD workflow for software development when exploring experimental prototypes or spikes where immediate behavior validation is unnecessary. This workflow enforces rigorous test creation and 80% coverage mandates, which may slow rapid, exploratory coding.
flatrickEnforce Test-Driven Development with tests before code and 80% coverage.
VenTheZoneGuide Test-Driven Development workflows with tests before code and 80% coverage.
cyphercr0wEnforce test-first development with 80% coverage across unit, integration, and E2E tests.
PAIPaloozaEnforce TDD/BDD with 80% test coverage for Python and TypeScript.
