KiCad schematics
The real schematic, live in the page — pan, zoom, fullscreen.
The living source of truth — for your team and your AI
One project tree for docs and design files. Docs are plain MDX with live blocks — the KiCad schematic, the 3D board, the SPICE sim and the code all run in the page, next to your prose. Synced with GitHub, readable by your team — and your AI. Not screenshots that rot by rev B.
# Power stage — LM317 Input filter, then an LM317 sets the 5 V rail. <KiCadView src="filter.kicad_sch" /> ```spice Version 4 SHEET 1 880 680 SYMBOL lm317 208 96 R0 SYMBOL res 320 160 R0 SYMATTR Value {R2} TEXT 32 280 !.param R2=720 ; @input Ohm ``` ```python cell R1, R2 = 240, 720 # Ω V = 1.25 * (1 + R2/R1) f"V_out = {V:.2f} V" ```
Input filter, then an LM317 sets the 5 V rail.
V_out = 5.00 V
Write the tag — the page runs it. The source of truth is your design files, so the doc can’t drift from the design.
The real schematic, live in the page — pan, zoom, fullscreen.
Orbit the board next to the prose that explains it.
Simulation schematics drawn clean — no screenshots.
Drag a parameter — the circuit re-solves in place.
Python runs in the page — scientific stack included. The result is a value, a table or a chart, not a paste.
Requirement blocks, pinout diagrams, board sim — in work. Tell us what your bench needs.
A code cell executes in the page — Python in the browser, scientific stack included. Whatever the cell returns is rendered: a value, a table, a chart. Computed when you read the doc, not pasted when someone wrote it.
Data too: SQL cells query your CSVs with DuckDB right in the doc. And firmware is next — Arduino/ESP32 simulation so an example sketch can blink for real.
Input filter, then an LM317 sets the 5 V rail. The divider keeps V_out at 5.00 V across the load range.
Thermal margin for the TO-220 is checked in the LiveCode block below.
Write in a rich editor; flip to source with </> anytime. The file stays plain MDX any tool — or agent — can read.
Uploads, docs and a mounted GitHub repo live in one project tree — repo files pinned to exact commits.
Cut REV A to freeze the whole tree — docs and repo files alike. Diff any two revisions; restore any time.
Docs are plain MDX in one tree; blocks carry structure, not pixels. Over MCP, an agent searches the project, answers with citations to the exact doc and revision — and edits pages like a teammate.
// MCP server — shipping during the private preview
No proprietary format. The whole tree is files any tool — or agent — can read and write.
Blocks reference the design itself — nets, BOM, parameters — so an agent quotes the schematic, not a screenshot of it.
MCP tools — search, read with citations, edit — run under the same scoped access grants as your teammates.
The live editor, GitHub sync, revisions and sharing are here now. During the private preview we’re building out the rest.
Requirement blocks with stable IDs and links; the traceability matrix is a derived view, never hand-edited.
Multiplayer on the same doc — cursors, comments, suggestions — on top of today’s scoped sharing.
Take any public project — clone the calculator set, fork the reference design — and make it yours.
Arduino/ESP32 simulation runtimes in the page — firmware examples that actually run.
Repo mounted into the project tree, every file pinned by commit.
Manufacturer datasheets as clean MDX, linked to your components.
Tell us what your flow needs — it shapes the preview.
Give your project a brain before rev B
netbrain is in private preview. Leave your email and tell us what you’re building — we’re onboarding hardware teams in batches.
You’re on the list.
We’ll email you when your seat opens up.