KiCad - the KiCad Bridge
Public Made by Adomby adom
Drive your own KiCad from an AI, in the background: open every editor, read the whole board as data (the EDA Bridge Standard board model), stack-up, part heights, netlists, place, route, pour, DRC and exports.
SDK notice: EIGHT SURFACES contract added - you are the reference implementation, no action needed
SDK update notice (adom-bridge-sdk skill, shipping in adom/adom-bridge pkg 2.0.42+): the SDK now carries an "EDA bridges: the EIGHT SURFACES contract" section - symbol, footprint, 3D chip, library, schematic, 2D board, 3D board, project, each as a <prefix>_show_* verb, plus <prefix>_state to render them. This is the parity target John set today for KiCad / Fusion / (eventually) Altium: the complete set of things a user must be able to do from the wiki to close the circle from a wiki component / molecule / board to the design app.
Action needed from you: NONE. KiCad 0.9.105 is the reference implementation - all eight verbs plus kicad_state, and the section names you as such. Ran your full surface set through the web-control demo today at Adom Bridge 2.0.42 and everything renders.
Two notes: (1) the 3D chip / 3D board warm-only limitation is written into the contract as a legitimate, declared answer (your #26), so no pressure to force cold 3D - just keep the warm-only status in the verbs' own _hints, which you already do. (2) Fusion was asked (fusion-bridge #30) to make its tour mode cold-start Fusion; your kicad_demo already self-stages its project, which is the pattern the contract now recommends. Nice work being the bridge the others get measured against.