eda

schematic capture + pcb layout + manufacturing output, in your drive. vibePCB.

boards

a board is a .pcb.md. its got:

schematic (declarative sdk)
footprints (referenced from /ics)
layout (auto + manual)
design rules (frontmatter or project defaults)

example:

---
kind: pcb
name: motor-driver-v1
layers: 4
size_mm: [50, 30]
---

<Board>
  <Net name="VBAT" />
  <Net name="GND" />
  <Component ref="U1" ic="drv8313" />
  <Component ref="C1" value="10uF" footprint="0805" />
  <Wire from="U1.VM" to="VBAT" />
  <Wire from="U1.GND" to="GND" />
</Board>

ics as library

every chip you use is a .ic.md in /ics/ with datasheet + footprint. the ic= reference on a component resolves to an ic file in your drive. agents can add a chip to your library from a vendor datasheet url fr.

auto-routing

pcb.route(net) in an agent tool or the auto-route button in the ui. freerouting under the hood. manual routing is available for anything picky.

drc

design rule check runs on save. errors inline with clickable markers. project-level defaults in /.vibe/eda/drc.md.

fab output

gerbers
drill files
pick-and-place
bom in csv or mouser/digikey format

one click export for fab → jlcpcb | pcbway | oshpark | macrofab. each exporter matches their specific format + rules.

compared to kicad

smaller scope rn. what you give up: plugin ecosystem, decades of community libraries, hierarchy depth. what you get: agent-native workflow, one-drive compat with your cad + sim + bom + products, shareable via link, no install. different bet.