Adom Library
Public Made by Adomby adom
adom-lbr — the EDA library translator. Bring a component in from any supported EDA tool and convert it to any other (KiCad ⇄ Altium ⇄ EAGLE/Fusion) through one canonical adom-lbr JSON — symbol + footp
adom-lbr roadmap / standing directives
Standing directive — match adom-symbol's 3D chip outline on EVERY export
When a thread asks adom-lbr to make a library and the adom-symbol input carries a 3D chip outline, ALWAYS embed that outline on the schematic symbol, placed as close to what adom-symbol renders as possible — for every export endpoint, not just Fusion. (Owner's directive, 2026-06-28.)
adom-symbol does the hard work of drawing the chip's vector outline and sizing it to the symbol body + pin layout. adom-lbr should stay faithful to that, never invent its own look.
Status by endpoint
| Endpoint | Path | Outline embedded? |
|---|---|---|
| Fusion 360 | EAGLE .lbr (generate --symbol-art) |
✅ done — wires on layer 94 |
| Altium | imports the same .lbr |
✅ done (free — same file) |
| OrCAD | imports the same .lbr |
✅ done (free — same file) |
| KiCad | import / deliver kicad → .kicad_sym |
⬜ TODO — carry the outline into the .kicad_sym (gfx polylines). NB adom-symbol is KiCad-native, so this only matters for the .lbr → .kicad_sym round-trip. |
Future native exporters (Altium .SchLib, OrCAD .olb, …) |
not built yet | ⬜ TODO when those land — embed the outline there too. |
So one .lbr already covers the three EAGLE-family tools. The open work is the
KiCad conversion path and any future native exporters.
How the matching works today (and how to make it exact)
generate --symbol-art <mpn>-3d-outline-*.svgtranscribes adom-symbol's flattened outline polylines → EAGLE<wire>s, centred and scaled to ~0.38× of the symbol body's smaller side (tunable with--symbol-art-scale). The 0.38 is reverse-engineered from adom-symbol's own-symbol.svgplacement — it's close, not exact.- To make it pixel-exact, adom-symbol should emit either (a) the outline
already in symbol mm-space (same viewBox as
-symbol.svg), or (b) a sidecar with the{center, scale}transform + the canonical default variant. See the contract proposed to the adom-symbol thread (2026-06-28). When that lands, switch adom-lbr to a 1:1 transcription and drop the 0.38 guess. - Detailed outlines are heavy (
-blueprint≈ 3000<wire>s, ~300 KB). adom-lbr warns and suggests a lighter variant; ideally adom-symbol emits a decimated "lite" outline for embedding.
# adom-lbr roadmap / standing directives
## Standing directive — match adom-symbol's 3D chip outline on EVERY export
**When a thread asks adom-lbr to make a library and the adom-symbol input carries
a 3D chip outline, ALWAYS embed that outline on the schematic symbol, placed as
close to what adom-symbol renders as possible — for every export endpoint, not
just Fusion.** (Owner's directive, 2026-06-28.)
adom-symbol does the hard work of drawing the chip's vector outline and sizing it
to the symbol body + pin layout. adom-lbr should stay faithful to that, never
invent its own look.
### Status by endpoint
| Endpoint | Path | Outline embedded? |
|---|---|---|
| **Fusion 360** | EAGLE `.lbr` (`generate --symbol-art`) | ✅ done — wires on layer 94 |
| **Altium** | imports the **same** `.lbr` | ✅ done (free — same file) |
| **OrCAD** | imports the **same** `.lbr` | ✅ done (free — same file) |
| **KiCad** | `import` / `deliver kicad` → `.kicad_sym` | ⬜ **TODO** — carry the outline into the `.kicad_sym` (gfx polylines). NB adom-symbol is KiCad-native, so this only matters for the `.lbr → .kicad_sym` round-trip. |
| Future native exporters (Altium `.SchLib`, OrCAD `.olb`, …) | not built yet | ⬜ **TODO** when those land — embed the outline there too. |
So one `.lbr` already covers the three EAGLE-family tools. The open work is the
**KiCad conversion path** and any **future native exporters**.
### How the matching works today (and how to make it exact)
- `generate --symbol-art <mpn>-3d-outline-*.svg` transcribes adom-symbol's
flattened outline polylines → EAGLE `<wire>`s, centred and scaled to ~0.38× of
the symbol body's smaller side (tunable with `--symbol-art-scale`). The 0.38 is
reverse-engineered from adom-symbol's own `-symbol.svg` placement — it's close,
not exact.
- **To make it pixel-exact**, adom-symbol should emit either (a) the outline
already in symbol mm-space (same viewBox as `-symbol.svg`), or (b) a sidecar
with the `{center, scale}` transform + the canonical default variant. See the
contract proposed to the adom-symbol thread (2026-06-28). When that lands,
switch adom-lbr to a 1:1 transcription and drop the 0.38 guess.
- Detailed outlines are heavy (`-blueprint` ≈ 3000 `<wire>`s, ~300 KB). adom-lbr
warns and suggests a lighter variant; ideally adom-symbol emits a decimated
"lite" outline for embedding.