← Commit history

page.json and package.json after the 0.4.2 package publish: the hero stays linked (screenshots/hero.png)

Colby Knox ·680ab693fc ·14d ago ·parent b08e04e
1 file changed +2−51
page.json+2−51
@@ -33,54 +33,5 @@     "port an altium bridge feature to kicad",     "build a new eda bridge",     "bridge parity across eda tools"-  ],-  "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.",-  "files": [-    "README.md",-    "SKILL.md",-    "verbs/standard.json",-    "verbs/coverage.json",-    "schema/board.schema.json",-    "schema/companions.schema.json",-    "docs/board-model.md",-    "docs/conventions.md",-    "docs/coverage.md",-    "tools/generate.py",-    "tools/tiers.json",-    "tools/equivalents/",-    "tools/proposed/",-    "install.sh",-    "uninstall.sh",-    "reference/",-    "screenshots/hero.png"-  ],-  "discovery_pitch": "The one standard for Adom's EDA bridges: shared verbs, one board model, the same checks on Altium, KiCad and Fusion 360.",-  "dependencies": {},-  "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?"-    }-  ],-  "org": "adom",-  "author": {-    "name": "Colby Knox",-    "email": "[email protected]"-  }-}\ No newline at end of file+  ]+}