# Tools

> Every listed resource, editors’ picks first. The filters below can be combined.

- Search: append `?q=<keywords>` to the URL. Separate several keywords with spaces; all of them must match. Matches name, repository, tags, professions, description and README.
- Filter by type: append `?type=<cli|skill|plugin|mcp>` to the URL.
- Filter by profession: append `?profession=<profession id>` to the URL. Separate several ids with commas; a resource matches when it suits any of them. Ids are listed at https://hebbmind.com/api/v1/professions
- Filter by tag: append `?tag=<tag>` to the URL. Separate several tags with commas; a resource must carry all of them. Tags are listed at https://hebbmind.com/api/v1/tags

Resources for Full-stack / Indie or ML / AI, Tagged `unit-testing`, `tdd`: 4 items.

> - Full-stack / Indie: General software work: coding-agent workflows, code review, debugging and Git collaboration.
> - ML / AI: Model training, evaluation and LLM application development.

- [Test-Driven Development](https://hebbmind.com/skill/test-driven-development.md): [Skill] Forces red-green-refactor: write a test and watch it fail, then write the minimum code to pass. Any code written without a verified failing test gets deleted and redone. From the Superpowers workflow.
- [tdd](https://hebbmind.com/skill/tdd.md): [Skill] Test-driven development in vertical slices: agree on test seams with the user first, verify behavior only through public interfaces, and avoid listed anti-patterns such as implementation coupling and tautological tests. From Matt Pocock's skills collection.
- [TDD Workflows](https://hebbmind.com/plugin/tdd-workflows.md): [Plugin] Test-driven development plugin: /tdd-workflows:tdd-cycle and related commands move through red-green-refactor phases with a checkpoint for approval at each, plus TDD orchestrator and code reviewer subagents. Part of the wshobson/agents marketplace.
- [TDD Guard](https://hebbmind.com/plugin/tdd-guard.md): [Plugin] Uses hooks to enforce test-driven development in Claude Code: blocks implementation without a failing test, prevents code beyond what tests require, and can use lint results to push refactoring. Needs Node.js 22+. Still maintained, but the author suggests its successor Probity for new projects.