What problem does it solve?
Keeps Kotlin/Spring teams from drifting away from the project’s mandatory Controller → Facade → Service coordination, CoreException-based error handling, DTO conversion chain, and layered domain-event expectations when implementing new features or modifying existing logic.
Core Features & Use Cases
- Layered Workflow: Enforces Controller->Facade->Service sequencing, read-only queries, horizontal dependency rules, and Korean ApiSpec separation so APIs stay consistent; consult
references/layer-boundaries.md and references/api-patterns.md.
- Domain Safety Nets: Prescribes CoreException + ErrorType messaging with
[field = $value] prefixes, rich DTO flows, event naming/versioning, entity encapsulation, and null-safety best practices documented in the various references/*.md files.
- Operational Consistency: Lists expected patterns for caching, event listeners, naming, and message formatting so every Kotlin/Spring implementation matches the Loopers template guidelines.
Quick Start
Ask for implementation guidance when updating domain logic so the Controller, Facade, Service, DTO, event, and caching flows remain aligned with the project standards.