74VHC165FT

This page has no EDA files, so nothing downstream can use it

adom/74vhc165ft carries a README, a characterization HTML and page.json - and none of the files a component page needs to be usable. It is the only one of the 140 Adom basic parts in this state; the other 139 are complete.

Found while running a KiCad library matrix over the basic parts. I wanted this part specifically, because it is the only real IC in the set (a TSSOP-16 shift register) and every other candidate is a two-terminal passive. It had to be dropped.

What is here

74VHC165FT.html      23,353 bytes   (characterization page)
README.md               770 bytes
page.json               982 bytes

What a working page carries, for comparison

This is adom/in-s42atg, a healthy page from the same set:

IN-S42ATG.kicad_sym         <- symbol          MISSING here
IN-S42ATG.kicad_mod         <- footprint       MISSING here
IN-S42ATG.step              <- 3D              MISSING here
IN-S42ATG.lbr               <- Fusion/EAGLE    MISSING here
IN-S42ATG.adom-lbr.json     <- hub record      MISSING here
IN-S42ATG.glb, .svg, -symview.html, -fpview.html, -viewer.html

Why it matters

The three that block everything are .kicad_sym, .kicad_mod and .step. Without them:

• KiCad: web control cannot install a symbol or footprint, so the part cannot be placed in a schematic or board at all.
• Fusion: no .lbr and no .step, so no library and no 3D.
• The page itself: the symbol/footprint/3D viewers a component page normally embeds have nothing to render.

The characterization HTML is genuinely nice, which is what makes this easy to miss - the page looks finished. Nothing errors; the part is simply unusable by any tool, and you only find out when you try to place it.

What would fix it

Generate and publish 74VHC165FT.kicad_sym, .kicad_mod and .step. Once those three exist, .lbr and .adom-lbr.json can be generated from them (adom-lbr generate --sym <sym> --fp <fp>; the recipe and its validation gate are in skills/fusion-publishable-lbr on the fusion-bridge page).

A TSSOP-16 is a standard package, so the footprint should be straightforward. The pinout is in the datasheet the characterization page already links.

Worth catching automatically

This is the case for the component linter proposed in adom/adom-bridge#92: a page that renders fine but carries no EDA files reads as complete to a human and is invisible until someone tries to use it. One rule - "a hardware page has .kicad_sym + .kicad_mod + .step" - would have flagged this without anyone running a matrix over 140 parts.