generate-diagram

Generate an Azure architecture diagram from a natural-language description.

Workflow

1. •Parse the user's architecture description from $ARGUMENTS
2. •Write a valid redspec YAML spec based on the description
3. •Save the YAML file to disk (use a descriptive filename based on the description, e.g., three-tier-web-app.yaml)
4. •Run redspec generate <yaml_file> to produce the diagram (optionally with --direction LR --dpi 200 for wide architectures or presentations)
5. •Report both output file paths to the user

YAML Schema Reference

The YAML file has three top-level sections:

diagram:
  name: "<Diagram Title>"
  layout: auto
  direction: TB       # TB, LR, BT, RL
  theme: default      # default, light, dark
  dpi: 150            # 72-600

resources:
  - type: azure/<resource-type>
    name: <unique-name>
    children:          # only for container types
      - type: azure/<resource-type>
        name: <unique-name>

connections:
  - from: <source-name>
    to: <target-name>
    label: <optional-label>
    style: dashed           # optional
    color: "#0078D4"        # optional hex color
    penwidth: "2.0"         # optional thickness
    arrowhead: vee          # optional: vee, dot, diamond, normal, none
    direction: both         # optional: forward, back, both, none

Supported Azure Resource Types

Container types (can have children):

• •azure/resource-group — gray dashed box
• •azure/vnet or azure/virtual-network — blue box
• •azure/subnet — purple box
• •azure/subscription — yellow box

Leaf resource aliases:

You can also use any full Azure icon name (e.g., azure/application-gateways).

Edge Styling

• •Use color on key edges: blue #0078D4 for primary, green #107C10 for AI/ML, red #D83B01 for security, purple #5C2D91 for identity
• •Use arrowhead: vee for modern look
• •Use direction: both for bidirectional flows (sync, replication)
• •Use penwidth: "2.0" to emphasize critical paths

Rules

• •Every resource name must be unique across the entire spec (including nested children)
• •Use azure/ prefix for all resource types
• •Container types can nest other containers (e.g., resource-group > vnet > subnet > app-service)
• •Connections reference resources by name — they work across any nesting level
• •Group related resources logically in resource groups and VNets
• •Add meaningful connection labels describing the data flow

CLI Command

redspec generate <yaml_file>
# Output: organized folder in ./output/<slug>/

redspec generate <yaml_file> -o <output.png>
# Output: direct file (backward compatible)

redspec generate <yaml_file> -d ./my-output/ --direction LR --dpi 200
# Output: organized folder with overrides