implementation

Enforce Kotlin/Spring layering, CoreException, DTO, and event standards.

25|1|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/toongri/oh-my-toong-playground --skill implementation-toongri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementation
Source: https://github.com/toongri/oh-my-toong-playground/tree/main/projects/loopers-kotlin-spring-template/skills/implementation
Command: npx skills add https://github.com/toongri/oh-my-toong-playground --skill implementation-toongri

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about implementation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure Kotlin Spring API controllers and services to maintain consistent layering?

Kotlin Spring API layering enforces a Controller to Facade to Service sequence and horizontal dependency rules to keep APIs consistent. This structure ensures read-only queries and domain logic separation when implementing new domain features.

How do I handle errors in a Kotlin Spring project using CoreException?

Error handling in a Kotlin Spring project uses CoreException with ErrorType messaging and specific field prefixes. This mechanism standardizes Korean error messaging across the entire application domain layer.

What is the best way to convert DTOs in a Spring service facade?

The best way to convert DTOs in a Spring service facade is through a rich DTO conversion chain. This process preserves entity encapsulation and null-safety while maintaining strict domain-event expectations.

When do I need domain events and caching in a Kotlin Spring implementation?

You need domain events and caching in a Kotlin Spring implementation when adding transactional flows that require operational consistency. This process dictates event naming, versioning standards, and caching best practices.

Does this Kotlin Spring implementation guideline apply to non-template projects?

This Kotlin Spring implementation guideline specifically applies within Loopers template projects. It standardizes domain logic, API patterns, transactions, and caching flows tailored to that specific environment.