Visualize

Show one idea with the fewest elements that carry it. Prefer prose or an equation when a picture adds no understanding.

Discover capabilities

Inspect the current environment's tool descriptions and input schemas for file authoring, diagram rendering, image inspection, and artifact display. Resolve capabilities to actual interfaces before calling them; follow the host's permissions. Tool names and calling conventions vary across harnesses.

Choose Mermaid for relationships, dependencies, flows, sequences, states, trees, and hierarchies. Choose SVG for exact positions, geometry, number lines, vectors, plots, and physical layouts.

A renderer may be an available tool or an installed command-line program. Inspect its documentation before use. If rendering or image inspection is unavailable, offer clearly labeled unverified source or a text diagram; never describe it as a verified image.

Produce

Define the intended concept, concrete elements, and essential relationships. Prune unnecessary labels; aim for roughly 5–7 elements. For example: “Packet at the top, arrows to ordering and retransmission, both feeding reliable stream. Show reliability built from packets.”

Author the source, render a PNG, inspect the actual image, and fix factual or layout errors. Check arrow directions, dependencies, labels, overlap, clipping, and readability. For SVG, compute coordinates and proportions, set a viewBox and dimensions, and leave margins. Rendering success alone does not establish correctness. Re-render and inspect after edits. Save source and the verified image in the host's artifact location or an appropriate project directory, using unique matching names and avoiding overwrites. Return the image's actual path or artifact reference. If no correct image can be produced, explain the limitation; simplify the brief or use prose.

Present