skills.rest
ryasrk
ryasrkCOMMUNITY
Explore all skills by this author →
GitHub

tdd-workflow

Enforce test-driven development with 80% coverage using Jest and Playwright.

Updated Mar 12, 2026
Search Tags:#unit tests#testing#tdd#refactoring#integration tests#code coverage#e2e tests
One-click install
npx skills add https://github.com/ryasrk/AgentBrokeTheMatrix-CopilotVersion --skill tdd-workflow-ryasrk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/ryasrk/AgentBrokeTheMatrix-CopilotVersion/tree/main/.github/skills/tdd-workflow
Command: npx skills add https://github.com/ryasrk/AgentBrokeTheMatrix-CopilotVersion --skill tdd-workflow-ryasrk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enforces rigorous test-driven development practices to ensure high code quality, comprehensive test coverage, and robust application behavior.

Core Features & Use Cases

  • Test-Driven Development: Guides the process of writing tests before implementation.
  • Comprehensive Coverage: Mandates 80%+ coverage across unit, integration, and E2E tests.
  • Use Case: When developing a new API endpoint, use this skill to first define the expected request/response and error scenarios in tests, then write the minimal code to satisfy those tests, ensuring the endpoint is functional and well-tested from the start.

Quick Start

Use the tdd-workflow skill to implement the new user authentication feature following test-driven development principles.

Frequently Asked Questions about tdd-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start test-driven development for a new API endpoint?▼

Test-driven development is a practice where you write tests before code implementation. It guides you to define expected behaviors, user journeys, and edge cases first, then write minimal code to satisfy those tests.

How can I enforce a minimum 80% code coverage across unit and E2E tests?▼

You can enforce 80% code coverage by mandating comprehensive tests across unit, integration, and end-to-end levels. This ensures robust application behavior and high code quality before shipping features.

Does the TDD workflow support writing both unit tests and E2E tests with Playwright?▼

Yes, the TDD workflow supports writing both unit and E2E tests. It specifically guides test creation using Jest for unit tests and Playwright for end-to-end tests, alongside mocking techniques.

What is the best way to cover edge cases and error scenarios using TDD?▼

The best way to cover edge cases using TDD is to define these specific error scenarios and user journeys in your tests before implementation. This approach mandates comprehensive coverage and robust application behavior.

When do I need to use mocking techniques during test-driven development?▼

You need to use mocking techniques during test-driven development when defining tests for complex user journeys and error scenarios before code implementation. This ensures comprehensive test coverage across integration and unit tests.

Related Skills

Explore More Software Engineering Skills→
bybren-llcbybren-llc
395

testing-patterns

Standardize Jest and Playwright tests with RLS-aware fixtures and Linear evidence templates.

Official
Intermediate
xu-xiangxu-xiang
1.8k

tdd-workflow

Enforce test-driven development workflows with 80% coverage across unit, integration, and E2E tests.

Community
Basic
vstorm-covstorm-co
1.0k

test-writer

Generate pytest or unittest suites for Python code with fixtures and mocks.

Official
Intermediate
wraithyywraithyy

tdd-workflow

Enforce a TDD workflow with 80% coverage across unit, integration, and E2E tests.

Community
Advanced