Adom Wiki

@@ -291,6 +291,40 @@ SKILL.md), per-skill:   create it as `hardware` from the start:   `adom-wiki pkg init <slug> --type hardware --kind <kind>`. +## Publishing many hardware pages fast (bulk)++Hardware pages have NO human gate: no Hero Studio pose, no discovery-fields+requirement (those are app/skill gates). 300 component pages is a loop an AI+runs unattended, bounded only by asset preparation:++Per part, the registry enforces exactly one hard thing: a 3D source+(`.step`/`.stp`/`.glb`) in the tarball. Everything else upgrades the page but+only warns: schematic symbol (`.kicad_sym`), footprint (`.kicad_mod`),+schematic, board, per-pad metadata JSONs. Purchasable parts (`kind:+component`) also want an `mpn` in package.json; molecule/board/project/+equipment identifiers derive from the slug. The hero for hardware is a plain+screenshot/render (no studio stamp): a chip render from the STEP works.++The loop per part:++```bash+adom-wiki pkg init <slug> --type hardware --kind component   # or molecule | board | project | equipment+cd <slug>+# drop assets: model.step (REQUIRED), docs/hero.png (render), <name>.kicad_sym, <name>.kicad_mod+# edit package.json: real description, mpn (purchasable parts), tags+adom-wiki pkg lint          # the full gate list before any network call+adom-wiki pkg publish --org <org>+adom-wiki page edit <org>/<slug> --source [email protected]   # provenance: the Source row (or --source on create)+```++Asset factories that feed this at scale: chip-fetcher (manufacturer CAD+bundles: STEP + KiCad symbol/footprint + datasheet per MPN), adom-symbol /+adom-footprint, step2glb, chip-thumbnailer (rendered chip icons and hero+shots from the STEP), chipsmith (validation + sign-off bake). Run parts in+parallel worktrees or dirs; keep publish concurrency modest (a handful at a+time) and let `pkg lint` catch problems before the network does. Every+failure names its fix in the hint; trust the hints over memory.+ ## Decision table  | You want to | Do this |

@@ -1,7 +1,7 @@ {   "slug": "wiki",   "title": "Adom Wiki",-  "version": "3.9.3",+  "version": "3.9.4",   "type": "skill",   "org": "adom",   "description": "How the Adom Wiki (wiki.adom.inc) works and how to drive it with the adom-wiki CLI: the two storage layers (git page repo vs package registry), hosting source by pushing files (not a tarball), making packages, cutting per-platform releases, and the three-tier skill layout (user skills ship, dev-skills/ and publish-skills/ stay source-only). adom-wiki is the current tool; adompkg is deprecated. Read this first before publishing or installing.",

@@ -1,6 +1,6 @@ {   "slug": "wiki",-  "version": "3.9.3",+  "version": "3.9.4",   "type": "skill",   "org": "adom",   "description": "How the Adom Wiki (wiki.adom.inc) works and how to drive it with the adom-wiki CLI: the two storage layers (git page repo vs package registry), hosting source by pushing files (not a tarball), making packages, cutting per-platform releases, and the three-tier skill layout (user skills ship, dev-skills/ and publish-skills/ stay source-only). adom-wiki is the current tool; adompkg is deprecated. Read this first before publishing or installing.",