draw

/draw — Create Diagrams in YuzuDraw

Use this as the single entrypoint for diagram work. Select one family, open the matching reference, then write DSL.

Workflow

1. Classify the request into one primary diagram family.
2. Open the matching reference file under references/.
3. Follow that reference's defaults instead of improvising a generic style.
4. Pass DSL to CLI commands using a heredoc with --dsl-stdin (see CLI Invocation Rules below). Every command MUST start with yuzudraw-cli — never use pipes, cat, or echo.
5. Always display the rendered ASCII output in a fenced code block in your response so the user can see it directly without expanding tool results.
6. After rendering, ask the user if they'd like to save the diagram (via create-diagram or update-diagram). Always prompt — don't assume they only wanted a preview.

If a yuzudraw-cli command fails with "command not found", ask the user to install it with curl -fsSL https://www.yuzudraw.com/install.sh | sh, then retry.

CLI Invocation Rules

Every CLI call MUST start with yuzudraw-cli so it can be allowlisted. Pass DSL inline via heredoc — no temp files, no pipes, no cat/echo.

• Render:

  yuzudraw-cli render-ascii --dsl-stdin <<'EOF'
  rect "hello" id box at 5,5 size 10x3
  EOF
  

• Create:

  yuzudraw-cli create-diagram --name <name> --dsl-stdin <<'EOF'
  ...DSL...
  EOF
  

• Update:

  yuzudraw-cli update-diagram --name <name> --dsl-stdin <<'EOF'
  ...DSL...
  EOF
  

Do NOT use pipes (cat file | yuzudraw-cli), --dsl-file, or any command that does not start with yuzudraw-cli.

Family Selection

Open architecture.md when the request is about:

• system topology
• regions, zones, groups, tiers
• cross-boundary relationships
• repeated nodes and framed areas
• high-level runtime structure

Open components.md when the request is about:

• modules, packages, services, subsystems
• interfaces, APIs, dependencies
• internal product structure
• ownership or containment boundaries