Agent skill

TDD

by FastLED in FastLED/FastLED

Guide Test-Driven Development workflow for FastLED. An agent skill from FastLED/FastLED.

MITAuto-check passedTesting & QA

Install TDD

skills CLI
$ npx skills add FastLED/FastLED --skill tdd -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FastLED/FastLED tdd --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FastLED/FastLED.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/tdd .claude/skills/tdd && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tdd
GitHub stars
7.5k
Token cost
~848 tokens
SKILL.md length
330 words
Files
1
Skills in repo
23
Repo updated
First seen
Licence
MIT

At a glance

Guide Test-Driven Development workflow for FastLED. An agent skill from FastLED/FastLED.

  • Works in 3 steps: RED — Write a Failing Test → GREEN — Make It Pass → REFACTOR — Clean Up
  • Implementing new features
  • SKILL.md covers Input, Phase 1: RED — Write a Failing…, Phase 2: GREEN — Make It Pass and Phase 3: REFACTOR — Clean Up, plus 2 more sections
  • Calls bash

What it does

TDD is an agent skill from FastLED/FastLED. Guide Test-Driven Development workflow for FastLED. Use when implementing new features or fixing bugs with a test-first approach. Enforces Red-Green-Refactor discipline with FastLED test conventions.

Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Test-driven development. It works with Bash and C++. The repository describes itself as: The FastLED library for colored LED animation on Arduino. Please direct questions/requests for help to the FastLED Reddit community: http://fastled.io/r We'd like to use github… The licence is MIT.

When your agent uses it

  • Implementing new features
  • Fixing bugs with a test-first approach

Example prompts

  • “/tdd”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. RED — Write a Failing Test
  2. GREEN — Make It Pass
  3. REFACTOR — Clean Up

What it can do on your machine

Read from SKILL.md and the folder at commit 8d6ed12. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

TDD loads about 848 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 330 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~51
When it runs · the whole SKILL.md, loaded when a task matches
~848

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FastLED/FastLED at commit 8d6ed12, republished under its MIT licence (© FastLED). 330 words, ~848 tokens.

Download SKILL.mdSave it as .claude/skills/tdd/SKILL.md (or your agent's skills folder).
name
tdd
description
Guide Test-Driven Development workflow for FastLED. Use when implementing new features or fixing bugs with a test-first approach. Enforces Red-Green-Refactor discipline with FastLED test conventions.
argument-hint
<feature or bug description>
context
fork
agent
test-writer-agent

TDD Workflow — Red-Green-Refactor for FastLED

You are guiding a Test-Driven Development cycle. Follow the strict Red-Green-Refactor discipline.

Input

$ARGUMENTS

Phase 1: RED — Write a Failing Test

Steps
  1. Understand the requirement: Read relevant source code to understand the API and behavior
  2. Find existing tests: Search tests/ for related test files — prefer extending them
  3. Write the test FIRST: Create a minimal test that describes the expected behavior
  4. Run the test: Execute bash test TestName to verify it FAILS
  5. Verify failure reason: The test must fail because the feature is missing or the bug exists, NOT because of a compile error or typo
Test Conventions
  • Read agents/tests.md for full conventions
  • Use FL_ prefixed assertion macros (e.g., FL_CHECK_EQ, FL_REQUIRE_TRUE)
  • Include test.h and FastLED.h
  • Use namespace fl; and anonymous namespace wrapper
  • Mirror source structure for file placement: src/fl/foo.h -> tests/fl/foo.cpp
  • Keep tests simple — no mocks, no helper classes, minimal setup
Output
## RED Phase

**Test file**: tests/fl/example.cpp
**Test case**: "Feature - expected behavior"
**Status**: FAILS as expected
**Failure reason**: [why it fails — confirms the test is valid]

Phase 2: GREEN — Make It Pass

Steps
  1. Write minimal code: Implement just enough to make the test pass
  2. No premature optimization: Simplest solution that works
  3. Run the test: Execute bash test TestName to verify it PASSES
  4. Run full suite: Execute bash test --cpp to verify no regressions
Output
## GREEN Phase

**Implementation**: src/fl/example.h (lines X-Y)
**Changes**: [brief description of what was added/changed]
**Test status**: PASSES
**Full suite**: All tests pass (no regressions)

Phase 3: REFACTOR — Clean Up

Steps
  1. Review the code: Look for duplication, unclear naming, unnecessary complexity
  2. Refactor incrementally: Make one change at a time
  3. Run tests after each change: bash test TestName must stay green
  4. Consider edge cases: Add 1-2 more test cases if critical edge cases are obvious
  5. Run full suite: bash test --cpp to confirm everything still passes
Output
## REFACTOR Phase

**Changes made**: [list of refactoring improvements]
**Test status**: All tests still pass
**Edge cases added**: [any additional test cases, or "none needed"]

Final Summary

After all three phases, provide:

## TDD Summary

**Feature**: [what was implemented]
**Test file**: [path]
**Source file(s)**: [paths]
**Tests added**: [count and names]
**All tests passing**: Yes/No

Key Rules

  • NEVER write implementation code before the test
  • NEVER skip the RED phase — you must see the test fail first
  • Keep tests simple — one focused test per behavior
  • Run tests at every phase transition — this is non-negotiable
  • Stay in project root — never cd to subdirectories
  • Use bash test — never bare python, meson, or ninja

© FastLED, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/tdd of FastLED/FastLED.

Open the folder on GitHubat commit 8d6ed12

Compare with similar skills

TDD next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

TDD compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
TDD this skillFastLED/FastLED7.5k—~848Automated safety check: PassMIT
Bats Shell Testing Patternswshobson/agents40k11 repos~1.3kAutomated safety check: PassMIT
Gh IssueTypedDevs/bashunit434—~721Automated safety check: NotesMIT
Mcpp Releasemcpp-community/mcpp155—~3.1kAutomated safety check: PassApache-2.0
Gh IssuesTypedDevs/bashunit434—~1.7kAutomated safety check: NotesMIT
TDD2SSK/dot-files247—~444Automated safety check: PassMIT

Similar skills

  • Writes unit tests for shell scripts with Bats: error-condition tests, fixtures and mocks, cross-shell checks, parallel runs, helper files and CI integration.

    40k GitHub starsUsed in 11 repos~1.3k tokens
    Testing & QAAuto-check passed
  • Gh Issue

    TypedDevs/bashunit

    Fetch GitHub issue, create branch, plan and implement with TDD, then open PR

    434 GitHub stars~721 tokensUpdated yesterday
    Testing & QAAuto-check: notes
  • Mcpp Release

    mcpp-community/mcpp

    A skill your agent uses when releasing a new version of mcpp — bumps version, creates tag, triggers release CI, and monitors until all platforms succeed.

    155 GitHub stars~3.1k tokensUpdated 2 days ago
    Testing & QAAuto-check passed
  • Gh Issues

    TypedDevs/bashunit

    Walk over all open GitHub issues that are unassigned or assigned to the current user, and process each one via the /gh-issue skill, sequentially.

    434 GitHub stars~1.7k tokensUpdated yesterday
    Testing & QAAuto-check: notes
  • TDD

    2SSK/dot-files

    Test-Driven Development workflow. An agent skill from 2SSK/dot-files.

    247 GitHub stars~444 tokensUpdated 25 days ago
    Testing & QAAuto-check passed
  • Writes a single failing test that reproduces a bug after its root-cause analysis is complete, before any fix is written.

    529 GitHub stars~4k tokensUpdated today
    Testing & QAAuto-check passed

More from FastLED/FastLED

All 23 skills in this repo
  • CI Fix

    FastLED/FastLED

    Scan all CI builds and tests, find failures, fetch error logs, and fix the code.

    7.5k GitHub stars~897 tokensUpdated today
    Auto-check passed
  • Driver Review

    FastLED/FastLED

    Review and implement hardware driver code — DMA safety, interrupt correctness, timing constraints, peripheral register usage, channel drivers, and peripheral mock implementations.

    7.5k GitHub stars~3.1k tokensUpdated today
    Auto-check passed
  • Embedded Debug

    FastLED/FastLED

    Firmware crash analysis, stack trace decoder, and register dump interpreter for ESP32/ARM/AVR platforms.

    7.5k GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Esp32 Log Triage

    FastLED/FastLED

    Parse and classify ESP32 serial log output to identify FastLED-related errors, RMT/I2S/SPI driver faults, timing violations, RTOS issues, and crash signatures.

    7.5k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Memory Audit

    FastLED/FastLED

    Audit embedded code for stack overflow risks, heap fragmentation, static allocation patterns, and memory leaks.

    7.5k GitHub stars~488 tokensUpdated today
    Auto-check passed
  • Platform Port

    FastLED/FastLED

    Guide porting FastLED to new MCU platforms, including int.h types, clockless drivers, SPI implementations, and platform detection.

    7.5k GitHub stars~580 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about TDD

What does TDD do?

Guide Test-Driven Development workflow for FastLED. An agent skill from FastLED/FastLED. TDD is an agent skill from FastLED/FastLED. Guide Test-Driven Development workflow for FastLED.

When should I use TDD?

TDD fits situations like: implementing new features; fixing bugs with a test-first approach.

How do I install TDD in Claude Code?

Run `npx skills add FastLED/FastLED --skill tdd -a claude-code`. Or copy the skill folder (.claude/skills/tdd in FastLED/FastLED) into .claude/skills/tdd in your project. Claude Code loads it when a task matches its description.

How do I install TDD in Codex?

Run `npx skills add FastLED/FastLED --skill tdd -a codex`. Or copy the skill folder (.claude/skills/tdd in FastLED/FastLED) into .agents/skills/tdd in your project. Codex loads it when a task matches its description.

Can I use TDD in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FastLED/FastLED --skill tdd -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tdd, .gemini/skills/tdd, .github/skills/tdd and .opencode/skills/tdd in your project.

What does TDD need to run?

Going by SKILL.md and its folder, TDD needs the command-line tools its instructions call (bash).

Does TDD access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is TDD safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does TDD use?

TDD is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does TDD use?

About 848 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to TDD?

Skills that share tags, products or a category with TDD: Bats Shell Testing Patterns (wshobson/agents, 40k stars), Gh Issue (TypedDevs/bashunit, 434 stars), Mcpp Release (mcpp-community/mcpp, 155 stars) and Gh Issues (TypedDevs/bashunit, 434 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains TDD?

FastLED (a GitHub organization) maintains it in FastLED/FastLED, which has 7,506 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 7, 2026.

Source: FastLED/FastLED on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.