← Commit history

6 use cases — transparent Chrome frames, full UIs, 3 live app screenshots (chip-fetcher, symbol)

John Lauer ·162e8fa958 · ·parent 817ae0a
8 files changed +35−15
README.md+30−13
@@ -24,8 +24,8 @@ acting only on the commands you give it.  ## What it does for you -Three real apps from the Adom ecosystem — each shown running **in a Chrome window the extension drives** (note-the **"Adom driving"** badge in the toolbar) — and how it helps you get the work done.+Six real apps from the Adom ecosystem — each shown running **in a Chrome window the extension drives** (note+the **"Adom driving"** badge in the toolbar), and how it helps you get the work done.  ### Web-based oscilloscope — verify an instrument UI without clicking through every iteration ![A web-based oscilloscope running in a Chrome window driven by the Adom extension](/blob/app/adom-browser-extension/screenshots/usecase-oscilloscope.png)@@ -34,19 +34,36 @@ signals. Instead of clicking through it by hand each pass, your AI assistant dri Chrome — sets the timebase, drags the trigger to **CH1-rising**, reads the measurements back, and screenshots the result. You stay in flow while it verifies the instrument and flags a regression the moment one appears. -### Web-based EDA & CAD — try a design change and see it routed, hands-free-![A browser EDA/CAD tool running in a Chrome window driven by the Adom extension](/blob/app/adom-browser-extension/screenshots/usecase-eda.png)-Mid-design you want to try a change and see it routed. Your AI opens the EDA tool in the browser you're-already signed into, **fills the schematic, re-runs the autorouter, and inspects the nets** — turning "try this-and tell me what breaks" into something it just does, in the same session where your part libraries and logins-already live.+### Chip-fetcher — fill your CAD library while you keep designing+![The chip-fetcher dashboard running in a Chrome window driven by the Adom extension](/blob/app/adom-browser-extension/screenshots/usecase-chipfetcher.png)+Sourcing CAD for a BOM is tedious — symbol, footprint, 3D model, and datasheet for every part. Your AI drives+the chip-fetcher dashboard in your browser, working down the parts list and pulling each one's full CAD bundle+into your library, so the components are ready to drop into your design instead of you hunting them down one+tab at a time. -### Apps that drive real circuit boards — hardware-in-the-loop in your actual session+### Adom Symbol — schematic symbols, generated and previewed live+![Adom Symbol running in a Chrome window driven by the Adom extension](/blob/app/adom-browser-extension/screenshots/usecase-symbol.png)+You need a schematic symbol for a chip — pins grouped sensibly, the 3D package shown right on the symbol. Your+AI drives Adom Symbol in the browser, generating the symbol from the datasheet pinout, arranging the pins by+function, and embedding the 3D model — then previews it live so you can eyeball it before it lands in your library.++### Web-based EDA & CAD — try a design change and see it routed+![A browser EDA/CAD schematic running in a Chrome window driven by the Adom extension](/blob/app/adom-browser-extension/screenshots/usecase-eda.png)+Mid-design you want to try a change and see it routed. Your AI opens the EDA tool in the browser you're already+signed into, **fills the schematic, re-runs the autorouter, and inspects the nets** — turning "try this and+tell me what breaks" into something it just does, in the same session where your part libraries already live.++### 3D board CAD — review the layout in the browser ![A 3D PCB in a browser CAD viewer running in a Chrome window driven by the Adom extension](/blob/app/adom-browser-extension/screenshots/usecase-board.png)-When a board-control app talks to real hardware, the AI needs your **actual** browser — your device session,-your USB permissions, your dashboard login. The Extension gives it exactly that: it drives the live page,-flashes and operates the board, and reports back — so hardware-in-the-loop testing runs hands-free instead of-you babysitting every flash.+Before a board goes out, you want to look at the actual layout. Your AI opens the 3D board viewer in your+browser, frames the camera, hides a component to see the traces underneath, and re-runs the autorouter — so+reviewing a PCB is a conversation, not a context-switch into a separate desktop tool.++### Adom Chipsmith — check a part fits its footprint before it ships+![Adom Chipsmith chip-on-pads validation running in a Chrome window driven by the Adom extension](/blob/app/adom-browser-extension/screenshots/usecase-chipsmith.png)+Before a part goes onto a board, its 3D model and footprint have to actually line up. Your AI drives Adom+Chipsmith in the browser to drop the chip onto its pads and check the fit visually — catching a mis-seated or+wrong-variant model before it ever reaches the PCB.  ## Every permission, justified 
package.json+5−2
@@ -24,11 +24,14 @@     "skills/driving-gusto/SKILL.md",     "skills/reading-google-messages/SKILL.md",     "screenshots/hero-v5.png",+    "PRIVACY.md",+    "privacy.html",     "screenshots/usecase-oscilloscope.png",+    "screenshots/usecase-chipfetcher.png",+    "screenshots/usecase-symbol.png",     "screenshots/usecase-eda.png",     "screenshots/usecase-board.png",-    "PRIVACY.md",-    "privacy.html"+    "screenshots/usecase-chipsmith.png"   ],   "scripts": {     "install": "./install.sh",
screenshots/usecase-board.png
⋯ 1 unchanged line ⋯
screenshots/usecase-chipfetcher.pngadded
⋯ 1 unchanged line ⋯
screenshots/usecase-chipsmith.pngadded
⋯ 1 unchanged line ⋯
screenshots/usecase-eda.png
⋯ 1 unchanged line ⋯
screenshots/usecase-oscilloscope.png
⋯ 1 unchanged line ⋯
screenshots/usecase-symbol.pngadded
⋯ 1 unchanged line ⋯