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
regenerate after kicad-lane (reference/kicad-1.0.72.json, insiders: thermal_vias, via_fence, height_check, placement_check from engine 0.4.0; placement_check now exact): KiCad 202 of 236
3 files changed
+6−6
docs/coverage.md+2−2@@ -1,6 +1,6 @@ # Coverage: every standard verb on each bridge -Altium bridge 0.2.78 (the reference), KiCad bridge 1.0.71, Fusion 360 bridge 1.13.3. 54 verbs came from other bridges' proposals (tools/proposed/); they are marked *proposed*.+Altium bridge 0.2.78 (the reference), KiCad bridge 1.0.72, Fusion 360 bridge 1.13.3. 54 verbs came from other bridges' proposals (tools/proposed/); they are marked *proposed*. `exact` is the same job under the same or an equivalent name; `partial` does part of it or does it differently (`verbs/coverage.json` names what in `note`); `unsupported` answers `not_supported` for the whole job and is not counted; blank is missing. Generated by `tools/generate.py` from `verbs/coverage.json`; do not edit by hand. @@ -197,7 +197,7 @@ Engineering computed from the board model, not by the tool: one shared engine, s | `net_lengths` | Routed length of every net (or the ones named) on the live board, by layer with its vias; the skew inside each differential pair; and the spread of... | `altium_net_lengths` | `kicad_net_lengths` | | | `pin_pad_check` | Do the footprints fit their symbols? Part by part, the symbol's pin numbers (from the sheet files) against the footprint's pad names (from the board): pins... | `altium_pin_pad_check` | `kicad_pin_pad_check` | | | `place_decoupling` *proposed* | Plan positions for decoupling capacitors beside an IC's power pins (each cap just outside the courtyard, its power pad facing the pin), answered as... | | `kicad_place_decoupling` | |-| `placement_check` | Review the placement before routing: parts whose courtyards (pads and body, grown by a margin) overlap on the same side, parts off the board or over its... | `altium_placement_check` | `kicad_placement_validate / kicad_score_placement` (partial) | `fusion_placement_check` |+| `placement_check` | Review the placement before routing: parts whose courtyards (pads and body, grown by a margin) overlap on the same side, parts off the board or over its... | `altium_placement_check` | `kicad_placement_check` | `fusion_placement_check` | | `plan_fanout` *proposed* | Plan the fanout of a BGA or QFN/QFP: the pad pitch, dogbone or via-in-pad per pad, the escape layer, surface stubs for the outer ring and a via grid for an... | | `kicad_plan_fanout` | | | `plan_route` *proposed* | Plan a path for one net between two pads without changing the board: a grid search around the existing copper that keeps the clearance rules, on the allowed... | | | `fusion_plan_route` (partial) | | `read_sheet_file` | Read a schematic sheet straight from its .SchDoc file, without Altium (it need not be installed or running): every part with its designator, library... | `altium_read_sheet_file` | `kicad_read_sheet_file` | `fusion_read_sheet_file` |
verbs/coverage.json+3−3@@ -6,7 +6,7 @@ }, "proposed": 54, "compared": {- "kicad": "1.0.71",+ "kicad": "1.0.72", "fusion360": "1.13.3" }, "tiers": {@@ -2673,8 +2673,8 @@ "match": "exact" }, "kicad": {- "verb": "kicad_placement_validate / kicad_score_placement",- "match": "partial"+ "verb": "kicad_placement_check",+ "match": "exact" }, "fusion360": { "verb": "fusion_placement_check",
verbs/standard.json+1−1@@ -6,7 +6,7 @@ }, "proposed": 54, "compared": {- "kicad": "1.0.71",+ "kicad": "1.0.72", "fusion360": "1.13.3" }, "tiers": {