tdd

Enforce Test-Driven Development with Red-Green-Refactor cycles for Gleam code.

2|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/aboio-labs/aboio-skills --skill tdd-aboio-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/aboio-labs/aboio-skills/tree/main/skills/tdd
Command: npx skills add https://github.com/aboio-labs/aboio-skills --skill tdd-aboio-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces Test-Driven Development (TDD) to ensure that all new code is written with corresponding tests, preventing bugs and regressions before they occur.

Core Features & Use Cases

  • Enforces Test-First: Mandates writing failing tests before any implementation code.
  • Guides TDD Cycle: Provides clear steps for the Red-Green-Refactor cycle.
  • Use Case: When developing a new feature, use this Skill to guide you in writing a failing test, then the minimal code to pass, and finally refactoring.

Quick Start

Follow the Red-Green-Refactor cycle for all new code.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I practice test-driven development in Gleam?

Test-driven development in Gleam is enforced by following the Red-Green-Refactor cycle: write a failing test first, implement minimal code to pass it, then refactor. This ensures all new features have corresponding tests to prevent regressions.

What is the Red-Green-Refactor cycle for code quality?

The Red-Green-Refactor cycle is a test-driven development methodology where you write a failing test, create the minimal implementation to make it pass, and then refactor the code. It enforces test-first development to ensure code quality.

How do I stop rationalizing skipping tests during refactoring?

To stop rationalizing skipped tests during refactoring, enforce strict adherence to test-driven development methodology. Address common anti-patterns by mandating failing tests before any implementation code to maintain code quality.

Does this TDD approach work with my existing Gleam project?

Yes, this TDD approach works with Gleam projects by guiding developers through writing failing tests before implementation. It ensures all new code is written with corresponding tests to prevent bugs and regressions.

When should I write the minimal code to pass a failing test?

You should write the minimal code to pass a failing test immediately after confirming the test fails. This test-driven development step ensures you only write code necessary to meet the test requirements before refactoring.