209 skills · sorted by relevance
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
The English summary is being prepared. Showing the original description.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
The English summary is being prepared. Showing the original description.
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
The English summary is being prepared. Showing the original description.
Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.
The English summary is being prepared. Showing the original description.
Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.
The English summary is being prepared. Showing the original description.
Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.
The English summary is being prepared. Showing the original description.
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
The English summary is being prepared. Showing the original description.
Design and implement comprehensive testing strategies. Use when setting up tests, choosing test types, implementing TDD, or improving code quality. Covers unit tests, integration tests, E2E tests, test-driven development, and testing best practices.
The English summary is being prepared. Showing the original description.
Write the test first, watch it fail, write minimal code to pass
The English summary is being prepared. Showing the original description.
Use when implementing any feature or bugfix, before writing implementation code
The English summary is being prepared. Showing the original description.
Write and migrate tests using the Swift Testing framework with @Test, @Suite, #expect, #require, confirmation, parameterized tests, test tags, traits, withKnownIssue, XCTest UI testing, XCUITest, test plan, mocking, test doubles, testable architecture, snapshot testing, async test patterns, test organization, and test-driven development in Swift. Use when writing or migrating tests with Swift Testing framework, implementing parameterized tests, working with test traits, converting XCTest to Swift Testing, or setting up test organization and mocking patterns.
The English summary is being prepared. Showing the original description.
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
The English summary is being prepared. Showing the original description.
Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.
The English summary is being prepared. Showing the original description.
Use when implementing any feature or bugfix, before writing implementation code
The English summary is being prepared. Showing the original description.
Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.
The English summary is being prepared. Showing the original description.
TDD: enforce RED-GREEN-REFACTOR, tests before code.
The English summary is being prepared. Showing the original description.
Use when implementing any feature or bugfix, before writing implementation code
The English summary is being prepared. Showing the original description.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
The English summary is being prepared. Showing the original description.
Test-driven development in Python using uv as the package manager. Covers the red-green-refactor cycle, vertical slicing, and uv project setup.
The English summary is being prepared. Showing the original description.
Create high-quality ToolUniverse skills following test-driven, implementation-agnostic methodology.
The English summary is being prepared. Showing the original description.
Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.
The English summary is being prepared. Showing the original description.
Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with test-first approach.
The English summary is being prepared. Showing the original description.
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
The English summary is being prepared. Showing the original description.
Ground framework-specific implementation in official documentation — detect stack versions, fetch authoritative docs, implement cited patterns, cite sources. Load when building with a library or framework where API correctness matters, when the user wants verified or documented code, or before writing framework code from memory. Also triggers on "source driven development", "cite the docs", "check official documentation", "verify against docs", "don't hallucinate APIs". Not for pure logic or renames. Pairs with feature-spec and test-driven-development.
The English summary is being prepared. Showing the original description.