Pimp My IDE / garage dispatchBack to the garage
October 8, 2026 / interface craft / field note

A diagram needs a proof layer.

Agent-made diagrams are getting better at composition. Review still needs to ask what the picture kept, what it dropped, who owns each route, and which claims have evidence.

Pretty geometry does not verify the system.

The diagram generator is now a real artifact.

Diagram Design appeared on GitHub Trending on October 8. Its repository ships templates and a skill for 42 diagram types. The output is self-contained HTML and SVG. Static output is the default. Optional motion keeps a complete static first frame and adds controls when interaction is available.[1]

The project also treats reduction as a recorded decision. Its import flow can redraw draw.io, Mermaid, and Excalidraw sources. A fidelity ledger records merged, collapsed, and dropped content. That ledger is the part worth stealing for any generated technical picture.[2]

A diagram should carry a receipt for every useful thing it leaves out.

Composition and truth are separate jobs.

A clean route can still omit a retry path. A tidy stack can hide the owner of a shared service. A highlighted database can look proven when the only input was a prompt. Review the information model before praising the layout.

Diagram Design makes this split concrete. It has source checks for names, labels, geometry, and packaged files. It also has rendered checks for clipping and overflow. We downloaded commit f4547ee and ran its packaged self-check against the included architecture example. The checker returned OK. That result covers the example against the packaged checker. It does not prove the architecture shown inside the example.[2]

The fallback needs words.

MDN recommends an accessible name for inline SVG. A short graphic can use a title. A complex graphic can add a desc or reference visible text. The visible explanation still matters because a diagram often carries more detail than a short accessible name can hold.[3]

Keep the summary, decisions, and evidence outside the picture too. The graphic should help readers see relationships. It should not become the only place where ownership, failure behavior, or proof exists.

Put four layers on the review bench.

  • Structure names the components and directed connections.
  • Ownership names the team, process, or service responsible for a boundary.
  • Failure shows timeout, retry, rollback, or dead-end behavior.
  • Evidence links the pictured claim to a trace, test, configuration, or source.

The light table below replaces a plain checklist with separate overlays. Each native checkbox controls one review layer. The copyable card records selected sections and leaves evidence fields open.

Interactive makeover / diagram review

Stack the proof plates.

This replaces a generic diagram checklist with a light table that shows which information layer is present. The controls select a review packet structure. They do not verify the pictured system.

Select layersInspect the stackCopy review card

Review layers

Select the information your review packet must contain. Structure and ownership are selected by default.

Choose diagram review layers
Live stack / review-only model

Inspection light table

2 layers selectedReview packet structure is incomplete. Failure and evidence sections are still open.
Sources read / October 8, 2026

Source log

Open the evidence boundary
  1. GitHub Trending, read October 8, 2026. Diagram Design appeared in the daily repository list. Trending position and star counts change over time.
  2. Diagram Design repository and documentation, read at commit f4547ee95f88e5b28a52517feff6b6c11cc657f9 on October 8, 2026. We read the output, motion, import, fidelity-ledger, accessibility, geometry, and rendered-check documentation. We downloaded that revision and ran skills/diagram-design/scripts/self_check.py against its included example-architecture.html. The command returned OK.
  3. MDN: SVG in HTML introduction, read October 8, 2026. We read its guidance for role="img", title, desc, aria-labelledby, and visible descriptions.

Evidence boundary: this dispatch reviews public documentation and runs one repository-provided checker against one included example. We did not install the skill into an agent host, generate a new diagram, inspect every verifier, or confirm every claim shown in the project's example diagrams. The light table is an original teaching component. It records requested review sections, not completed evidence.