200 skills · sorted by relevance
Guide development through test-driven development (TDD): write a test, confirm it fails, add minimal code, then clean up. Apply this cycle to features and bug fixes while checking that existing behavior still passes its tests.
Automatically repair source code against a failing test while preserving the test itself. Set a spending limit and attempt count, then receive verification results and usage costs based on rerunning the test command.
Follow Conductor's development plans using test-driven development: write a failing test, implement the change, then improve the code. Manage phase verification, progress updates, and focused git commits as tasks move toward completion.
Create unit test scaffolds, sample data, and mocks from code or specifications. Analyze coverage reports to prioritize missing tests, and guide test-driven development through failing tests, minimal implementation, and refactoring.
Guides feature development and bug fixes through test-driven development: write a test, confirm the expected failure, then add the minimum code to pass. It also covers refactoring and checking the full test suite.
Create and improve agent skills by testing behavior before and after adding guidance. The skill applies test-driven development to SKILL.md documents, covering structure, discovery descriptions, supporting files, and checks that reveal unclear or ineffective instructions.
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.
Test-driven development workflow with philosophy guide - plan → write tests → implement → validate
The English summary is being prepared. Showing the original description.
Test-driven development workflow with philosophy guide - plan → write tests → implement → validate
The English summary is being prepared. Showing the original description.
Use when Java implementation work should be guided by Test-Driven Development, including maintaining a test list, choosing the next behavior, writing a failing test first, implementing only enough production code to pass, and refactoring while keeping tests green. This should trigger for requests such as Apply TDD; Use test-driven development; Drive this Java change with tests; Write the failing test first; Red-green-refactor this feature. Part of Plinth Toolkit
The English summary is being prepared. Showing the original description.
Use only when the user explicitly invokes obra test-driven-development for iron-law examples. Core TDD is docs/ai/skills/tdd/SKILL.md. Do not use this for docs-only, formatting-only, or generated-mirror changes.
The English summary is being prepared. Showing the original description.
Test-Driven Development workflow for Software Metrics Machine. Covers test frameworks (Vitest 4.x for CLI/REST/core/utils, Jest 30.x for webapp), test patterns (describe/it, builder pattern, mocks via vi.fn), test commands, coverage requirements, and the Red-Green-Refactor cycle. USE FOR: write tests, run tests, test this, add tests, testing, coverage, TDD, test-driven development, vitest, jest, test pattern, test convention. DO NOT USE FOR: linting (use lint skill), building (use build commands directly), debugging production issues.
The English summary is being prepared. Showing the original description.
This skill should be used when developing code using Test-Driven Development (TDD) methodology. Use this skill when the user wants to write tests first before implementation, needs guidance on the red-green-refactor cycle, or explicitly requests TDD-style development. Triggers include requests like "develop this feature using TDD", "write tests first", "help me with test-driven development", or "implement this following TDD practices". The skill guides through writing failing tests, implementing minimal code to pass, and refactoring while maintaining test coverage.
The English summary is being prepared. Showing the original description.
Test-driven development: production-level red green refactor and boundaries. Use when implementing, reviewing or testing test-driven development for React, Vite, Next.js or Perfect_AI projects.
The English summary is being prepared. Showing the original description.
Implement test-driven development (TDD) workflow using the red-green-refactor cycle. Use when writing new features, fixing bugs, or refactoring existing code. Always write the failing test first, then implement minimal code to pass, then refactor. Essential for ensuring code reliability, preventing regressions, improving design through testability requirements, documenting expected behavior through tests, enabling confident refactoring, and maintaining high code quality standards throughout the development process.
The English summary is being prepared. Showing the original description.
Apply the Red-Green-Refactor cycle to software development. Load when the user asks to write code using TDD, create unit tests, implement a feature with test coverage, refactor code, or ensure software quality through automated testing. Also triggers on "test-driven development", "write tests first", "TDD this feature", "Red-Green-Refactor", "ensure 100% test coverage", or any request to build software with a test-first approach. Supports unit, integration, and end-to-end testing strategies.
The English summary is being prepared. Showing the original description.
Guides feature development and bug fixes by writing tests before implementation. It confirms each test fails for the expected reason, adds only enough code to pass, and checks the full test suite before completion.
Create, revise, and validate agent skills through tests that compare behavior with and without the instructions. It helps identify unclear guidance, choose an appropriate document structure, and refine wording before deployment.
Build features or fix bugs by writing one failing test, then the smallest implementation that passes it. Tests check behavior through public interfaces, the entry points callers use, so they remain useful when internal code changes.
Turn a specification and its tickets into code by coordinating multiple agents around task dependencies. Combine their work on one integration branch, use test-driven development, review the result, and close tickets through the issue tracker’s workflow.
Develop features and fix bugs by running a failing test first, making the smallest passing change, then refactoring. Check at least 80% test coverage and preserve evidence of failures, successful fixes, and verified behavior.
Develop Spring Boot features and fixes by writing tests before implementation. Guides unit, web, persistence, and integration testing with JUnit 5, Mockito, MockMvc, and Testcontainers, plus JaCoCo measurement of how much code tests cover.
Develop and refactor Quarkus 3.x LTS services by writing tests first. Covers API responses, event handling, and asynchronous operations, with unit and integration tests plus coverage checks to show how much code is tested.
Write Kotlin tests with Kotest and MockK using test-driven development, where tests come before implementation. Cover asynchronous code, check behavior across generated inputs, and use Kover reports to measure how much code the tests exercise.