Adom Bridge

Use when the user wants to send files to their desktop, control KiCad or Fusion 360, send desktop notifications, or troubleshoot the desktop connection. Provides CLI tools for bridging the Docker container to the user's local machine.

The Windows translation layer for Adom Anywhere. The Adom ecosystem skills that Adom Bridge delivers to a local agent (Claude Desktop, Codex, Claude Code on this PC) were written for Adom LINUX CONTAINERS; this skill is the authoritative table of what changes on a Windows PC that has no container. Read when a delivered skill carries the ADOM ANYWHERE NOTE banner, when an example says adom-cli or bash or ~/project and you are on Windows, when you need to run adom-wiki on Windows with auth, or when a wiki package install fails because its payload is a Linux binary. Triggers include adom anywhere windows, adom-cli not found, container-only skill, wiki cli on windows, and ADOM ANYWHERE NOTE.

Adom Anywhere, the full map of what a LOCAL third-party agent (Claude Desktop, Codex, Claude Code on Windows) can do with the Adom ecosystem from this PC, and where the boundary is. Covers what the Adom Bridge installer already gave you (adom-bridge-cli.exe and adom-wiki.exe on PATH, the auto-linked skill set), driving the PC and pup locally, authoring and managing wiki pages with adom-wiki, the ecosystem skills ab delivers daily (adom core, adom-wiki-cli), and the one hard boundary; running Linux binaries published on the wiki needs an Adom container, which is what Hydrogen provides. Use when a user on Claude Desktop or Codex asks what they can do with Adom, how to use the wiki from their PC, or why a wiki package will not run locally.

No description in this skill's frontmatter.

No description in this skill's frontmatter.

No description in this skill's frontmatter.

Use when working with the adom-bridge CLI itself - how to run desktop verbs, discover commands (adom-bridge commands, help topics), address targets with --target, start the serve relay with --supervise, read the status/durationMs/timeoutSeconds response shape, stream long ops with watch, or sweep the screenshot cache with janitor.

No description in this skill's frontmatter.

No description in this skill's frontmatter.

Reaches the user's Windows/Mac laptop desktop from this container via adom-bridge — run commands & scripts on the laptop, list/kill processes, restart apps (e.g. Explorer), desktop/app-window screenshots, send/pull files, notifications, list/focus/flash windows, RDP tunnels. Also launches and drives KiCad (schematics/boards/symbols/footprints, DRC, library install, 3D viewer, automation) and Fusion 360 (.f3d/.f3z, import/export STEP/GLB/.lbr, BOM/parameters, Fusion API). Also covers Puppeteer/pup real-Chrome automation (pup_screenshot, pup_eval, pup_navigate, multi-session profiles, ralph-loop), WSL distro control + golden-image bakes (wsl_exec, wsl_exec_async, wsl_import/export/unregister), the relay server (adom-bridge serve), and connection setup. Trigger words: run command on laptop, run on my pc, restart explorer, restart a program, kill a process, list processes, taskkill, screenshot laptop/desktop/windows/fusion/kicad, list windows, focus window, send file to laptop, pull file from laptop, desktop notification, launch KiCad, open in KiCad, run DRC, launch Fusion, import/export STEP, export GLB/lbr, Fusion API, pup, puppeteer, real Chrome, browser automation, flash taskbar, open URL on desktop, RDP, tunnel, WSL, golden image, adom-bridge, bridge to my pc, windows app, KiCad bridge, Fusion bridge.

No description in this skill's frontmatter.

Install and manage Windows fonts on the user's machine through adom-bridge's font verbs — list installed families, install a single .ttf/.otf per-user (no admin), uninstall one, or idempotently ensure the Adom brand fonts (Satoshi, JetBrains Mono, Familjen Grotesk) are installed so chat/prose renders in Satoshi instead of falling back to Segoe UI. Use when a font needs to be installed on the PC, when brand fonts are missing, when Hydrogen's setup needs font_ensure_brand, or when the user asks to add/remove a Windows font. Trigger words: install font, font_ensure_brand, font_install, font_list, font_uninstall, Satoshi, JetBrains Mono, Familjen Grotesk, brand fonts, add a font to Windows, missing font, per-user font, ensure brand fonts.

No description in this skill's frontmatter.

No description in this skill's frontmatter.

No description in this skill's frontmatter.

No description in this skill's frontmatter.

No description in this skill's frontmatter.

No description in this skill's frontmatter.

No description in this skill's frontmatter.

How Adom Bridge lives quietly on the machine. Covers the system tray and close-to-tray behavior (the X button hides the window, ab keeps serving), the low-memory hidden-window mode (WebView2 suspension while hidden), launch on boot (default ON, Startup-shortcut self-heal), and the taskbar icon states (muted "Adom Bridge" standalone tile vs vivid "Adom Bridge Hydrogen Embedded" tile, the AUMID flip). Use when a user or AI asks why ab is still running after closing the window, why memory is low while hidden, how to tell standalone from embedded mode from the taskbar alone, how to enable or disable launch on boot, why the tray icon is missing, or what the window title markers mean.

No description in this skill's frontmatter.

Managed Node and Python runtimes for Adom Bridge bridges. Use this skill when a node or python bridge fails to spawn, when you need to check runtime status with the runtimes verb, when a bridge needs Node.js or Python and the box may not have one, when npm dependencies for a source-only node bridge are missing, or when you want to understand the no-UAC portable node/python install, the prewarm on first launch, the Runtimes panel in the GUI, or the loopback-only bind rule for bridge processes.

AUDIT and maintain a shipped bridge: the self-audit checklist to run when asked to 'audit against the SDK', how to stay current with SDK changes on your own, the verb-contract quick reference, how to get bugs reported in the OUTPUT rather than buried in a skill file, and how to file issues against Adom Bridge or the repos you depend on. Use for a periodic health check of your bridge or when an SDK-change notice lands on your wiki discussion.

Call Adom Bridge BACK from inside your bridge: the loopback direct API gives you the FULL ab verb set (screenshots, files, windows, notifications, other bridges), how to forward caller provenance so the user sees WHICH AI thread asked (X-Adom-Caller-* headers and the delegation chain), and how to brand a window you borrowed (window identity, taskbar tile, jump list, overlay badge). Use when your bridge needs an ab verb, when the Activity Log or an approval prompt misattributes your calls, or when a window you drive presents as the wrong app.

No description in this skill's frontmatter.

No description in this skill's frontmatter.

The RUNTIME contract for a bridge: Adom Bridge provisions Node/Python for you and you MUST bind loopback (ADOM_BIND_HOST) so no firewall prompt appears; plus prewarm, the cold-start tiers, host-app detection and the bridge_readiness probe, the health endpoint and status- chip contract (led/summary/tooltip), the lifecycle verbs users drive, and the logging split (ab owns the file, you own the volume). Use when your bridge fails to spawn, shows the wrong LED, is slow on first call, or needs a runtime it cannot assume exists.

No description in this skill's frontmatter.

The core thesis of Adom Bridge: WHY it exists and what the whole system is for. Read this to understand the high-level goal before diving into any verb or feature skill, or when a user asks what Adom Bridge is, why they would want it, what problem it solves, whether it is only for Adom/Hydrogen users, or how it is safe to let an AI control a whole computer. Trigger words: what is adom desktop, why adom desktop, adom desktop goal, adom desktop thesis, value proposition, is it safe, do I need hydrogen, unleash the AI, full machine access, AI on my PC.

No description in this skill's frontmatter.

How to run - and how to BELIEVE - a web-control test of the KiCad/Fusion library verbs across a batch of wiki components. Covers the four-artifact evidence contract every library import owes (symbol, footprint, 3D chip, ganged view), the mandatory per-image content check, the five known false-success modes that make a green flag lie (stale window, blank workspace, placeholder 3D, screensaver, name mismatch), and the rule that the run is driven from the web-control page in pup so the UI itself is part of the evidence. Read this BEFORE running any "test N components through web control" request. Trigger words: web control test, library matrix, run the library verb on N parts, evidence images per component, kicad_show_library, fusion_show_library, prove the import worked.

No description in this skill's frontmatter.

The complete reference for Adom Bridge screenshots — every capture verb, the exact JSON response shape (coordMap, shotId, ownedPopupCount, the screenshots[] child-dialog array, windowRect, the multi-monitor display block), and how the CLI automatically stores each shot on disk (the window/ and screen/ buckets, the ISO-stamped filenames, the single-vs-full/safe pair, the .popup-NN grouping, and the <stem>.json sidecar). Read this to drive a GUI app that pops modal dialogs, to capture a backgrounded/occluded window, to understand a multi-monitor grab, or to build a tool (like shotlog) that renders every screenshot shape ab can return. Covers desktop_screenshot_window, desktop_screenshot_screen, kicad_screenshot_all, the coordMap click-what-you-see contract, and the exact on-disk sidecar schema.

Make a window an AI drives present itself as YOUR app on Windows — its taskbar button, Alt-Tab entry, hover name, jump-list (right-click menu), taskbar overlay badge, and pins. Covers the AUMID model, the register+stamp two-halves rule, per-session identities, jump-list tasks + header branding, taskbar progress/overlay, and the icon-format rules (why an icon renders as a generic white document and how to fix it). Use when a bridge borrows a host window (e.g. Chrome for Testing) and it reads as the wrong app.

Read this BEFORE doing any work on adom-bridge from a Claude Code session running directly on the user's Windows machine. Explains how to route everything through the adom-bridge CLI so paths, file operations, and process spawns reach the user's real filesystem instead of getting silently virtualized into Claude Code's Windows AppContainer sandbox. Skipping this causes hour-long debugging spirals where 'open install folder' fails, bridges install to the wrong place, screenshots come back blank, and synthesized clicks don't reach the WebView2.

Use when the user wants to send files to their desktop, control KiCad or Fusion 360, send desktop notifications, or troubleshoot the desktop connection. Provides CLI tools for bridging the Docker container to the user's local machine.

No description in this skill's frontmatter.

No description in this skill's frontmatter.

Launch and drive Fusion 360 on the user's laptop from this container via the adom-desktop CLI. Open .f3d/.f3z designs, open cloud files, close documents, dismiss recovery dialogs, capture Fusion window screenshots, send keyboard shortcuts + click coordinates, run the optional add-in (for STEP/GLB/.lbr import-export and BOM/parameters queries). Trigger words: fusion, Fusion 360, open fusion, launch fusion, open design, f3d, f3z, open .f3d, import STEP, export STEP, export GLB, export lbr, import lbr, Fusion electronics, Fusion PCB, BOM from Fusion, Fusion parameters, Fusion API, dismiss recovery, Fusion screenshot, Fusion window, fusion_click, fusion_send_key, fusion bridge, close fusion.

No description in this skill's frontmatter.

Launch and drive KiCad on the user's laptop (KiCad 7/8/9/10 supported, multi-version side-by-side) from this container via the adom-desktop CLI. Open schematics/boards/symbols/footprints, run DRC, install sym-lib-table / fp-lib-table libraries, show the 3D viewer, capture KiCad window screenshots, send keyboard shortcuts and click coordinates. Trigger words: kicad, open schematic, open board, open pcb, open symbol, open footprint, KiCad symbol editor, KiCad footprint editor, KiCad 3D viewer, run DRC, install KiCad library, sym-lib-table, fp-lib-table, KiCad screenshot, kicad_send_key, kicad_click, kicad_window_info, kicad_screenshot_all, close KiCad, kicad versions, kicad_list_versions, KiCad bridge.

No description in this skill's frontmatter.

No description in this skill's frontmatter.