Skip to content
nifdinifdi docs

Prompts

Use prompts with either mode of nifdi MCP server: Hosted MCP, which works on cloud diagrams stored in your nifdi account or Local MCP, which works on .nifdi.svg files stored on your machine.

What to ask for

Section titled “What to ask for”

nifdi draws block-and-connector diagrams: boxes, text and icons, joined by arrows. Ask in plain language, as you would a colleague. For example:

  • “Draw the architecture of this repository as a nifdi diagram, grouping services by deployment.”
  • “Make a flowchart of the sign-up process described in this document.”
  • “Recreate the diagram in this screenshot as a nifdi diagram.”
  • “In the payments diagram, add a queue between the API and the worker, and label the arrow retries.”
  • “Make every database in this diagram the same colour, and line the services up in a row.”

nifdi works out the layout. The agent says what goes where — this box inside that one, this label on that edge — and nifdi sizes and places everything, routes the arrows around the boxes, and keeps labels attached to what they describe when anything moves. It is not a freeform drawing canvas, so it suits a picture made of boxes and arrows rather than an illustration or a poster.

Seeing the result

Section titled “Seeing the result”

The agent will use nifdi to render a diagram as a bitmap to check its appearance. You may see these images appear in the chat transcript.

To look more closely yourself, ask for the editor link and open it in your browser. The editor is live: you see the agent’s changes as they happen, and the agent sees yours.

Working together

Section titled “Working together”

Mix asking and editing, using whichever is quicker for the change at hand. Ask the agent for a whole diagram or a sweeping change, then drag, delete and restyle in the editor yourself. The agent reads the diagram afresh before it edits, so it builds on your changes rather than overwriting them.

Undo and history

Section titled “Undo and history”

A diagram has one change history, shared by everyone editing it: you, the agent and anyone else. Each entry records who made the change. The agent can read the history to see what changed, and undo or redo any change, including one you made in the editor. You can undo the agent’s changes in the editor in the same way.