Add DiagramZu to Claude Code or Cursor

When Call before create_diagram to avoid duplicating an existing named diagram — pass q to search title, description, or code. After creating, list again to land on the latest match.

{
  "q": "DB schema",
  "sort": "relevance"
}

When Call when you might place a new diagram somewhere specific. If a folder named "Infra" or "Schema" exists, prefer it over the root.

{}

When Read the description as the brief before deciding what to change.

{
  "id": "dgm_abc123"
}

When Use before a risky overwrite to know what restore points exist.

{
  "diagramId": "dgm_abc123"
}

When Read a past snapshot to understand how the diagram evolved or to recover content the live version no longer has.

{
  "diagramId": "dgm_abc123",
  "versionId": "ver_xyz789"
}

When Always write a description first — it becomes the agent brief for future calls. Set folderId to file the diagram under a human-managed folder.

{
  "title": "User signup flow",
  "description": "Auth path from /signup → verify → first login.",
  "code": "graph TD; A-->B-->C",
  "folderId": "fld_..."
}

When Pass createVersion: true when the change is meaningful — your future self will want a restore point. versionLabel is shown in the history drawer.

{
  "id": "dgm_abc123",
  "code": "graph LR; A-->B-->C-->D",
  "createVersion": true,
  "versionLabel": "added retry path"
}

When Use before simplifying a complex diagram, or as a sanity check that your generated code produces a clean graph.

{
  "id": "dgm_abc123"
}

When Call before create_deck to extend an existing deck instead of duplicating it.

{}

When Read the slide order and titles before reordering or adding slides with update_deck.

{
  "id": "dck_abc123"
}

When Create the slide diagrams first, collect their ids, then pass them in slide order. The URL it returns opens the deck for space members only — to show it to anyone outside the Space, open the deck and create a public link from its Share button.

{
  "title": "System architecture walkthrough",
  "description": "Read in order: context → data flow → deploy.",
  "slides": ["dgm_context", "dgm_dataflow", "dgm_deploy"]
}

When slides is declarative — send the complete desired list of diagram ids; any id you omit is removed, new ids are appended.

{
  "id": "dck_abc123",
  "slides": ["dgm_context", "dgm_dataflow", "dgm_deploy", "dgm_appendix"]
}

When Pass nodeId to read just one node's thread; resolved threads are included unless you set includeResolved: false.

{
  "diagramId": "dgm_abc123",
  "includeResolved": false
}

When Leave structured review findings a human will see on the diagram. Pin to a node with nodeId, or reply to a thread with parentId.

{
  "diagramId": "dgm_abc123",
  "nodeId": "PaymentService",
  "body": "This should call the retry queue, not the DB directly."
}