What problem does it solve? Monoliths without clear internal structure degrade into big balls of mud, while adopting microservices too early creates distributed complexity. This Skill provides architecture principles for building monoliths with enforced module boundaries, clean contracts, and a viable path to microservices extraction later. ## Core Features & Use Cases - Module Boundary Definition: Identify bounded contexts, size modules correctly, and define public API contracts via index exports. - Communication Patterns: Decide between synchronous public API calls and asynchronous event-driven communication with a decision framework. - Data Isolation & Shared Kernel Rules: Enforce per-module data ownership, minimize shared code, and prevent cross-module coupling. - Use Case: When starting a new application that doesn't justify microservices, use this Skill to structure modules (users, orders, notifications) with isolated data, event-driven side effects, and a composition root — so any module can later be extracted into a service with only communication-layer changes. ## Quick Start Ask the AI to design a modular monolith structure for your application with defined module boundaries, public APIs, and event-based communication.
