Azure Topology Style

Use a restrained Microsoft Learn-like visual language to make Azure ownership, containment, traffic, and delivery flow legible. Load only the assets in this skill; do not assume another diagram package exists.

Start from topology, not decoration

1. Inventory resources with ARM type, logical owner, scope, network placement, and dependencies.
2. Nest Subscription, Resource Group, VNet, and Subnet envelopes accurately.
3. Map every resource to one semantic family through assets/tokens.json.
4. Draw only relationships needed to answer the diagram's question.
5. Label connector intent and direction; do not rely on color alone.
6. Use generic placeholders unless the user supplies publishable names.

Visual contract