Adom Wiki Skill Pack

@@ -1,6 +1,6 @@ {   "slug": "adom-wiki-skillpack",-  "version": "0.3.0",+  "version": "0.3.1",   "type": "skill",   "description": "The Adom Wiki Skill Pack — one main skill plus 14 focused sub-skills that teach the AI to publish to wiki.adom.inc without breaking pages, name the wiki repo archetypes (Page, Skillpack, Family), and publish rich component pages (chips, molecules, boards). The wiki is six tools in one: git, adompkg, releases, discussions, pull requests, and discovery. One adompkg install drops the whole set onto your container.",   "discovery_triggers": [

@@ -213,6 +213,62 @@ previews inline + deep-link the interactive tools** (SymView `:8781`, FpView  --- +# The "Open in…" toolbar++A chip page should let the user *act* on the part — open it in a tool or on their+desktop — not just read it. The targets and how each is reached:++| Target | Reached by | Auto-open from a web page today? |+|---|---|---|+| 3D / Symbol / Footprint **viewer** | the wiki's own `/viewer/{3d,symbol,footprint}/component/<slug>` routes | ✅ yes — plain links, work in any browser/Hydrogen/pup |+| Download CAD (`.kicad_sym/.kicad_mod/.step/.glb/.IntLib/.lbr`) | `/blob/component/<slug>/<file>` | ✅ yes — `<a download>` links |+| Buy (Mouser / DigiKey) | `distributor_links` URLs | ✅ yes |+| **adom-symbol / adom-footprint / adom-lbr / adom-step / adom-chipfit / adom-chipsmith / chip-fetcher** (container tools) | container CLI / services (`:8781`, `:8782`, `:8851`, `:8894`) | ❌ no page→container bridge — **paste-to-Claude prompt** |+| **KiCad / Fusion 360 on the desktop** | `adom-desktop kicad_open_* / fusion_open_*` | ❌ no page→desktop bridge — **paste-to-Claude prompt** |+| **Altium / OrCAD on the desktop** | — | ❌ no adom-desktop verb exists — download the file + open manually |+| Send library → Downloads + open folder | `adom-desktop send_files` + reveal-folder | ❌ paste-to-Claude prompt |++### Why most targets use a paste-to-Claude prompt today++A wiki page is server-rendered HTML and **cannot run JS** (the README sanitizes+`<script>`), and **there is no page→adom-desktop bridge** (no injected+`window.adomDesktop`, no `adom://` scheme, no local endpoint the page may call).+So the only universal trigger is: render a one-line **Claude Code prompt** the user+pastes ("open the <MPN> symbol in adom-symbol"). It works from every context. Ship+the direct links as real buttons; ship the rest as copyable prompts.++### Three contexts (and why they'd differ if a bridge existed)++- **Hydrogen webview** — the page is inside HD; the *richest* potential target+  (HD could open adom-symbol in its own webview tab). Detect via an HD-injected+  global (doesn't exist yet).+- **Native browser** — laptop; best target is "open in KiCad/Fusion on the+  desktop" via adom-desktop, or download.+- **pup** — a controlled Chrome; same as native but adom-desktop is already attached.++Runtime detection of which context the page is in **does not exist yet** (no+injected marker), so today the prompt is context-agnostic and Claude figures out+the right path. The clean long-term home for this is a **native wiki "Open in…"+toolbar for component pages** (server-rendered, like the viewer sections), wired to+an adom-desktop page-bridge — not hand-rolled JS per README.++### 📋 TODO — make the toolbar one-click (for the adom-desktop + wiki teams)++- **A page→desktop bridge**: an injected `window.adomDesktop` (in HD webview + pup)+  and/or a localhost endpoint / `adom://` scheme a wiki page may call, so a button+  can trigger `kicad_open_*` / `fusion_open_*` / `send_files` directly.+- **Runtime context detection** the page can read (HD webview vs native vs pup).+- **`adom-desktop` capability + endpoint enumeration** surfaced to the page, incl.+  **which desktop apps are installed** (KiCad/Fusion/Altium present?), so the+  toolbar only shows viable targets and routes to the best one (e.g. HD instance+  running → open adom-symbol in HD's webview).+- **A reveal-folder verb** so "send to Downloads + open the folder" is one click.+- **Altium / OrCAD desktop open verbs** in adom-desktop (none today).+- **A native wiki "Open in…" toolbar** component for `type:component` pages+  (server-rendered), so every chip page gets it without per-page HTML.++---+ # Molecule component pages  A molecule is published via **adom-molecule** (`create --source kicad|fusion …`),