What problem does it solve? Technical documentation often lacks clear, consistent diagrams that accurately reflect the approved architecture, leading to confusion between aspirational designs and the real system. This Skill produces Mermaid diagrams that stay aligned with the modulith, multi-tenancy, and stack decisions already documented in the repository. ## Core Features & Use Cases - Architecture and flow diagrams: Create flowcharts, sequence diagrams, ERDs, state diagrams, and Gantt timelines for modules, authentication flows, domain events, and delivery phases. - Architecture-aligned conventions: Enforces rules such as explicit tenant resolution, bounded context separation, and no undocumented microservices, so diagrams never contradict approved ADRs. - Quality checklist and anti-pattern review: Detects illegible diagrams, generic boxes, cross-module data coupling, and missing actors before the diagram ships. - Use Case: While writing an ADR for the authentication module, ask for a sequence diagram of the login and refresh token flow that explicitly shows where tenant resolution and auditing occur. ## Quick Start Ask the assistant to create a Mermaid sequence diagram of the login flow showing where authentication, tenant resolution, and auditing happen in the modulith.
