kicad-bridge-macos

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

@@ -0,0 +1,26 @@+# KiCad Bridge for macOS++**Your AI drives KiCad on your Mac, in the background.** It opens boards, schematics, symbols and footprints, shows and turns the 3D Viewer, runs DRC and ERC, exports fabrication files, places and routes on a live board, and installs libraries and parts, while KiCad stays behind your work and never takes your focus.++This is the macOS edition of the KiCad bridge: one signed native program for Apple Silicon Macs that [Adom Bridge](https://wiki.adom.inc/adom/adom-bridge) installs and keeps up to date. The Windows edition is [adom/kicad-bridge](https://wiki.adom.inc/adom/kicad-bridge); the two share their verb set and are released separately.++## Install++There is nothing to install by hand. Adom Bridge for macOS (bundled with Hydrogen) downloads the bridge the first time an AI asks for KiCad and updates it on its own. If KiCad itself is missing, the AI can install the official build for you (`kicad_upgrade`).++## What it needs++- KiCad 9 or 10 (KiCad 10 recommended).+- Adom Bridge's Accessibility, Screen Recording and Accessibility Access (Events) grants. Hydrogen's first run sets them up.++## How it stays out of your way++KiCad windows open behind your work. When the AI needs you to see something, it says why first, then brings the window forward. Menus that macOS only lets the frontmost app use are reached through KiCad's own actions and a small helper plugin inside KiCad, so nothing jumps in front of you.++## For AIs++Install the skill: `adom-wiki pkg install adom/kicad-bridge-macos`. Then `adom-bridge kicad_describe '{}'` lists every verb.++## License++MIT.

@@ -0,0 +1,42 @@+---+name: kicad-bridge-macos+public: true+description: "Drive KiCad on the user's Mac from this container through Adom Bridge: open boards, schematics, symbols and footprints, show the 3D Viewer and turn it, run DRC/ERC, export fab outputs, route and place on a live board, install libraries and parts, take screenshots. Everything runs in the background: KiCad never takes the user's focus. Trigger words: kicad, open my board, open schematic, symbol editor, footprint editor, 3D viewer, run drc, gerbers, kicad on mac, kicad bridge."+---++# KiCad on the user's Mac++Every verb goes through the Adom Bridge CLI and runs on the user's Mac:++```bash+adom-bridge kicad_<verb> '<json args>'+```++- `kicad_describe '{}'` lists every verb with its arguments. `kicad_readiness '{}'` says whether KiCad is installed and ready.+- KiCad missing (`errorCode: host_app_not_installed`): offer to install it, then run `kicad_upgrade '{}'` (the official universal DMG into /Applications/KiCad).+- Branch on `errorCode`, not on the prose, and pass the `_hint` on to the user.++## Background by default++KiCad windows open behind the user's work and never take focus. To show the user something on purpose, pass `foreground: true` with a `foregroundReason`; the bridge captions the reason first. Use `kicad_screenshot_all` (then pull the files) to see what KiCad shows.++## Permissions++The bridge works through Adom Bridge's macOS grants: Accessibility (windows and menus), Screen Recording (screenshots) and, for keys and clicks into KiCad, Accessibility Access (Events). A verb that needs a missing grant returns `errorCode: permission_required` and names the System Settings pane.++## Things that differ from Windows++- macOS has one menu bar per app, and a KiCad in the background keeps the last active window's menus up. The bridge opens editors and the board's 3D Viewer through KiCad's own actions instead, and fires the 3D Viewer's camera commands (`kicad_3d_view`, `kicad_animate_view`) through a small plugin inside KiCad that the bridge installs and keeps current.+- `kicad_enable_software_opengl` has nothing to do on a Mac and says so.++## Common jobs++| Job | Verb |+|---|---|+| Open a board / schematic | `kicad_open_board {filePath}`, `kicad_open_schematic {filePath}` |+| Show a symbol / footprint | `kicad_show_symbol {symbolName, libraryName}`, `kicad_show_footprint {footprintName, libraryName}` |+| 3D | `kicad_open_3d_viewer {editor:"pcb"}`, `kicad_3d_view {action}`, `kicad_animate_view {steps}`, `kicad_render_board_3d {filePath}` |+| Checks and outputs | `kicad_run_drc`, `kicad_run_erc`, `kicad_export_gerber`, `kicad_export_step`, `kicad_export_bom` |+| Live board edits (IPC API) | `kicad_routing_state`, `kicad_route_net`, `kicad_place_footprint`, `kicad_zoom_to` |+| Libraries and parts | `kicad_install_library`, `kicad_install_symbol`, `kicad_install_footprint` |+| What is open | `kicad_open_editors`, `kicad_document_info`, `kicad_window_info` |

⋯ 1 unchanged line ⋯

@@ -0,0 +1,15 @@+#!/usr/bin/env bash+# Install the KiCad Bridge for macOS user skill. The skill directory name must equal SKILL.md's `name:`+# (kicad-bridge-macos). The bridge RUNTIME is not here: Adom Bridge installs and updates it from this+# page's Releases. The Adom Bridge CLI + core skills arrive through this pkg's dependencies.+set -e+PKG_DIR="$(cd "$(dirname "$0")" && pwd)"+deploy_into() {+  mkdir -p "$1/kicad-bridge-macos"+  cp "$PKG_DIR/SKILL.md" "$1/kicad-bridge-macos/SKILL.md"+  echo "  -> $1/kicad-bridge-macos"+}+echo "Installing KiCad Bridge for macOS skill:"+deploy_into "$HOME/.claude/skills"+[ -d "$HOME/.codex" ] && deploy_into "$HOME/.codex/skills"+echo "Done. The skill drives KiCad on the Mac through the adom-bridge CLI; Adom Bridge installs the bridge on first use."

@@ -0,0 +1,8 @@+#!/usr/bin/env bash+# Remove the KiCad Bridge for macOS skill.+set -e+remove_from() { rm -rf "$1/kicad-bridge-macos"; echo "  <- $1"; }+echo "Removing KiCad Bridge for macOS skill:"+remove_from "$HOME/.claude/skills"+[ -d "$HOME/.codex" ] && remove_from "$HOME/.codex/skills"+echo "Done."