메뉴
Use when implementing new features, fixing bugs, or when the user asks for test-driven development. Triggers: "TDD", "test first", "red green refactor", "write tests", "test-driven". NEVER write production code without a failing test first.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Use when building backend APIs, REST/GraphQL endpoints, or setting up database schemas. Triggers: "build the backend", "create API", "set up database", "write endpoints", backend work for a full-stack app. Every endpoint MUST interact with the database. Produce an API summary for frontend handoff.
Use when running automated exploratory E2E testing on a web application. Triggers: "e2e loop", "exploratory testing", "test this app", "find bugs", "run e2e tests against the app". Claude becomes the tester: navigates with Playwright, clicks through workflows, documents issues.
Use when building frontend that consumes backend APIs or connects to real data sources. Triggers: "wire up the frontend", "connect to API", "fetch data from backend", "form submission", building UI that needs real data flow. NEVER use mock/hardcoded data. Every component connects to a real endpoint.
Use when debugging a failing test, unexpected behavior, or production error. Triggers: "why is this failing", "debug", "investigate", "root cause", stack traces, error messages. NEVER skip to a fix without completing the investigation phases.
Use when perfecting a frontend design through iterative visual evaluation. Triggers: "make it look perfect", "10/10 design", "iterate on the design", "polish the UI". Loops: screenshot → evaluate → fix → re-screenshot until design scores 10/10.
Use when implementing a new feature that requires multiple files and careful planning. Triggers: "implement feature", "build this feature", "add this functionality", multi-file changes. 7-phase structured development with exploration and design before any code.
SOC 직업 분류 기준
| name | tdd |
| description | Use when implementing new features, fixing bugs, or when the user asks for test-driven development. Triggers: "TDD", "test first", "red green refactor", "write tests", "test-driven". NEVER write production code without a failing test first. |
MANDATORY: Follow RED-GREEN-REFACTOR. No exceptions.
No production code exists without a failing test that demanded it.
should [expected] when [condition]Each RED-GREEN-REFACTOR cycle should be 1-5 minutes. If a cycle takes longer:
| Excuse | Why It Fails |
|---|---|
| "I'll write tests after" | You won't. And the code won't be testable. |
| "This is too simple to test" | Simple untested code becomes complex untested code. |
| "I need to write the whole thing first" | No. One test, one behavior, one cycle. |
| "Testing slows me down" | Testing speeds you up. Debugging untested code is what's slow. |
| "The test would be trivial" | Good. Trivial tests catch non-trivial regressions. |
| "I know it works" | Prove it. With a test. |