메뉴
Use when implementing any feature or bug fix. Defines the red-green-refactor cycle and the rule that no production code may be written without a failing test first. Load before starting any implementation work.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when writing or reviewing any Repository, Table object, or migration. Defines Exposed table conventions, the Either-returning repository pattern, newSuspendedTransaction usage, and Liquibase migration rules. Load before generating any database access code.
Use when writing or reviewing any Handler, Service, or Repository. Defines how Either, bind(), mapLeft, ensure, and Either.catch are used in this codebase. Load before writing any business logic or database access code.
Use when writing any Route, DTO, or error response. Defines JSON:API document shapes, field rules, Kotlin DTO patterns using elhub-jsonapi, error helper functions, and JSON Schema layout. Load before generating any API response or request DTO.
Use when writing any test.Defines FunSpec structure, MockK patterns for suspend functions, clearMocks usage, Arrow assertions, route test wiring, and integration test extensions. Load before generating any test class.
Use when writing tests for Routes, Handlers, Services, or Repositories. Defines how each layer is tested in isolation and how e2e tests wire the full stack. Load alongside testing-kotest and testing-anti-patterns before writing any test class.
Use when creating or modifying any feature code. Defines the feature/action directory layout, Route/Handler/Error/DTO responsibilities, Module.kt wiring, and shared kernel structure. Load before generating any new feature, action slice, or module.
| name | test-driven-development |
| description | Use when implementing any feature or bug fix. Defines the red-green-refactor cycle and the rule that no production code may be written without a failing test first. Load before starting any implementation work. |
Write the test first. Watch it fail. Write minimal code to pass. Refactor.
RED → write one failing test
↓ confirm it fails for the right reason
GREEN → write minimal code to pass
↓ confirm all tests pass
REFACTOR → clean up, no new behaviour
↓ confirm still green
→ next test
Write one test covering one behaviour. The test must fail before any implementation exists. If it passes immediately, it is not testing anything new.
class CreateHandlerTest : FunSpec({
test("returns Left(AuthorizationError) when party does not match model") {
val repo = mockk<RequestRepository>()
val partyService = mockk<PartyService>()
coEvery { partyService.resolve(any()) } returns mismatchedParty.right()
val result = CreateHandler(repo, partyService).invoke(validModel)
result.shouldBeLeft(CreateError.AuthorizationError)
}
})
Run the test. Confirm it fails because the feature doesn't exist, not because of a compilation error or wrong setup.
Write the minimum code to make the test pass. Do not add behaviour the test doesn't require.
Clean up duplication and naming. Do not change behaviour. All tests must remain green throughout.
suspend functions are mocked with coEvery, not every.beforeTest — see the Testing skill.Before fixing a bug, write a test that reproduces it. The test must fail. Then fix. The test is the regression guard.