jOOQ DDL-based code generation and runtime configuration. Use when setting up jOOQ codegen, writing blocking JDBC repository implementations, or troubleshooting identifier case issues.
Arrow-kt patterns for this Clean Architecture Kotlin project. Use when writing or reviewing code that involves error handling with Either, either{} DSL, bind(), mapLeft(), Either.catch(), ensure(), or fold(). Covers all Arrow-kt APIs used in domain, application, infrastructure, and presentation layers.
Clean Architecture rules and patterns for Kotlin + Spring Boot + Arrow-kt projects. Use when implementing or reviewing any CA layer: domain modeling, use case design, repository patterns, infrastructure implementation, or controller/DataFetcher wiring. Triggers on: domain entity design, value object creation, repository interface definition, use case implementation, jOOQ repository, REST controller, DGS DataFetcher, DI wiring.
Functional programming patterns for Kotlin with Arrow-kt. Use when writing immutable domain models, designing pure functions, working with Either error handling, creating value objects, or applying sealed interface error hierarchies. Triggers on: value object design, Either usage, sealed class/interface design, entity mutation patterns, extension function mapping.
SDD (Specification-Driven Development) for Kotlin CA/FP projects. Produces precise, layer-aware spec files that drive tests and implementation. Use when planning a feature, designing the domain model, specifying API contracts, or writing acceptance criteria. Triggers on: spec writing, feature planning, domain model design, error hierarchy design.
SDD+TDD workflow for this Clean Architecture Kotlin project. Use when implementing a new feature end-to-end: spec → tests (red) → implementation (green) → refactor. Covers spec-to-layer mapping, test-first patterns per layer, coroutine testing, property-based testing, and the red-green-refactor cycle.
TDD patterns for Kotlin CA/FP projects using Kotest + MockK + Arrow-kt. Use when writing tests, designing test cases, or following the red-green-refactor cycle. Triggers on: test file creation, writing value object tests, use case tests with mocked repositories, controller tests, property-based testing, coEvery/coVerify patterns.