Test Driven Development

Organization

DevelopersGlobal

test-driven-development

Red-green-refactor cycle with meaningful coverage. Tests are written before implementation. Coverage is a side effect of good tests, not the goal.

Overview

Publisher	DevelopersGlobal
Repository	`ai-agent-skills`
Skill name	`test-driven-development`
Stars	212
Forks	33
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by DevelopersGlobal on GitHub. Read the source before you install it.

Installation

Install the Test Driven Development AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/DevelopersGlobal/ai-agent-skills/tree/main/skills/test-driven-development
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/DevelopersGlobal/ai-agent-skills/tree/main/skills/test-driven-development

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/DevelopersGlobal/ai-agent-skills.git /tmp/ai-agent-skills
mkdir -p .claude/skills
cp -r /tmp/ai-agent-skills/skills/test-driven-development .claude/skills/test-driven-development

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Test Driven Development in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Test Driven Development on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Test Driven Development is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Overview

TDD is the discipline of writing a failing test before writing implementation code. It forces you to think about the interface before the internals, produces tests that actually test behavior (not just coverage), and gives you a safety net for every refactor.

AI agents skip tests constantly. This skill makes tests non-optional.

When to Use

Starting any new feature or function
Fixing any bug (write a test that reproduces the bug first)
Refactoring existing code (ensure test coverage before you start)

Process

Step 1: Write a Failing Test (Red)

Write a test for the behavior you want — before writing implementation.
The test should describe what the code does, not how:
- ✅ test("returns 404 when user not found")
- ❌ test("calls findById with the user id")
Run the test. Confirm it fails for the right reason (not a syntax error — a missing implementation).

Verify: Test runs and fails with a clear "not implemented" or "undefined" error.

Step 2: Write Minimum Code (Green)

Write the minimum implementation to make the test pass.
Do not write more than the test requires — resist the urge to add logic for future cases.
Run the test. Confirm it passes.

Verify: All tests pass. No new tests added yet.

Step 3: Refactor (Refactor)

Now clean up the implementation — no new behavior, only improved structure.
Run tests after every refactoring step — do not batch refactors.
If tests break during refactor: revert immediately, refactor more carefully.

Verify: Tests still pass after refactor. Code is cleaner.

Step 4: Repeat for Each Behavior

Repeat steps 1–3 for each distinct behavior of the feature.
Test pyramid: many unit tests, fewer integration tests, minimal end-to-end tests.

Step 5: Coverage Sanity Check

Run coverage report. Flag any critical paths with 0% coverage.
Do NOT chase a coverage number — write tests for behaviors that matter.

Verify: All happy paths and key edge cases have tests. Coverage report reviewed.

Common Rationalizations (and Rebuttals)

Excuse	Rebuttal
"I'll add tests after"	After never comes. And after-the-fact tests test your implementation, not the behavior.
"This code is too simple to test"	Simple code breaks in unexpected ways when requirements change.
"Integration tests are enough"	Unit tests catch bugs faster, run faster, and localize failures better.
"We don't have time for TDD"	You have time for the bug investigation that comes without TDD?

Red Flags

Tests were written after the implementation
Tests test internal implementation details (private methods, DB queries) rather than behavior
"Happy path only" test coverage
Tests pass even when you break the implementation (mocked away the real behavior)
Coverage target hit by testing trivial getters/setters

Verification

Tests written before implementation (or alongside for bug fixes)
Each test describes a specific behavior
Red-green-refactor cycle followed
All tests pass
Key edge cases covered (empty input, null, boundary values)
Coverage report reviewed for critical path gaps

Frequently asked questions

What does the Test Driven Development AI skill do?

Red-green-refactor cycle with meaningful coverage. Tests are written before implementation. Coverage is a side effect of good tests, not the goal.

Why use Test Driven Development on TypingMind?

Because you install it once and use it with any model. Test Driven Development is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Test Driven Development in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/DevelopersGlobal/ai-agent-skills/tree/main/skills/test-driven-development. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Test Driven Development?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Test Driven Development?

As many as you like. As long as a model supports skills, you can use Test Driven Development with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Test Driven Development AI skill free?

Yes. It is published on GitHub by DevelopersGlobal under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Control Ui E2e

openclaw

OrganizationPopular

Use when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks, mocked Gateway flows,…

Discord E2e

Test Discord with Convex-leased QA bots: check credentials without a Gateway, exercise owned messages, or prove OpenClaw replies, files, threads, reactions, streaming, and typing. Distinguish API and…

Openclaw Qa Testing

Run, watch, debug, extend, or explain OpenClaw qa-lab and qa-channel scenarios, artifacts, and live lanes.

Proof Video

Add subtitles, captions, narration cues, or zoom to a proof video or PR recording using repo-local capture helpers and a system ffmpeg renderer.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Overview

When to Use

Process

Step 1: Write a Failing Test (Red)

Step 2: Write Minimum Code (Green)

Step 3: Refactor (Refactor)

Step 4: Repeat for Each Behavior

Step 5: Coverage Sanity Check

Common Rationalizations (and Rebuttals)

Red Flags

Verification

References

Frequently asked questions

Related AI Skills

Set up your own AI workspace now