What problem does it solve? Drawing an accurate microservices architecture diagram by hand is error-prone: shared databases sneak in, sync and async edges get mixed up, and arrows cross labels. This Skill produces a correct microservices topology diagram in Excalidraw — API gateway on top, a row of independent services each owning exactly one datastore, and a queue/event bus for asynchronous traffic — then lints, scores, and validates it against architecture rules. ## Core Features & Use Cases - Topology generation: Creates the full layout (gateway, services row, per-service datastores, bounded-service frames, event bus, sync/async legend) via a dedicated architecture pattern, a template, a prompt structure, or by reverse-engineering a repository's deployables, DB configs, and broker usage. - Architecture validation: Enforces database-per-service ownership, a single gateway front door, solid edges for synchronous HTTP/gRPC calls, and dashed edges for queue/event messages, with a mandatory legend keying both. - Quality loop: Runs lint, score, repair, and polish cycles until the drawing scores at least 95 with zero hard blockers, then saves, versions, and exports it. - Use Case: Ask to diagram an order platform where a Kong gateway fronts OrderService, PaymentService, and InventoryService, each with its own Postgres database, communicating over RabbitMQ — the result is a validated topology with sync/async edges clearly distinguished. ## Quick Start Ask the AI to draw a microservices topology for your system, naming the API gateway, the services, each service's own database, and the queue or event bus used for asynchronous messages.
