tdd-practices
This skill should be used when writing a TDD plan, reviewing test quality, choosing between unit and integration tests, or applying red-green-refactor. Contains outside-in double-loop, test isolation, and test naming.
Install
With your agent
Install OMGSkills skill "incubyte/ai-plugins:bee/skills/tdd-practices" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/incubyte/ai-plugins /tmp/ai-plugins && ln -s /tmp/ai-plugins/bee/skills/tdd-practices ~/.claude/skills/tdd-practices
From README
TDD Practices Red-Green-Refactor The fundamental TDD cycle: RED — Write a failing test that describes the behavior you want. Run it. Watch it fail. This confirms the test is actually testing something. GREEN — Write the minimum code to make the test pass. No more. Resist the urge to build ahead. REFACTOR — Clean up duplication, improve naming, extract patterns. Tests protect you from breaking anything. Each cycle should take minutes, not hours. Small cycles build confidence and momentum. Outside-In Double-Loop (Onion/Hexagonal) For architectures with clear layer boundaries: Outer loop: Integration test at the boundary (HTTP request in, response out). Stays RED until all inner layers are wired. Inner loop: Unit tests for each layer, working inward: Inbound adapter (controller/handler): test request parsing, response shaping Use case + domain: test business rules with mocked outbound ports. Domain is PURE — zero external dependencies.
More from this repo
ai-ergonomics
This skill should be used when evaluating how well code supports LLM-assisted development.
ai-workflow
This skill should be used when explaining why Bee follows spec-first TDD workflows, or when teaching mode is on.
architecture-patterns
This skill should be used when evaluating architecture options, checking dependency direction, or deciding between...
