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
0.30.12: coverage reads Fusion 360 bridge 1.13.49 (fusion-bridge#136)
5 files changed
+7−6
README.md+1@@ -158,6 +158,7 @@ Decisions so far (proposals from the KiCad and Fusion bridges, 2026-10-27; issue ## Status +Version 0.30.12: coverage reads Fusion 360 bridge 1.13.49 (public; urgent fix for fusion-bridge#136, no verb changes). Version 0.30.11: coverage reads Fusion 360 bridge 1.13.47 (public; .lbr files without line breaks are rewritten before USE, fusion-bridge#135). Version 0.30.10: coverage reads KiCad bridge 1.0.98 (document_info exact). Version 0.30.9: coverage reads KiCad bridge 1.0.97 (tested on KiCad 10.0.8).
docs/coverage.md+1−1@@ -1,6 +1,6 @@ # Coverage: every standard verb on each bridge -Altium bridge 0.2.88 (the reference), KiCad bridge 1.0.98, Fusion 360 bridge 1.13.47. 67 verbs came from other bridges' proposals (tools/proposed/); they are marked *proposed*.+Altium bridge 0.2.88 (the reference), KiCad bridge 1.0.98, Fusion 360 bridge 1.13.49. 67 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.
package.json+1−1@@ -1,6 +1,6 @@ { "slug": "eda-bridge-standard",- "version": "0.30.11",+ "version": "0.30.12", "type": "skill", "title": "EDA Bridge Standard: one way for an AI to drive every PCB tool", "description": "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.",
verbs/coverage.json+2−2@@ -1,5 +1,5 @@ {- "standard": "0.30.11",+ "standard": "0.30.12", "reference": { "bridge": "altium", "version": "0.2.88"@@ -7,7 +7,7 @@ "proposed": 67, "compared": { "kicad": "1.0.98",- "fusion360": "1.13.47"+ "fusion360": "1.13.49" }, "tiers": { "core": "Read and edit the design. Every bridge provides these: they are how an AI sees and changes a board.",
verbs/standard.json+2−2@@ -1,5 +1,5 @@ {- "standard": "0.30.11",+ "standard": "0.30.12", "reference": { "bridge": "altium", "version": "0.2.88"@@ -7,7 +7,7 @@ "proposed": 67, "compared": { "kicad": "1.0.98",- "fusion360": "1.13.47"+ "fusion360": "1.13.49" }, "tiers": { "core": "Read and edit the design. Every bridge provides these: they are how an AI sees and changes a board.",