Loading...
Loading...
Found 378 Skills
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.
Implement the minimal code needed to make failing tests pass in the TDD green phase.
단일 태스크의 RED-GREEN-REFACTOR TDD 루프를 ping-pong 방식으로 실행합니다. .tdd-sessions/에서 활성 세션 파일을 읽어 현재 태스크를 찾고, 개발자와 함께 전체 사이클을 진행하며 (테스트 작성과 구현을 번갈아가며), 완료 시 세션 파일을 업데이트합니다. 세션 파일을 생성하려면 먼저 /tdd-plan을 실행하세요.
Add a new feature with design, TDD, and PR workflow
Use when creating a plan using Plan model and enhancing structured design plans in Cursor Plan mode for Java implementations. Use when the user wants to create a plan, design an implementation, structure a development plan, or use plan mode for outside-in TDD, feature implementation, or refactoring work. This should trigger for requests such as Create a plan with Cursor Plan mode; Write a plan with Claude Plan mode; Design an implementation plan; Structure a development plan. Part of cursor-rules-java project
Requirements clarification for TDD. Use BEFORE RED phase to understand WHAT to test. Asks targeted questions to uncover ambiguities, edge cases, and acceptance criteria.
ping-pong TDD 세션의 마지막 단계입니다. .tdd-sessions/에서 활성 세션 파일을 읽어 완료된 태스크를 요약하고, Conventional Commits 메시지를 제안하며, 커밋을 실행하고 세션 파일을 정리합니다. 모든 /tdd-task 호출이 완료된 후 실행합니다.
Design failing tests for complex features using Independent Evaluation — dispatches a context-free agent that sees only the requirement spec and code paths (not the implementation approach), then returns executable failing tests. Use when starting TDD for a non-trivial feature, when the requirement is ambiguous enough that biased tests are a risk, or when the user asks for independent test design.
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
Test-driven development methodology — red-green-refactor cycle, writing failing tests first, minimal implementation, and iterative refinement. Use when implementing features test-first, when the user asks for TDD, or when writing tests before code.
Spec-driven development pipeline with 6 phases: Explore, Requirements, Design, Task Plan, Implementation, Review. Enforces human approval gates between phases. Use when user wants structured feature development, spec-first approach, or says "I want to add feature X", "new feature", "implement", "build". Keywords: spec, requirements, design document, TDD plan, task plan, implementation, code review, pipeline, approval gates, WHEN/SHALL.
Ralph Wiggum loops - self-referential TDD iteration until tests pass