Adom Wiki

@@ -305,12 +305,21 @@ 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 LOOK IS GATED ONCE, BY A HUMAN (hero-studio 0.19): pose one+representative part in Hero Studio, let the human walk the wizard and+Generate, then `hero-studio style save <name>`. After that,+`hero-studio batch --style <name> --parts parts.json --pace 5 --human <who>+--quote "<their words>"` generates every part's hero in that exact style+locally (per-part title + render), each PNG's provenance carrying the gate+it inherited. Ugly one-off heroes are how hardware pages rot; the gated+style is how 300 pages come out looking like one family.+ 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+# drop assets: model.step (REQUIRED), docs/hero.png (from the style batch above), <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>@@ -320,9 +329,10 @@ adom-wiki page edit <org>/<slug> --source [email protected]   # provenance: the Source r 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+shots from the STEP), chipsmith (validation + sign-off bake). Hero generation is local (no rate limits). PUBLISHING is the paced part:+run publishes serially or 2-3 at a time with a few seconds between; a 429+answer carries its own back-off hint, so slow down when one appears rather+than pre-tuning. 300 parts at ~5s spacing is under half an hour. Every failure names its fix in the hint; trust the hints over memory.  ## Decision table

@@ -1,7 +1,7 @@ {   "slug": "wiki",   "title": "Adom Wiki",-  "version": "3.9.4",+  "version": "3.9.5",   "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.4",+  "version": "3.9.5",   "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.",