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

sample prompts

Colby Knox ·2a64f8978b ·15d ago ·parent ad2724b

1 file changed +19−1

package.json+19−1

@@ -52,5 +52,23 @@   "scripts": {     "install": "./install.sh",     "uninstall": "./uninstall.sh"-  }+  },+  "sample_prompts": [+    {+      "label": "Compare the bridges",+      "prompt": "which altium bridge features is the kicad bridge missing?"+    },+    {+      "label": "Port a check",+      "prompt": "add the return path check to the kicad bridge using the eda bridge standard"+    },+    {+      "label": "Read the board model",+      "prompt": "what does the board model json from routing_state look like?"+    },+    {+      "label": "Start a new bridge",+      "prompt": "I want to write a bridge for a new PCB tool: what verbs and replies does the standard expect?"+    }+  ] }