squinch architecture diagrams as code for coding agents

Your coding agent already knows the architecture.
Now it can draw it.

Describe the system in a paragraph. Squinch turns it into a clean, professional diagram — layout you steer without placing a box, vendor-accurate icons, and altitudes you can zoom through, from the whole landscape down to one service's internals. It ships as a skill for the agent you already use — one install and it speaks the language.

A paragraph is typed into a prompt box describing a products API on AWS. A status line reads Thinking, then Using squinch skill, then Finalizing diagram, and the finished diagram rises underneath it, every element from the sentence drawn with its real vendor icon.

On a landscape of five systems, clicking a service card opens it into its own internals while the rest stay as muted context. The breadcrumb closes it again, and the view cuts to full detail with every system open at once before returning to the landscape.

Multiple altitudes, one model

Zoom into any system

The altitudes are derived, never drawn twice: a collapsed system is a card previewing what's inside, and opening it shows the internals while the neighbours it talks to stay on screen as muted context. Edges that cross the boundary re-anchor themselves. One model, every altitude — no second diagram to maintain, so nothing can drift.

Motion carries meaning

Packets down a queue, a slow dashed archive job, a comet on the final push — cadence you can read, from CSS keyframes and never script.

A notification pipeline: events queue, a worker archives and pushes to the customer

Real deployment boundaries

VPCs, subnets, cloud and on-prem zones: nested, tinted by kind, labelled where you'd expect them.

Nested cloud, VPC and on-premises zones drawn as dashed boundaries around their members

1,358 vendor icons

AWS, Azure, Google Cloud, Kubernetes and the products around them — Kafka, Postgres, Datadog — not grey boxes with labels inside.

Beyond the clouds — product logos alongside cloud vendor icons

Light and dark, both designed

One file, both palettes

--adaptive renders the pair off one shared layout and merges them, so a single SVG follows the reader's system theme — in a README, a wiki, a pull request. Pack artwork is never recoloured: a vendor's mark stays its own colour on either ground.

The same diagram in the light palette, on the same layout

Deterministic, not best-effort

Diagrams you can commit

The same bytes on every machine

One source, one SVG — identical on macOS, Linux and Windows. Your diff shows what you changed, never what your laptop did.
The font ships with the renderer

Text is measured against a bundled metrics table, never against the machine it runs on. Nothing reflows because someone else installed a different font.
Renders offline. No telemetry.

Rendering never touches the network and tells nobody. No account, no icon fetched at render time, nothing about you or your diagrams leaves the machine.
Rigorously tested, agents included

Independent cold agents get a prose brief, the skill and the CLI — nothing else. Every diagram they write is committed and re-scored by CI.