What problem does it solve? Azure architecture diagrams often become inconsistent, cluttered, or dependent on proprietary icon sets, making ownership, containment, and traffic flow hard to read. This Skill provides a self-contained visual language with semantic resource families, containers, connectors, and tokens so diagrams stay accurate and legible. ## Core Features & Use Cases - Semantic resource families: Map ARM resource types to eight families (compute, data, identity, integration, network, monitor, governance, devops) via assets/tokens.json. - Container and connector contract: Nest Subscription, Resource Group, VNet, and Subnet envelopes correctly, and express connector intent (dependency, peering, data, secret, event, telemetry, delivery, approval) through line style, color, and arrows. - Self-contained assets: Use assets/tokens.css, assets/tokens.json, and a self-authored line-art SVG sprite without external icon dependencies. - Use Case: Given a list of Azure resources in a hub-and-spoke network, produce a diagram showing VNet peering, private endpoint attachment, and a CI/CD delivery flow with gated approvals. ## Quick Start Ask the agent to draw a hub-and-spoke Azure network diagram for your listed resources using the azure-topology-style conventions.