name: cloud-libraries description: Use Adom Cloud Libraries, the wiki's component carts that export as native KiCad, Fusion and Altium libraries. Build a library from wiki parts, export it into the user's EDA tool through Adom Bridge (or as a zip), drive the same thing from an AI thread with adom-wiki library, troubleshoot an export, and report Cloud Library problems on the adom/cloud-libraries Issues tab. Triggers - cloud library, make me a library, add parts to my library, export library to kicad, put these parts in fusion, altium library from the wiki, library export failed, report a cloud library bug.

Cloud Libraries

A Cloud Library is a list of wiki parts that exports as a real library for KiCad, Fusion or Altium: symbols, footprints and 3D models, with the part number engraved on each 3D model where the wiki has one. Libraries live in the user's wiki account at https://wiki.adom.inc/libraries and are private to that account.

The export is fixed code, not AI. The wiki assembles the library the same way every time, and Adom Bridge runs fixed steps on the PC to add it to the EDA tool.

Build a library

On the web: every part page has an Add to Cloud Library button. It adds to the active library (one at a time, shown as a chip in the header). The libraries page creates, renames, duplicates and switches libraries.

From an AI thread (adom-wiki CLI, signed in as the user):

adom-wiki library create "Guitar Amp" --description "Parts for a 45 W amp"
adom-wiki library add "Guitar Amp" adom/tl072cp adom/lm7815ct adom/gbu806g
adom-wiki library show "Guitar Amp"
adom-wiki library availability "Guitar Amp"

A library reference is its lib_ id or its exact name.
Parts can be owner/slug, a bare unambiguous slug, or the page's permanent pg_ id. Adding is idempotent.
A board page can go in a library; its parts are included at export.
availability lists each part against KiCad, Fusion and Altium and says why a part cannot go to a tool. Run it before promising the user an export.
library activate <ref> makes a library the one-click add target on the web.
A part the wiki does not have yet can be requested with adom-wiki part request <MPN> (or --bom <file> for a whole BOM). Ask the user first: some people prefer to request through the website.

Export into an EDA tool

On the web, open the library and use Export into KiCad / Fusion / Altium. With Adom Bridge running on the PC (the pill at the top of the library page turns green), the export goes straight into the tool. Without it, the same export downloads as a zip.

Tool	What the user sees when it is done
KiCad	The library is added to the symbol and footprint tables, and the Symbol Editor opens in the background with it loaded. A picture of it comes back to the page.
Fusion	The library opens in Fusion Electronics with 3D bound to each part. Exporting again reuses parts that did not change.
Altium	The library is added and opens on the SCH Library panel. A closed Altium is started first, which takes about a minute.

From an AI thread:

adom-wiki library install "Guitar Amp"                     # KiCad, through Adom Bridge
adom-wiki library export "Guitar Amp" --format fusion      # downloads the .lbr bundle
adom-wiki library export "Guitar Amp" --format altium      # downloads the .SchLib/.PcbLib zip

library install handles KiCad end to end (pass --target <machine> when more than one PC is connected). For Fusion and Altium, export the bundle, send it to the PC, and hand it to that tool's bridge: fusion_open_lbr then fusion_build_library_3d for the 3D models, or altium_install_library_bundle. The fusion-bridge and altium-bridge skills have the details. Keep the user's windows in the background; never bring an EDA window to the front unless they ask.

When an export goes wrong

The pill says Adom Bridge is not running or blocked. Start Adom Bridge on the PC. "Blocked by your browser" means the browser's local network permission was denied for wiki.adom.inc; allow it in the site settings.
KiCad was already open. KiCad reads its library tables at startup, so the new library appears after KiCad restarts. The page says so.
The export finished but no picture came back. The library is still added. The picture arrives later if the tool was slow, or not at all if the bridge restarted (for example, for an update) during the export.
Altium took about a minute. Altium was closed and had to start. The page says when this is happening.
A part is missing from one tool. Check availability: it names the part and the reason.

Report a problem

Cloud Library problems go on the Issues tab of this page: https://wiki.adom.inc/adom/cloud-libraries/issues

adom-wiki issue create adom/cloud-libraries --title "<what went wrong>" --body-file report.md

Include:

the tool (KiCad, Fusion or Altium) and roughly when it happened
what the page or CLI said, word for word
the library's lib_ id (only the owner can open it, so it is safe to share)
the Adom Bridge version on the PC, if the export went through the bridge

Do not attach design files or the exported library to a public issue. A problem with one part's symbol, footprint or 3D model belongs on that part's own page instead.

---
name: cloud-libraries
description: Use Adom Cloud Libraries, the wiki's component carts that export as native KiCad, Fusion and Altium libraries. Build a library from wiki parts, export it into the user's EDA tool through Adom Bridge (or as a zip), drive the same thing from an AI thread with adom-wiki library, troubleshoot an export, and report Cloud Library problems on the adom/cloud-libraries Issues tab. Triggers - cloud library, make me a library, add parts to my library, export library to kicad, put these parts in fusion, altium library from the wiki, library export failed, report a cloud library bug.
---

# Cloud Libraries

A Cloud Library is a list of wiki parts that exports as a real library for KiCad,
Fusion or Altium: symbols, footprints and 3D models, with the part number engraved
on each 3D model where the wiki has one. Libraries live in the user's wiki account
at https://wiki.adom.inc/libraries and are private to that account.

The export is fixed code, not AI. The wiki assembles the library the same way every
time, and Adom Bridge runs fixed steps on the PC to add it to the EDA tool.

## Build a library

On the web: every part page has an **Add to Cloud Library** button. It adds to the
**active** library (one at a time, shown as a chip in the header). The libraries page
creates, renames, duplicates and switches libraries.

From an AI thread (`adom-wiki` CLI, signed in as the user):

```
adom-wiki library create "Guitar Amp" --description "Parts for a 45 W amp"
adom-wiki library add "Guitar Amp" adom/tl072cp adom/lm7815ct adom/gbu806g
adom-wiki library show "Guitar Amp"
adom-wiki library availability "Guitar Amp"
```

- A library reference is its `lib_` id or its exact name.
- Parts can be `owner/slug`, a bare unambiguous slug, or the page's permanent
  `pg_` id. Adding is idempotent.
- A board page can go in a library; its parts are included at export.
- `availability` lists each part against KiCad, Fusion and Altium and says why a
  part cannot go to a tool. Run it before promising the user an export.
- `library activate <ref>` makes a library the one-click add target on the web.
- A part the wiki does not have yet can be requested with
  `adom-wiki part request <MPN>` (or `--bom <file>` for a whole BOM). Ask the user
  first: some people prefer to request through the website.

## Export into an EDA tool

On the web, open the library and use **Export into KiCad / Fusion / Altium**. With
Adom Bridge running on the PC (the pill at the top of the library page turns green),
the export goes straight into the tool. Without it, the same export downloads as a
zip.

| Tool | What the user sees when it is done |
|---|---|
| KiCad | The library is added to the symbol and footprint tables, and the Symbol Editor opens in the background with it loaded. A picture of it comes back to the page. |
| Fusion | The library opens in Fusion Electronics with 3D bound to each part. Exporting again reuses parts that did not change. |
| Altium | The library is added and opens on the SCH Library panel. A closed Altium is started first, which takes about a minute. |

From an AI thread:

```
adom-wiki library install "Guitar Amp"                     # KiCad, through Adom Bridge
adom-wiki library export "Guitar Amp" --format fusion      # downloads the .lbr bundle
adom-wiki library export "Guitar Amp" --format altium      # downloads the .SchLib/.PcbLib zip
```

`library install` handles KiCad end to end (pass `--target <machine>` when more than
one PC is connected). For Fusion and Altium, export the bundle, send it to the PC, and
hand it to that tool's bridge: `fusion_open_lbr` then `fusion_build_library_3d` for
the 3D models, or `altium_install_library_bundle`.
The `fusion-bridge` and `altium-bridge` skills have the details. Keep the user's
windows in the background; never bring an EDA window to the front unless they ask.

## When an export goes wrong

- **The pill says Adom Bridge is not running or blocked.** Start Adom Bridge on the
  PC. "Blocked by your browser" means the browser's local network permission was
  denied for wiki.adom.inc; allow it in the site settings.
- **KiCad was already open.** KiCad reads its library tables at startup, so the new
  library appears after KiCad restarts. The page says so.
- **The export finished but no picture came back.** The library is still added. The
  picture arrives later if the tool was slow, or not at all if the bridge restarted
  (for example, for an update) during the export.
- **Altium took about a minute.** Altium was closed and had to start. The page says
  when this is happening.
- **A part is missing from one tool.** Check `availability`: it names the part and
  the reason.

## Report a problem

Cloud Library problems go on the Issues tab of this page:
https://wiki.adom.inc/adom/cloud-libraries/issues

```
adom-wiki issue create adom/cloud-libraries --title "<what went wrong>" --body-file report.md
```

Include:
- the tool (KiCad, Fusion or Altium) and roughly when it happened
- what the page or CLI said, word for word
- the library's `lib_` id (only the owner can open it, so it is safe to share)
- the Adom Bridge version on the PC, if the export went through the bridge

Do not attach design files or the exported library to a public issue. A problem with
one part's symbol, footprint or 3D model belongs on that part's own page instead.