Load when checking the name and label conventions for branches, commits, issues, and PRs. The single source for the three title formats (issue/PR/commit), branch strategy, commit types, and label/assignee rules. The actual execution procedures live in the…
Load when designing the layer structure or deciding where new-feature code goes. Holds per-layer responsibilities and package placement; details on transaction boundaries, the web layer (DTO/response/Swagger), and integration (pagination/events) are split…
The review lens for daruda server code — the layer-boundary/transaction/convention/exception/performance/security/style checklist, severity rules, and the Korean output format. Read by the code-reviewer agent; also load it directly when reviewing a diff.
Load when handling exceptions/errors. Holds the BusinessException hierarchy and ErrorCode-addition rules; the GlobalExceptionHandler handling list, response format, and auth exceptions are split into references/.
A list of known cleanup targets in existing code written before the guidelines were unified. Load when doing refactoring work, or when you find a rule violation in existing code and need to judge whether it is "newly introduced or was already there".
Load when writing or modifying tests. Holds the JUnit 5 + Mockito (BDD) + AssertJ base structure and required rules; per-layer strategy, fixtures, and anti-patterns are split into references/.
Load when writing or modifying Java code. Holds the core naming, Lombok, and Checkstyle rules; formatting/import-order details and entity/service writing idioms are split into references/.