What problem does it solve? When building Kotlin Multiplatform apps, it is easy to lose track of where a class belongs, letting DTOs leak into the UI or ViewModels call Retrofit directly. This Skill provides a deterministic rule set for placing every class in the correct layer (Presentation, Application, Domain, Infrastructure, Composition) and for reviewing whether a PR respects dependency direction. ## Core Features & Use Cases - Layer assignment rules: A responsibility table and decision tree map each element (Entity, Use Case, DTO, ViewModel, Koin module, etc.) to exactly one layer. - Dependency enforcement: Invariants and anti-patterns define illegal imports, such as ViewModels knowing Ktor or Entities carrying persistence annotations. - PR review checklist: A checklist and Definition of Done let an agent audit existing code for architectural violations. - Use Case: While adding a new feature, ask where a repository implementation or mapper should live, and get a definitive layer placement plus the allowed dependencies. ## Quick Start Ask the agent to decide which Clean Architecture layer a new class belongs to, or to review a pull request for layer boundary violations.
