components

Detects, loads, and applies reusable task patterns for Claude's main, subagent workflows, and slash commands.

288|31|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/ThibautMelen/agentic-ai-systems --skill components
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: components
Source: https://github.com/ThibautMelen/agentic-ai-systems/tree/main/implementation/components
Command: npx skills add https://github.com/ThibautMelen/agentic-ai-systems --skill components

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams to apply Test-Driven Development (TDD) to feature implementation, reducing bugs and rework by defining tests before code.

Core Features & Use Cases

  • RED: Write a failing test: Capture the requirement and specify expected behavior before writing code.
  • GREEN: Implement minimal code: Write the smallest amount of code to make tests pass.
  • REFACTOR: Improve while preserving tests: Refactor for clarity and maintainability without breaking tests.
  • Use Case: When starting a new feature or bug fix, begin with a failing test to lock in requirements and drive design.

Quick Start

Create a failing test for the new feature, then implement the minimal code to pass the test, and finally refactor for readability.

Frequently Asked Questions about components

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

FAQPage Schema
How do I use test-driven development to improve code quality?

Test-driven development (TDD) improves code quality by writing failing tests first to capture requirements, then implementing minimal code to pass them, and finally refactoring for clarity. This cycle locks in expected behavior and reduces bugs before they reach production.

What's the red-green-refactor cycle in TDD?

Red-green-refactor is TDD's core workflow: write a failing test (red), implement minimal code to pass it (green), then improve the code without breaking tests (refactor). This ensures every line serves a requirement and stays maintainable.

When should I start with a failing test instead of writing code first?

Start with a failing test when beginning a new feature or bug fix to lock in requirements and drive design. Writing tests first clarifies what success looks like before implementation, preventing scope creep and rework.

How do I apply TDD to bug fixes?

For bug fixes, write a failing test that reproduces the bug, then implement the minimal fix to pass it. This ensures the bug stays fixed and prevents regression.

Can TDD reduce rework and bugs in feature development?

Yes. TDD reduces bugs and rework by defining tests before code, ensuring every feature meets its specification from the start. Teams catch misunderstandings early rather than during integration or production.