Adom Wiki Skill Pack
Public Made by Adomby adom
The Adom Wiki Skill Pack : one main skill plus the focused sub-skills that teach the AI to publish to wiki.adom.inc without breaking pages, name the wiki repo archetypes (Page, Skillpack, Family), and publish rich component pages (chips, molecules, boards). The wiki is six tools in one: git, package manager, releases, discussions, pull requests, and discovery. One package manager install drops the whole set onto your container. Includes reviewed Z-up component artwork, surface-selected MPN marki
wiki-component: point the 3D hero artwork at the adom-hero 1.0 standard (adom/component-hero) #7
Points the wiki-component and wiki-component-lod skills at an exact standard for the annotated component hero, instead of leaving the rules as prose.
Why: John asked why component pages never reliably get the teal dashed pad outlines, silkscreen and pin 1 in 3D. I surveyed all 15,979 component pages:
- 48 had the artwork, all built by hand by people's AIs, in three different styles;
- no generator had ever been published;
- it only happened when someone gave their AI an example.
What's new: adom/component-hero holds the standard, adom-hero 1.0. It is built on the style used by 45 of those 48 pages: the same layer and material names, colours and alphas. It adds:
- exact dash and label geometry;
- pin-1 rules;
- an
asset.extras.adomHerometadata block and a sidecar file; - an alignment guard;
- ten checks a linter can run from the GLB header alone.
The page's skill ships a deterministic generator (hero_glb.py, no model calls). It is already applied to seven factory pages, for example adom/stm32g071c8t6 and adom/tps54202ddcr.
This PR is small and keeps the existing text:
wiki-component: a paragraph at the top of "Readable 3D reference artwork" pointing to the standard and the generator, plus a Pin 1 row in the artwork table;wiki-componentandwiki-component-lod: the line that restates the hero colours now names the standard.
John, it's your skill pack, so merge it if it reads right. Happy to adjust the wording.
Diff Skip to comments
@@ -1,773 +1,782 @@⋯ 138 unchanged lines ⋯ ### Readable 3D reference artwork +The exact rules are the **adom-hero 1.0** standard on [adom/component-hero](https://wiki.adom.inc/adom/component-hero):+layer and material names, colours, dash and label geometry, pin 1, metadata (`asset.extras.adomHero`) and+the checks a hero must pass. Build the hero with that skill's deterministic generator+(`scripts/hero_glb.py <board-use.glb> <footprint.kicad_mod> <page.json> <slug>-hero.glb --png preview.png`)+rather than by hand, publish it as `<slug>-hero.glb` in `component.parts.model_3d`, and keep the clean model+in `model_3d_plain`. What follows summarises it.+ The physical chip remains sourced from the manufacturer. Add reference artwork as separate named, nonphysical layers aligned to the verified footprint seating plane in Adom Z-up. Preserve units, pin-1 orientation, pad rotations and corner radii.⋯ 8 unchanged lines ⋯ | Copper-pad boundaries | Teal dashed outlines, 50% transparent (material alpha 0.50). | | Silkscreen contours | 70% transparent (material alpha 0.30). | | Pad labels | Actual signal/pin names, 50% transparent (alpha 0.50), placed legibly outside the body. |+| Pin 1 | On the silkscreen layer: the footprint's own pin-1 mark, or an added dot beside pad 1 (recorded as AI-added) when the footprint has none. | | Package MPN | Exact manufacturer part number on a deliberately chosen clear surface, readable when zoomed in, using `adom-chip-laser`. | Resolve signal names through the canonical pin-to-pad mapping and datasheet; never⋯ 603 unchanged lines ⋯ Remove only explicitly identified nonphysical footprint/silkscreen/label helper subtrees before creating high; prune their unused geometry/materials. Derive lower levels from that clean board-use high. Keep manufacturer originals and the annotated hero unchanged, and record separate source hashes, asset purpose and removal proof. A viewer hiding the helpers at runtime is defense in depth, not an acceptable substitute for clean reusable downloads. -For the wiki hero, retain teal dashed footprint outlines at 50% transparency, pad signal names at 50% transparency (unique pad numbers when no real names exist), and silkscreen at 70% transparency. Hero and all LODs share the verified Z-up frame, units and seating transform; do not rotate or recenter individual derivatives. Cache chip outlines from the approved physical chip and marking placement, excluding floating footprint annotations.+For the wiki hero (exact rules: adom-hero 1.0 on adom/component-hero), retain teal dashed footprint outlines at 50% transparency, pad signal names at 50% transparency (unique pad numbers when no real names exist), and silkscreen at 70% transparency. Hero and all LODs share the verified Z-up frame, units and seating transform; do not rotate or recenter individual derivatives. Cache chip outlines from the approved physical chip and marking placement, excluding floating footprint annotations. Validate scene contents and visually inspect top, underside and an assembled-board placement. Require zero footprint/silkscreen/label helper nodes in every LOD, real terminals intact, and unchanged hero hashes. Refresh all downstream hashes, cached previews and dependent board assets after a correction. Never reuse a hero screenshot as a preview of a clean board LOD. ⋯ 2 unchanged lines ⋯ ## Ship the bench with a board or project page A board, molecule or project page can carry its author's Hydrogen layout: `hydrogen/workspace.json` in the page repo, with the 3D layout pane, the KiCad or Altium dashboard, the parts search and the project page arranged the way you work. Export it from a live Hydrogen with `adom-cli hydrogen workspace export --out hydrogen/workspace.json`, push it with `adom-wiki repo push <owner>/<slug> --files hydrogen/workspace.json`, and readers of a fork or clone open it with `adom-cli hydrogen workspace apply <owner>/<slug>` (Hydrogen Cloud lists it under Project workspaces with an Apply button). Apps are referenced by wiki page, never by URL; declare each in `page.json` `dependencies`. The full contract and the `WORKSPACE_*` hints are in the wiki-workspaces skill.+@@ -1,36 +1,37 @@⋯ 30 unchanged lines ⋯ Remove only explicitly identified nonphysical footprint/silkscreen/label helper subtrees before creating high; prune their unused geometry/materials. Derive lower levels from that clean board-use high. Keep manufacturer originals and the annotated hero unchanged, and record separate source hashes, asset purpose and removal proof. A viewer hiding the helpers at runtime is defense in depth, not an acceptable substitute for clean reusable downloads. -For the wiki hero, retain teal dashed footprint outlines at 50% transparency, pad signal names at 50% transparency (unique pad numbers when no real names exist), and silkscreen at 70% transparency. Hero and all LODs share the verified Z-up frame, units and seating transform; do not rotate or recenter individual derivatives. Cache chip outlines from the approved physical chip and marking placement, excluding floating footprint annotations.+For the wiki hero (exact rules: adom-hero 1.0 on adom/component-hero), retain teal dashed footprint outlines at 50% transparency, pad signal names at 50% transparency (unique pad numbers when no real names exist), and silkscreen at 70% transparency. Hero and all LODs share the verified Z-up frame, units and seating transform; do not rotate or recenter individual derivatives. Cache chip outlines from the approved physical chip and marking placement, excluding floating footprint annotations. Validate scene contents and visually inspect top, underside and an assembled-board placement. Require zero footprint/silkscreen/label helper nodes in every LOD, real terminals intact, and unchanged hero hashes. Refresh all downstream hashes, cached previews and dependent board assets after a correction. Never reuse a hero screenshot as a preview of a clean board LOD.+
Comments
Log in to comment.
No comments yet.