What problem does it solve? It helps developers avoid common architectural mistakes such as tangled business logic, generic naming, and reinventing existing solutions by enforcing Clean Architecture and Domain-Driven Design rules during coding and design work. ## Core Features & Use Cases - Architecture Guidance: Applies DDD and Clean Architecture principles, separating domain entities from infrastructure and keeping business logic framework-independent. - Code Style Rules: Enforces early returns, function and file size limits, arrow functions, and domain-specific naming instead of generic utils/helpers modules. - Library-First Decision Making: Directs evaluation of existing libraries and SaaS solutions before writing custom code, with clear criteria for when custom code is justified. - Use Case: When designing a new order-processing module, use this Skill to structure bounded contexts, name components like OrderCalculator instead of utils, and decide whether to adopt an existing library or write custom logic. ## Quick Start Ask the assistant to review or design your module's architecture following Clean Architecture and DDD principles with proper naming and separation of concerns.
