layered-architecture-design

What problem does it solve?

This Skill addresses the problem of circular dependencies and tightly coupled components by prescribing a strict, ordered layering approach where higher layers may depend only on lower layers, improving modularity, testability, and maintainability.

Core Features & Use Cases

• Strict Layer Separation: Defines clear responsibilities for Kernel/Infrastructure, Domain/Logic, Application, and UI layers to avoid bootstrap circularity.
• Dependency Inversion Guidance: Recommends interfaces in higher-level layers with concrete implementations in infrastructure to keep domain code pure.
• Enforcement & Case Study: Shows how to enforce acyclic module graphs with build tools and illustrates the pattern using the mathsets-kt project as a real-world example.

Quick Start

Ask the skill to analyze your project's modules and propose a layered refactor that separates kernel, logic, domain, and infrastructure with explicit interfaces and downward-only dependencies.