What problem does it solve? Drawing or auditing a modular-monolith architecture by hand is error-prone: modules drift outside the deployable frame, a second database creeps in, or one module reaches into another module's tables. This Skill produces a correct modular-monolith diagram — one application-shell frame containing module cards over a single shared database with per-module schemas — and enforces the architectural invariants automatically. ## Core Features & Use Cases - Diagram generation: Creates the full modular-monolith layout (outer shell frame, module cards with public-API stubs, in-process event bus, one shared DB cylinder split into schema lanes) through the Excalidash MCP server, including reverse-engineering modules and schema ownership from a repository analysis. - Architecture validation: Runs lint, score, repair, and validate_architecture loops to guarantee one deployable, one shared database, no cross-schema reach-throughs, no module cycles, and a score of at least 95 with zero hard blockers. - Secrets hygiene: Redacts shared-database connection strings and API keys to typed placeholders before any tool call and re-scans exports. - Use Case: Ask to draw "Acme Commerce — one Spring Boot app with Catalog, Ordering, Billing, Identity, and Notifications modules over one shared Postgres" and receive a validated, exportable Excalidraw diagram proving each module owns only its own schema. ## Quick Start Ask the assistant to draw your application as a modular monolith, naming the single deployable, its modules, the allowed cross-module dependencies, and the shared database with its per-module schemas.
