94건 · 관련도순
Drive a Genie change test-first through the genie MCP tools, working entirely from the live image (no files). Use when adding behavior or fixing a bug in the image — anything where a test should lead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test-driven development with a red-green-clean loop, running mix credo on the whole project at the end of every vertical slice so standards violations are fixed in the slice that introduced them instead of piling into a refactor at the end. 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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when encountering any bug, test failure, or unexpected behavior. Enforces a strict reproduce-first, root-cause-first, failing-test-first debugging workflow before fixing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use before non-trivial coding work to pick a task-appropriate working mode — debug, fix, review, test-first, refactor, optimize, migrate, upgrade, integrate, spike, or unstuck — then follow its checklist. Modes are procedures, not personas. Not needed for trivial one-line edits or non-coding tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[Workflow] Implement a well-defined feature spec-first and test-first when its behavior is not yet captured in a canonical spec. Spec-complete behavior uses workflow-implement-spec.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test-driven development with red-green-refactor and behavior-focused tests. Use when the user explicitly wants test-first work, a regression test before a fix, or integration tests that drive a feature through a public interface.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use test-driven development for behavior-changing feature or fix work, and whenever the user mentions TDD, test-first, red-green-refactor, tracer bullets, integration tests, or public-interface behavior tests. Skip for docs-only, path-only rename, formatting-only, or purely mechanical chores unless explicitly requested.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with test-first approach.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Decompose an approved PWDEV Flow specification into dependency-aware waves and atomic executable tasks. Use when design is approved and the user needs exact file scope, test-first actions, verification commands, and an execution gate.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute approved PWDEV Flow plans one atomic task at a time with test-first implementation, fresh verification, blocker handling, and durable evidence. Use after the plan gate is approved or for approved Flow correction tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run TDD cycle for feature implementation. Use when implementing features with RED-GREEN-REFACTOR, running test-driven development, automating TDD workflow, or ensuring test-first development.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.