architecturelisted

# /architecture — Generate Architecture Diagram (draw.io) ## When to use Visualize system architecture (microservice, layered architecture, network topology) for design docs, ADRs, or stakeholder presentations. ## Input examples ``` /architecture TOPO system: Angular SPA → API Gateway → 3 microservices (Container, Booking, Auth) → SQL Server /architecture --cloud azure deploy architecture: App Service, Azure SQL, Blob Storage, Front Door /architecture integration flow with Customs system via REST API ``` ## Workflow ### Phase 1 — Identify components & trust boundaries List components by group: - **Client**: web app, mobile app, external user (actor) - **Edge**: load balancer, API gateway, CDN - **Service**: backend service/microservice (process box) - **Data**: database, cache, message queue (cylinder/tape) - **External**: third-party system (cloud shape) Identify trust boundaries (internet ↔ DMZ ↔ internal) — draw with container boxes `dashed=1;fillColor=none;`. ### Phase 2 — Layout (L3 preview) Print a block diagram as table/ASCII before generating XML — confirm which groups sit inside which boundaries and the data-flow direction. ### Phase 3 — Generate XML Use `_templates/architecture.drawio` as the frame: - Default to **core shapes** (`ellipse+shape=cloud`, `shape=cylinder3`, `shape=umlActor`, `rounded=1`) — opens on any machine. - If `--cloud aws|azure|gcp`: add matching stencils (`shape=mxgraph.aws4.*`, `shape=mxgraph.azure.*`) and **note clearly in the outp