Adom Hydrogen (Linux)
Public Made by Adomby adom
The Linux platform layer for Adom Hydrogen: Ubuntu, Debian and Fedora, the workspace and the computer.
d8a45ab
name: hydrogen-eda-discovery description: >- Post-setup playbook for discovering which EDA tools the user runs (KiCad, Fusion 360, Altium, OrCAD) on their Linux computer and other machines, and onboarding them into the AI-first electronics workflow. Use when asked to explore what EDA software I use, detect KiCad or Fusion, or on the post-setup discovery pass.
EDA tool discovery & onboarding (run in the background after setup)
You're (likely) a second Claude conversation launched after Hydrogen setup to quietly figure out the user's electronics-design stack and show them what the AI-first Adom workflow unlocks. Be exploratory and opt-in — detect first, then offer; never auto-install or auto-build. Do the detection in the background, then come back with a short, friendly summary + one clear offer.
1. Detect
On this Linux computer, without any bridge
The workspace sees the host's /usr and /opt read-only at /mnt/host/usr and /mnt/host/opt,
and the host's /home at /mnt/host/home, so installs can be found from here:
ls /mnt/host/usr/bin 2>/dev/null | grep -iE '^(kicad|eeschema|pcbnew|eagle|librepcb|horizon-eda)'
ls /mnt/host/opt 2>/dev/null | grep -iE 'kicad|eagle|diptrace|cadence|orcad|librepcb'
ls -d /mnt/host/home/*/.local/share/flatpak/app/org.kicad.KiCad 2>/dev/null # per-user Flatpak
ls -d /mnt/host/home/*/.config/kicad/* 2>/dev/null # KiCad config = versions used
System-wide Flatpaks (/var/lib/flatpak) and snaps are not visible from the workspace; when
nothing turns up, ask instead of concluding "not installed".
Fusion 360 and Altium Designer have no Linux build, so they will not be on this computer.
Driving the tools needs Adom Bridge
Opening a board, running DRC or taking a KiCad screenshot goes through Adom Bridge's bridges
(kicad_*, fusion_*, altium_*). Adom Bridge runs on this computer only once Hydrogen has
installed it (when a Linux build is published for the user's account), so:
adom-bridge ping # anything connected at all?
adom-bridge targets # the user's machines on the Adom mesh
adom-bridge --target <machine> kicad_list_versions '{}' # KiCad installed (+ versions)
adom-bridge --target <machine> fusion_status '{}' # Fusion 360 ("installed but not running" = yes)
adom-bridge --target <machine> altium_readiness '{}' # Altium (altium-bridge)
- On this computer these work while Adom Bridge runs here (Hydrogen installs it when a Linux
build is published for the user's account) and the bridge has a Linux build; otherwise the verb answers
unsupported_on_this_osor nothing connects. See adom-bridge-linux. - On the user's other machines (for example their Windows PC or a Mac) they work through the mesh. Never guess which machine: ask.
- Tools with no bridge (OrCAD, Cadence/Allegro, EAGLE, DipTrace, ...) on another machine:
detect them by install path or running process with
adom-bridge --target <machine> run_script '{"interpreter":"bash","scriptB64":"<b64>"}'(pick the interpreter that machine has).
(Whatever the platform: treat empty output as a timeout, not a negative result.)
2. Branch on what you found
A) KiCad and/or Fusion 360 found — we have bridges, go deep (opt-in)
- Remember it. Write a small prefs file so future threads skip re-detection:
(Also worth a one-line memory note if you keep memories.)mkdir -p ~/.adom cat > ~/.adom/eda-prefs.json <<'JSON' {"primary":"kicad","versions":["10.0"],"machine":"<where it runs>","detectedAt":"<date>", "notes":"KiCad 10 on this Linux computer; Fusion on the user's laptop"} JSON - Show, don't tell — offer to open an example so they see it work:
"Want me to open a sample board in KiCad and pop the 3D viewer so you can see what I can drive?" → use the
pic_programmerdemo flow (hydrogen-self-screenshotand the kicad-bridge skills,adom-wiki pkg install adom/kicad-bridge): open.kicad_sch+.kicad_pcb, symbol/footprint editors, then the board 3D viewer (close the footprint+symbol editors first —kicad_open_3d_viewerattaches to the active editor otherwise). If KiCad is only on this computer and no Adom Bridge runs here, say so and offer what works without it (files, wiki parts, andkicad-cliexports ifcommand -v kicad-clifinds it in the workspace). - Pitch the loop that AI makes effortless — "From here I can export gerbers and help you order the board — JLCPCB, PCBWay, or OSHPark." If they're keen, that's the on-ramp to (4).
- The real unlock — build the glue, publish it. Most fab vendors have no clean API, so the value is AI-built automation: pull from KiCad → stage in the workspace → drive the vendor's upload flow (pup) → order. Offer to vibe-code an uploader/automation app for their fab of choice and publish it to the Adom wiki so the whole community gets it. This is exactly what the wiki is for (see §3).
B) OrCAD / Allegro / EAGLE / other — no bridge yet (the community pitch)
We don't have a bridge for these — but that's an opportunity, not a dead end. Offer:
"You're on OrCAD — we don't have an Adom bridge for it yet, but we have a wiki for sharing apps with the whole community, and we could build one together right now. The KiCad and Fusion 360 bridges are great references for the AI to model the design on — it's probably ~30 minutes of vibe-coding. Then we publish it to the Adom wiki so every OrCAD user gets it. We could all use it. Want to?"
- Reference bridges:
adom-inc/adom-bridge/plugins/kicad/and…/plugins/fusion360/(a Python bridge that the desktop app dispatches to; see the adom/kicad-bridge and adom/fusion-bridge wiki pages for the verb shape). A new bridge = the same pattern (launch app, open files, screenshot, send keys, an optional in-process add-in for the richer API). - Publish flow: the Adom wiki hosts shared apps (
apps/<name>) — see the wiki publish skills. - Building one: adom-bridge-sdk.
C) Nothing detected / unsure
Ask what they design boards in, and whether they'd like a bridge or workflow built. Keep it one friendly question, not an interrogation.
3. The frame (why this matters — say it briefly, don't lecture)
The electronics industry is moving AI-first, and the tools mostly aren't built for it yet. Adom is where that comes together: you build an AI-first app (a bridge, an uploader, a fab-automation glue), publish it to the Adom wiki, and the whole community can install and improve it. KiCad/Fusion bridges, a JLCPCB/PCBWay/OSHPark uploader, an OrCAD bridge — each one makes the next person's AI-first workflow turnkey. The user isn't just configuring their setup; they can contribute the missing piece in half an hour.
4. Etiquette
- Opt-in always. Detect silently; offer the demo/build — don't open apps or write code unprompted. One clear offer beats five questions.
- Don't overpromise vendor APIs. JLCPCB/PCBWay/OSHPark uploads are mostly UI automation
(pup), not clean APIs — frame the uploader as AI-driven glue, and verify pages exist before
templating URLs (
hydrogen-pup). - Respect read-only states (e.g. an expired Fusion subscription is view/query-only).
- Report back to the user concisely: what you found, one thing you can show them now, and one thing worth building.
Related skills
- hydrogen-adom-bridge: the bridge relay and the Linux reality
- hydrogen-bridges: the KiCad / Fusion / pup bridges
- hydrogen-pup — driving fab-vendor upload pages; hydrogen-open-url (platform bootstrap) — opening vendor sites
- the Adom wiki publish skills — sharing the bridge/app you build with the community
---
name: hydrogen-eda-discovery
description: >-
Post-setup playbook for discovering which EDA tools the user runs (KiCad, Fusion 360,
Altium, OrCAD) on their Linux computer and other machines, and onboarding them into the
AI-first electronics workflow. Use when asked to explore what EDA software I use, detect
KiCad or Fusion, or on the post-setup discovery pass.
---
# EDA tool discovery & onboarding (run in the background after setup)
You're (likely) a **second Claude conversation** launched after Hydrogen setup to quietly figure out
the user's electronics-design stack and show them what the AI-first Adom workflow unlocks. Be
**exploratory and opt-in** — detect first, then offer; never auto-install or auto-build. Do the
detection in the background, then come back with a short, friendly summary + one clear offer.
## 1. Detect
### On this Linux computer, without any bridge
The workspace sees the host's `/usr` and `/opt` read-only at `/mnt/host/usr` and `/mnt/host/opt`,
and the host's `/home` at `/mnt/host/home`, so installs can be found from here:
```bash
ls /mnt/host/usr/bin 2>/dev/null | grep -iE '^(kicad|eeschema|pcbnew|eagle|librepcb|horizon-eda)'
ls /mnt/host/opt 2>/dev/null | grep -iE 'kicad|eagle|diptrace|cadence|orcad|librepcb'
ls -d /mnt/host/home/*/.local/share/flatpak/app/org.kicad.KiCad 2>/dev/null # per-user Flatpak
ls -d /mnt/host/home/*/.config/kicad/* 2>/dev/null # KiCad config = versions used
```
System-wide Flatpaks (`/var/lib/flatpak`) and snaps are not visible from the workspace; when
nothing turns up, ask instead of concluding "not installed".
**Fusion 360 and Altium Designer have no Linux build**, so they will not be on this computer.
### Driving the tools needs Adom Bridge
Opening a board, running DRC or taking a KiCad screenshot goes through Adom Bridge's bridges
(`kicad_*`, `fusion_*`, `altium_*`). Adom Bridge runs on this computer only once Hydrogen has
installed it (when a Linux build is published for the user's account), so:
```bash
adom-bridge ping # anything connected at all?
adom-bridge targets # the user's machines on the Adom mesh
adom-bridge --target <machine> kicad_list_versions '{}' # KiCad installed (+ versions)
adom-bridge --target <machine> fusion_status '{}' # Fusion 360 ("installed but not running" = yes)
adom-bridge --target <machine> altium_readiness '{}' # Altium (altium-bridge)
```
- On **this** computer these work while Adom Bridge runs here (Hydrogen installs it when a Linux
build is published for the user's account) and the bridge has a Linux build; otherwise the verb answers `unsupported_on_this_os` or nothing connects. See
**adom-bridge-linux**.
- On the user's **other** machines (for example their Windows PC or a Mac) they work through the
mesh. Never guess which machine: ask.
- Tools with **no bridge** (OrCAD, Cadence/Allegro, EAGLE, DipTrace, ...) on another machine:
detect them by install path or running process with
`adom-bridge --target <machine> run_script '{"interpreter":"bash","scriptB64":"<b64>"}'`
(pick the interpreter that machine has).
(Whatever the platform: treat **empty output as a timeout**, not a negative result.)
## 2. Branch on what you found
### A) KiCad and/or Fusion 360 found — we have bridges, go deep (opt-in)
1. **Remember it.** Write a small prefs file so future threads skip re-detection:
```bash
mkdir -p ~/.adom
cat > ~/.adom/eda-prefs.json <<'JSON'
{"primary":"kicad","versions":["10.0"],"machine":"<where it runs>","detectedAt":"<date>",
"notes":"KiCad 10 on this Linux computer; Fusion on the user's laptop"}
JSON
```
(Also worth a one-line memory note if you keep memories.)
2. **Show, don't tell** — offer to open an example so they *see* it work:
*"Want me to open a sample board in KiCad and pop the 3D viewer so you can see what I can drive?"* → use the `pic_programmer` demo flow (`hydrogen-self-screenshot` and the kicad-bridge skills, `adom-wiki pkg install adom/kicad-bridge`): open `.kicad_sch` + `.kicad_pcb`, symbol/footprint editors, then the **board** 3D viewer (close the footprint+symbol editors first — `kicad_open_3d_viewer` attaches to the active editor otherwise).
If KiCad is only on this computer and no Adom Bridge runs here, say so and offer what works
without it (files, wiki parts, and `kicad-cli` exports if `command -v kicad-cli` finds it in
the workspace).
3. **Pitch the loop** that AI makes effortless — *"From here I can export gerbers and help you
order the board — JLCPCB, PCBWay, or OSHPark."* If they're keen, that's the on-ramp to (4).
4. **The real unlock — build the glue, publish it.** Most fab vendors have no clean API, so the
value is AI-built automation: *pull from KiCad → stage in the workspace → drive the
vendor's upload flow (pup) → order.* Offer to **vibe-code an uploader/automation app** for
their fab of choice and **publish it to the Adom wiki** so the whole community gets it. This
is exactly what the wiki is for (see §3).
### B) OrCAD / Allegro / EAGLE / other — no bridge yet (the community pitch)
We don't have a bridge for these — **but that's an opportunity, not a dead end.** Offer:
> *"You're on **OrCAD** — we don't have an Adom bridge for it yet, but we have a wiki for
> sharing apps with the whole community, and we could **build one together right now**. The
> KiCad and Fusion 360 bridges are great references for the AI to model the design on — it's
> probably ~30 minutes of vibe-coding. Then we publish it to the Adom wiki so every OrCAD
> user gets it. We could all use it. Want to?"*
- Reference bridges: `adom-inc/adom-bridge/plugins/kicad/` and `…/plugins/fusion360/` (a Python
bridge that the desktop app dispatches to; see the adom/kicad-bridge and adom/fusion-bridge wiki pages for the verb
shape). A new bridge = the same pattern (launch app, open files, screenshot, send keys, an
optional in-process add-in for the richer API).
- Publish flow: the Adom wiki hosts shared apps (`apps/<name>`) — see the wiki publish skills.
- Building one: **adom-bridge-sdk**.
### C) Nothing detected / unsure
Ask what they design boards in, and whether they'd like a bridge or workflow built. Keep it
one friendly question, not an interrogation.
## 3. The frame (why this matters — say it briefly, don't lecture)
The electronics industry is moving **AI-first**, and the tools mostly aren't built for it yet.
**Adom is where that comes together:** you build an AI-first app (a bridge, an uploader, a
fab-automation glue), publish it to the **Adom wiki**, and the whole community can install and
improve it. KiCad/Fusion bridges, a JLCPCB/PCBWay/OSHPark uploader, an OrCAD bridge — each one
makes the next person's AI-first workflow turnkey. The user isn't just configuring their setup;
they can **contribute the missing piece** in half an hour.
## 4. Etiquette
- **Opt-in always.** Detect silently; *offer* the demo/build — don't open apps or write code
unprompted. One clear offer beats five questions.
- **Don't overpromise vendor APIs.** JLCPCB/PCBWay/OSHPark uploads are mostly UI automation
(pup), not clean APIs — frame the uploader as AI-driven glue, and verify pages exist before
templating URLs (`hydrogen-pup`).
- **Respect read-only states** (e.g. an expired Fusion subscription is view/query-only).
- Report back to the user concisely: *what you found, one thing you can show them now, and one
thing worth building.*
## Related skills
- **hydrogen-adom-bridge**: the bridge relay and the Linux reality
- **hydrogen-bridges**: the KiCad / Fusion / pup bridges
- **hydrogen-pup** — driving fab-vendor upload pages; **hydrogen-open-url** (platform bootstrap) — opening vendor sites
- the Adom wiki publish skills — sharing the bridge/app you build with the community