skill
EDA Bridge Standard: one way for an AI to drive every PCB tool
Public Made by Adomby adom
The standard every Adom EDA bridge follows so one AI can drive Altium, KiCad, Fusion 360 and any future PCB tool the same way: shared verb names in tiers, the board model JSON, reply and refusal conventions, and a coverage table of each bridge against the Altium reference.
← Commit history
fusion-lane: equivalents render_board (fusion_render_board_3d, partial) and export_pos (fusion_export_cpl, partial)
1 file changed
+10
tools/equivalents/fusion360.json+10@@ -539,5 +539,15 @@ "fusion_update_footprints_from_library", "partial", "the plan only, against .lbr files named (a Fusion design's libraries are cloud items); apply is refused with the plan, since Fusion's UPDATE asks about each part in a dialog"+ ],+ "render_board": [+ "fusion_render_board_3d",+ "partial",+ "Fusion's own view of the design's 3D PCB from one side (top, bottom, left, right, front, back, iso), png or jpg, transparent background, width, height, zoom, perspective. No refs framing, rotation only through side iso, and quality high (raytraced) is refused: Fusion's raytracer is the mechanical layer's render_image, for a 3D design"+ ],+ "export_pos": [+ "fusion_export_cpl",+ "partial",+ "the Component Placement List CSV in mm, side all, top or bottom; JLCPCB's own CPL columns come from fusion_jlcpcb_order (cpl-jlcpcb.csv). No ascii or gerber format, inch units, smdOnly or excludeDnp filter" ] }