EDA Bridge Standard: one way for an AI to drive every PCB tool - Commit

by 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.

Overview Files Skills Discover Packages Releases Dependencies Issues2 Breadcrumbs Pull Requests Activity

← Commit history

fusion-lane: import_part is partial (one display mode)

Colby Knox ·610e06ff2a ·12d ago ·parent 2fb504c

1 file changed +1−1

tools/equivalents/fusion360.json+1−1

@@ -268,7 +268,7 @@  ],  "import_part": [   "fusion_import_part",-  "exact",+  "partial",   "the footprint and symbol specs Altium's bridge takes, into one .lbr (pcbLib/schLib are one file in Fusion); an EAGLE symbol has one look, so one display mode is drawn (mode, default 0); a repeated pad number becomes N@2 on the same pin; the STEP binds through the component (needs symbolSpec and a signed-in Fusion)"  ] }