← The Thermite family

Thermite Schematics

Clear drawings. Shared knowledge.

Electrical schematics as code. Describe a system in JSON; a compiler checks it and generates the drawings, schedules, and reports. Free, open source, and built for people and AI agents.

From model to drawingOpen-source alpha
Electrical documentation, built from data

The idea

Good documentation should be easier to create—and easier to share.

Equipment, terminals, connections, and potentials form a structured project in JSON. A compiler checks that model, and the drawings are generated from it: the same model and tool version produce the same sheets, byte for byte. Nobody redraws a sheet after a change. Change the model, and the drawings, schedules, and lists follow.

Check every connection.

Every endpoint you declare must be a real terminal on a real device. Duplicate tags are rejected, the voltage declared for a net is compared with the ratings of the terminals on it, and terminals left unconnected are listed. Nobody has to hunt for those mistakes page by page, and neither does your agent.

Generate the documentation.

Render SVG, HTML, and PDF drawings, printable multi-view packets, cable and terminal views, PLC I/O schedules, and BOM and wire/cable CSV reports. Rendering the same model again gives identical files.

Give people and AI common ground.

Use readable project files and guarded agent tools to inspect connections, review proposed edits, and validate changes before applying them.

Built for agents

The compiler does the checking.

Checking a drawing set connection by connection is slow work for a person and a poor use of an AI agent. Thermite Schematics gives that job to a compiler. Your agent can edit the JSON directly, or use the guarded patch tool, which compiles a change before writing it. No assistant is built in and there is no MCP server to install: every tool is a command.

Inspect
inspect, neighbors, trace, and net answer questions about the model without opening a drawing
Change
A patch names the file contents it expects, can be tried as a dry run, and is refused if the patched project does not compile
Diagnose
Each diagnostic carries a code, the file, and the line, so your agent goes straight to the fault
Review
snapshot and review list what changed in the model: devices, wires, and the devices they touch
Read the agent guide on GitHub
AGENT SESSION

YouAdd a part-present proximity sensor, B1, in the field. Wire it to PLC1’s first input.

AgentI’ll snapshot the model, then propose the change as a dry run so the compiler checks it before anything is written.

Run thermite snapshot -o drawings/before.jsonsaved

Write requests/add-b1.request.jsondevice B1 and three wires, as a dry-run patch

Run thermite agent apply-source-patch --input requests/add-b1.request.jsonrefused, nothing written: E102 Device "PLC1" of type "core:plc-compact" has no terminal "X1.2".

Run thermite inspect PLC1terminals L+, M, X1.0, X1.1, X2.0, X2.1; the first input is X1.0

Edit requests/add-b1.request.jsonsignal wire now lands on PLC1.X1.0

Run thermite agent apply-source-patch --input requests/add-b1.request.jsondry run passes: the patched project compiles

Run thermite agent apply-source-patch --input requests/add-b1.apply.request.jsonapplied: 2 files changed

Run thermite view B1 --to PLC1 --include-power -o drawings/b1-to-plc1.svgWrote 1 sheet(s)

Run thermite review --before drawings/before.json4 semantic changes: device B1, wires W-CTL-003 to W-CTL-005

AgentB1 is in the model and drawn. The compiler refused my first patch: I had landed the signal on X1.2, a terminal PLC1 does not have. The change is a diff in your repository, ready for an engineer to review.

YouGood. I’ll review the sheet and the diff.

Illustrative walkthrough with an example project and values, in the style of a Claude Code session. “thermite” is short for “bun thermite.mjs”. The compiler’s message and the drawing are real output.

Under the surface

One model. Useful outputs.

Source model
Structured electrical project data (JSON)
Checks
Endpoints, duplicate tags, declared voltage against terminal ratings
Output
Deterministic SVG, HTML, and PDF drawings and packets
Supporting documents
Terminal and cable views, I/O schedules, BOM, wire and cable lists
Agent tools
Six stateless commands, with dry-run patches
License
Apache-2.0
Current stage
Public alpha
K1 / control · sheet 1 of 1
Generated control sheet for contactor K1, cropped to the main panel: PLC1 output X2.0 leaves for the stop push-button, and the circuit returns through overload contact OL1 to the K1 coil, with every wire labelled
Wire list · CSV report
Conductor / labelEnd AEnd BColor / size
W-CTL-005 / PLC1-DO0-STOPPB1.11PLC1.X2.0blue / 18AWG
W-CTL-006 / STOP-OL1-NCPB1.12OL1.95blue / 18AWG
W-CTL-007 / OL1-NC-K1-A1OL1.96K1.A1blue / 18AWG
W-CTL-008 / K1-A2-0VPS1.-K1.A2blue/white / 18AWG
Part of a control sheet and its wire list, both generated from the motor-starter example in the repository. Open the full sheet.

Your next step

Let’s put good thinking
to work.

Talk about Thermite Schematics