technicaldiagrams.comv0.1 · visual references for agents
← Data structures

Object tree

Expand a hierarchy without losing parent context.

Visual 86/100Edit 95/100Balanced 90/100Editorial baseline · revision 1
Object treeExplain a JSON document or nested configuration structure. All values are illustrative example data.The shape of a documentJSON structure · field types1document2├── id: string3├── title: string4├── author5│ ├── id: string6│ └── name: string7└── tags: string[]
Live SVG · all content is illustrative

Make it yours

Edit labels & content

Change the text directly. Use the scene editor to move or add elements.

Edit individual elements

Choose a shape or text element, then change its properties. Related labels and connectors have separate coordinates.

Edit scene JSON

Change positions, dimensions, paths, and labels. Apply validates the scene before changing the preview. Primitive reference ↗

Review this diagram

Your scores and review history stay in this browser. Export reviews to propose a catalog update. Read the rubric.

    Use this when

    Explain a JSON document or nested configuration structure.

    Choose another form when

    Most relationships are many-to-many.

    Built from

    Text blockLabel

    Indented text is cheap to edit and handles hierarchy without complex geometry.

    Initial editorial assessment by Codex · 2026-09-07. Scores are judgments about this example, not a benchmark of AI capability.

    Give your agent this reference

    Use the example to show your agent the form you want. Describe your system or provide your source material, then ask it to generate an adapted diagram and inspect the result.

    Includes the reference URL, current scene, and settings. Paste it into your own agent.

    Read the agent workflow ↗

    Take the source

    The SVG is self-contained. The JSON preserves editable primitives and your presentation settings. Labels remain text; shapes remain vectors.

    Original scene JSON ↗
    Controls, limits, and embedding ↗