Overview Files Skills Packages Releases Dependencies Issues Breadcrumbs Pull Requests Activity

Install

Adom Desktop bridge for Altium Designer — add LCSC/JLCPCB-tagged parts to file-based libraries (symbols, footprints with 3D, value-only display) by driving Altium via DelphiScript.

adom-wiki pkg install barrett-land/adom-desktop-altium-bridge

Latest: v0.0.36, published 2026-06-30

Download for your machine · v0.0.33 ?

Release 0.0.33

altium-bridge-manifest.json315 B · 5 downloads altium-bridge-v0.0.33.zipwindows · 21 KB · 3 downloads

Contents

Install
Usage
Develop
Optional package.json fields

adom-desktop-altium-bridge

Adom Desktop bridge for Altium Designer — add LCSC-tagged parts to file-based libraries

Screenshot of adom-desktop-altium-bridge

Replace docs/screenshot.png with a real screenshot before publishing. The pre-publish lint nags about apps/skills without inline images because visual context dramatically improves discoverability.

Install

adom-wiki pkg install adom-desktop-altium-bridge

Usage

adom-desktop-altium-bridge

Develop

cd adom-desktop-altium-bridge
adom-wiki pkg pack       # build a tarball locally to inspect
adom-wiki pkg publish    # publish to the registry (runs lint first)

Edit-in-place once published:

adom-wiki pkg link adom-desktop-altium-bridge     # point the installed slug at this checkout
# edit files; changes propagate immediately via the symlink convention
adom-wiki pkg unlink adom-desktop-altium-bridge   # restore the published install

Optional package.json fields

Add these to package.json when relevant:

Field	Purpose
`devDependencies`	Tools needed for editing this package, not running it (e.g. style guides). Installed only with `adom-wiki pkg install --dev`.
`peerDependencies`	Packages this one augments. Auto-installed if missing; shared with the rest of the tree.
`optionalDependencies`	Nice-to-have integrations; install failures are non-fatal.
`engines.adom-wiki`	Minimum CLI version, e.g. `">=2.8.0"`.
`scope`	`"runtime"` / `"dev"` / `"either"`: hint to consumers about how this package is meant to be used.
`visibility`	`"public"` (default) or `"private"`. Set on first publish only.
`scripts.prepublish`	Runs in the project dir before tarball build. Use for code-gen / asset builds.
`scripts.postinstall`	Runs in the module dir after install.sh succeeds. Use for setup.