Tdd logo

Tdd

OrganizationPopular
ccusage
tdd

Guides t-wada Red-Green-Refactor TDD for ccusage logic changes. Use when implementing a feature, writing a regression test for a bug, or refactoring Rust or TypeScript behavior test-first.

Overview

Publisherccusage
Repositoryccusage
Skill nametdd
Stars
19K
Forks
871
Bundled files
Instructions only
Links
  • 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 ccusage on GitHub. Read the source before you install it.

Installation

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

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/ccusage/ccusage/tree/main/.agents/skills/tdd
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

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/ccusage/ccusage.git /tmp/ccusage
mkdir -p .claude/skills
cp -r /tmp/ccusage/.agents/skills/tdd .claude/skills/tdd
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Tdd 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 Tdd 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 Tdd 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.

TDD

Logic changes here — bug fixes, features, refactors — follow t-wada style Red-Green-Refactor. For unfamiliar APIs, prototypes, and data exploration, execute-inspect-adjust first; not every probe needs a test.

The testing skill owns the ccusage-specific side: fixtures, adapter coverage, pricing, model names, snapshots, and CLI output.

Cycle

  1. Sketch the behaviors as placeholders — it.todo(...) in Node test, #[ignore] in Rust — then take them one at a time, simplest first. Bug fixes start with a regression test that reproduces the bug.
  2. Red — write the failing test and confirm it fails for the expected reason.
  3. Green — write the minimum production code that passes. Fake it, make it real, then triangulate with more tests.
  4. Refactor — clean up test and production code while everything stays green. Restructure only while green; when a test is red, fix the production code first.
  5. Run the affected tests after each green and each refactor step. Full-suite runs are for final verification and CI.

Keep each test on one observable behavior, named after that behavior and asserted through a public interface; never weaken a valid test to get a green build. A test that asserts a document contains certain wording freezes text rather than proving a contract.

Three failure modes worth naming:

  • Horizontal slicing. One seam, one test, one minimal implementation, then the next — not every test first and the implementation afterwards.
  • Tautological expectations. The expected value comes from an independent source, not from rerunning the production algorithm inside the test.
  • Mocking inside the system. Substitute only real boundaries — the pricing fetch and the log directories — through the seams the code already has: --offline, CLAUDE_CONFIG_DIR and its siblings, and ccusage-test-support. Collaborators the workspace owns are exercised through their public interface.

Focused runs

Rust tests live in the rust/Cargo.toml workspace. Prefix with direnv exec . when cargo is not already on PATH.

sh
direnv exec . cargo test --manifest-path rust/Cargo.toml --workspace <name-filter>
direnv exec . cargo test --manifest-path rust/Cargo.toml --workspace -- --ignored

node --test --test-name-pattern '<name-filter>' apps/ccusage/src/cli.test.ts

just test runs both suites, just rust::test the Rust one, just test-node the Node one.

Frequently asked questions

What does the Tdd AI skill do?

Guides t-wada Red-Green-Refactor TDD for ccusage logic changes. Use when implementing a feature, writing a regression test for a bug, or refactoring Rust or TypeScript behavior test-first.

Why use Tdd on TypingMind?

Because you install it once and use it with any model. Tdd 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 Tdd in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ccusage/ccusage/tree/main/.agents/skills/tdd. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Tdd?

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 Tdd?

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

Is the Tdd AI skill free?

It is published on GitHub by ccusage. Check the repository for licensing terms. 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

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇