Publish a Hardware Component to the Adom Wiki
Public Made by Adomby adom
The one-stop-shop for publishing a hardware component (or molecule/board) to the Adom Wiki. The whole lifecycle: page anatomy, the clone→edit→preview→push loop and its hard rules, making a great hero image (Hero Component Studio — 16:10, overlay-safe, datasheet-backed), the animated 3D composite, the interactive 3D viewer, ct thumbnails, the datasheet-accuracy audit, and every wiki push/pull gotcha we've hit. Now includes the worked Path B (board) pipeline: STEP-to-GLB, refdes tagging, layer de-
Skills
The skills this repo ships, by tier, each with a quick health read. Install the user skills with:
adom-wiki skills install adom/adom-hardware-component-publishThe one-stop-shop for publishing a HARDWARE COMPONENT (or molecule/board) to the Adom Wiki — everything you need in one place. Covers the whole lifecycle: what a component page is made of, the clone→edit→preview→push loop and its hard rules, how to make a great hero image (Hero Component Studio: a lit part on a procedural PCB or a molecule on a shadow ground, 16:10, overlay-safe, datasheet-backed), the animated 3D composite model, the interactive 3D viewer, ct thumbnails (symbol + footprint + 3D icons), the datasheet-accuracy audit, and every wiki push/pull gotcha we have hit. Use whenever someone wants to publish, update, or improve a component/molecule/board page on wiki.adom.inc. Trigger words: publish component, publish hardware, publish to wiki, component page, molecule page, board page, wiki page, hero image, component thumbnail, card art, 3d composite, insertion.glb, interactive viewer, ct thumbnails, datasheet audit, wiki push, wiki clone, page hero, set hero, land pattern, footprint viewer. PRIVATE — Adom only.
No dev skills in this repo.
How to build, debug, and test this app. Source-only (dev-skills/), never shipped in the tarball.
No publish skills in this repo.
The app-to-wiki publish glue. Source-only (publish-skills/), never shipped in the tarball.
Health: the size chip is green when right-sized, yellow when getting long, red when the model likely skims it. A green check is a passed preamble/structure signal; an amber mark is a gentle nudge, not a hard failure.