'test-driven' 검색 결과

Use when implementing any feature or bugfix, before writing implementation code

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Test-first development practice where test specifications are written before production code, integrated into plan tasks as mandatory first sub-steps.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Strict RED-GREEN-REFACTOR cycle enforcement. Tests are never skipped or deferred. Run mode only, never watch mode. Exit code evidence mandatory.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Coordinate the test-driven development cycle from requirements and failing tests through implementation, refactoring, and validation. Use when building a feature with a structured TDD workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AI DevKit · Test-driven development — write a failing test before writing production code. Use when implementing new functionality, adding behavior, or fixing bugs during active development.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green. Use when a user asks to practice TDD, write tests first, follow red-green-refactor, do test-driven development, write failing tests before code, or phrases like 'make the test pass', 'test coverage', or 'unit tests before implementation'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user explicitly requests strict or test-first TDD, or when the current conversation already contains an explicit `TDD Route: strict` decision from another Aegis workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Test-driven development for behaviour a unit test cannot reach, by writing the expectation against the running app before writing the code. Declare the consequence first, watch it fail, implement, watch it pass. Use when building a user-facing feature, when the user asks for TDD on UI or full-stack work, when a unit test cannot express the outcome that matters, or when you want a red-green loop that runs against the real app instead of mocks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Backend API design, database architecture, microservices patterns, and test-driven development. Use for designing APIs, database schemas, or backend system architecture.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide red-green-refactor TDD with test generation, coverage-gap analysis, and multi- framework support. Use when writing tests first, analyzing coverage, generating test stubs, or converting tests between Jest, Pytest, JUnit, and Vitest.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

TDD and testing skills for iOS/macOS apps. Covers characterization tests, TDD workflows, test contracts, snapshot tests, test infrastructure, and deterministic quality gates (fitness functions, coverage ratchet, mutation testing). Use for test-driven development, adding tests to existing code, or building test infrastructure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when implementing any feature or bugfix, before writing implementation code

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write the test first, watch it fail, write minimal code to pass

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when implementing any feature or bugfix, before writing implementation code

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply test-driven development with small, behavior-focused feedback loops. Use when the user asks to build or fix something test-first, mentions red-green-refactor, or wants integration tests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.