Adom Wiki Skill Pack

@@ -197,3 +197,5 @@ existing 3D viewer handles full chip rendering. ### Component hero and board model separation  The component and LOD skills now distinguish annotated wiki heroes from clean board-use LODs. Every LOD, including high, excludes footprint outlines, pad labels and silkscreen, while preserving actual terminals and reviewed chip markings. The LOD widget uses cached image previews before the user enables 3D.++Component LOD guidance also covers exact micrometre placement transforms, real rendered MPN checks, authenticated lazy asset transport under the wiki sandbox, short-viewport preview activation, and recording review.

@@ -1,7 +1,7 @@ {   "slug": "adom-wiki-skillpack",   "title": "Adom Wiki Skill Pack",-  "version": "0.8.10",+  "version": "0.8.11",   "type": "skill",   "hero": {     "path": "screenshots/hero.png"@@ -75,7 +75,7 @@   ],   "dependencies": {     "adom/adom-wiki-hero-image": "^0.2.2",-    "adom/component-widgets": "^1.1.7"+    "adom/component-widgets": "^1.1.12"   },   "files": [     "SKILL.md",

@@ -2,7 +2,7 @@   "type": "skill",   "slug": "adom-wiki-skillpack",   "title": "Adom Wiki Skill Pack",-  "brief": "How to use the Adom Wiki without breaking pages \u2014 the wiki is six tools in one (git, package manager, releases, discussions, PRs, discovery), and three repo archetypes have emerged from real use: Page, Skillpack, and Family. Plus how to publish rich component pages (chips, molecules, boards). One install, 15 skills, plus a write-up of the design patterns for the people who build the wiki.",+  "brief": "How to use the Adom Wiki without breaking pages — the wiki is six tools in one (git, package manager, releases, discussions, PRs, discovery), and three repo archetypes have emerged from real use: Page, Skillpack, and Family. Plus how to publish rich component pages (chips, molecules, boards). One install, 15 skills, plus a write-up of the design patterns for the people who build the wiki.",   "hero": {     "type": "image",     "path": "screenshots/hero.png"@@ -104,7 +104,10 @@     "component LDO detail levels",     "coarse-first board viewer",     "3D board GPU memory freeze",-    "reviewed chip artwork in assembled board"+    "reviewed chip artwork in assembled board",+    "hero GLB versus board LOD",+    "footprint or silkscreen baked into high LOD",+    "image-first component LOD previews"   ],   "discovery_pitch": "Anything touching wiki.adom.inc: publishing, page archetypes, readmes, heroes, discovery, and the wiki-bloat rule (find where a thing already lives before creating any page).",   "sample_prompts": [@@ -121,11 +124,11 @@       "prompt": "Before I create this wiki page, check whether the thing already has a home."     }   ],-  "version": "0.8.10",-  "description": "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.",+  "version": "0.8.11",+  "description": "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 marking, reusable thumbnail caches and component-page widgets.",   "dependencies": {     "adom/adom-wiki-hero-image": "^0.2.2",-    "adom/component-widgets": "^1.1.7"+    "adom/component-widgets": "^1.1.12"   },   "files": [     "SKILL.md",@@ -154,7 +157,14 @@     "skills/wiki-discovery/SKILL.md",     "skills/wiki-scoring/SKILL.md",     "skills/wiki-bloat/SKILL.md",-    "skills/wiki-readme-slideshow/SKILL.md"+    "skills/wiki-readme-slideshow/SKILL.md",+    "skills/wiki-sub-readme/SKILL.md",+    "skills/wiki-subreadme/SKILL.md",+    "skills/wiki-hero-studio/SKILL.md",+    "skills/wiki-component-lod/SKILL.md",+    "skills/wiki-component-lod/references/generation.md",+    "skills/wiki-component-lod/references/verification.md",+    "skills/wiki-component-lod/references/runtime.md"   ],   "scripts": {     "install": "./install.sh",@@ -176,4 +186,4 @@     "email": "[email protected]"   },   "org": "adom"-}+}\ No newline at end of file

@@ -25,7 +25,7 @@ Maintain two explicitly named products in the same component repo: | Product | Included content | Consumer | |---|---|---| | Annotated wiki hero GLB | Reviewed chip body, actual manufacturer terminals, manufacturer markings, reviewed virtual MPN, plus footprint pad outlines, unique pad labels and silkscreen reference art. | Component page inspection hero. |-| Board component LOD GLBs, all four levels including high | Chip body, actual terminals/leads, manufacturer markings and the reviewed virtual MPN where legible at that detail level. No footprint copper/pad outlines, pad labels or numbers, silkscreen, courtyard, substrate or other board reference artwork. | EDA board, scaffold and digital-twin assembly viewers. |+| Board component LOD GLBs, all four levels including high | Chip body, actual terminals/leads, manufacturer markings and the reviewed virtual MPN where legible at that detail level. No footprint copper/pad outlines, pad labels or numbers, silkscreen, courtyard, external board substrate or other board reference artwork. | EDA board, scaffold and digital-twin assembly viewers. |  The EDA board supplies its own copper, pads and silkscreen. Never bake those into any component LOD, even high. Actual package terminals and exposed metal pads are physical chip geometry and MUST remain; do not remove them by matching the word "pad" or by deleting all transparent materials. The virtual laser-etched MPN is reviewed chip identification artwork and stays in high/medium at its approved location. Coarse levels may omit it when unreadable, with that omission recorded. 

@@ -11,3 +11,9 @@ The native board substrate, copper, vias and silkscreen also need budgets. Component LOD alone does not fix thousands of board-surface primitives. Keep native manufacturing geometry intact; generate separate presentation derivatives.  Primary references: [glTF Transform simplification](https://gltf-transform.dev/modules/functions/functions/simplify), [meshoptimizer](https://github.com/zeux/meshoptimizer).++## Preserve small placement transforms when writing GLBs++Metre-scale component art can contain deliberate micrometre offsets that keep the reviewed virtual MPN visible on its chosen surface. Some exporters suppress near-identity transforms: glTF Transform 4.5.0's writer uses a default 1e-5 equality tolerance when omitting TRS values, which can discard a 6e-6 metre marking offset. Geometry can remain present while the marking sinks into the body.++Preserve exact local TRS or matrices through serialization. Read the written file back and compare retained node world transforms against high/source, with precision tighter than the smallest meaningful placement. Do not move or re-etch the reviewed source to compensate for an exporter error. Recheck actual top/side renders, not only mesh counts or an MPN-present flag. Prune unused hero materials as well as helper nodes and geometry, then refresh hashes, previews and downstream caches. The native substrate inside a physical module is part of that component and remains; only external board/reference substrate artwork is excluded.

@@ -29,3 +29,9 @@ Primary reference: [Babylon LOD](https://doc.babylonjs.com/features/featuresDeep Show cached PNG/WebP previews of the actual four board-use LOD files by default. Use the same camera, framing and lighting to make comparison meaningful; record the corresponding GLB hash in each preview entry and invalidate stale screenshots. No WebGL context, Babylon import or GLB downloads until the user enables the interactive preview.  On enable, use one viewer starting with super-low, then load/swap detail as the user zooms with hysteresis and eviction. Show the active level truthfully. Turn off must abort pending loads and dispose the scene, engine and GPU resources. Release on hidden tab, offscreen widget or disconnect, and coordinate to avoid multiple active previews. Test repeated enable/zoom/disable cycles and actual live wiki authentication, CSP and module-loading behavior. A passing local harness does not establish live wiki behavior.++## Wiki sandbox and private component files++Use the current `component-widgets` skill for authenticated on-demand loading. The registered widget receives server-inlined JSON; that does not authorize credentialed GLB fetch from its opaque origin. Component-owned `*.frame.html` transports can load under normal wiki page authorization only when requested, transfer the selected GLB bytes to the exact parent request, and be removed immediately. Verify source iframe, nonce, SHA-256, size and cancellation; pass verified bytes directly to Babylon instead of fetching a disallowed blob URL. Never weaken the sandbox or expose private models publicly. The direct GLB remains the canonical reusable board file.++Web Storage can be unavailable in sandboxed frames. Use ephemeral preferences only when real storage access throws. Shared-viewer environment textures and ready/error reporting require explicit sandbox checks. Local model/resource tests and the actual deployed viewer's appearance are separate evidence. Wiki frames may be lazy-loaded: reveal the relevant section and wait for the actual frame/context before interacting. Preserve the user's editor pane and foreground.

@@ -19,3 +19,5 @@ Recording is a separate resource user. Verify the actual recorder target, engine For incidents, preserve evidence (versions, returned source, primitive counts, frame timing and logs), duplicate-check and file on the owning viewer/bridge/wiki project. Distinguish observations from suspected causes: a high static mesh count is not proof of a leak. Recheck a live process or recording handle before restarting. Source fixes, generated caches, published skills, installed skills and running AI context must each be verified separately.  Reject any board LOD containing footprint outlines, pad names/numbers, silkscreen or other nonphysical board art, including high. Inspect top and underside to distinguish real package terminals from footprint helpers. Verify the separately annotated hero remains unchanged.++A successful model download is not a visible result. Check actual scene readiness, loading-overlay dismissal and a rendered screenshot. Exercise enable when the button is near the bottom of a short viewport: reveal the expanded viewer before offscreen observation, then prove that later scrolling it offscreen releases resources. Record failed takes separately from accepted motion footage, with per-clip trim/crop and editorial metadata.

@@ -611,7 +611,7 @@ Maintain two explicitly named products in the same component repo: | Product | Included content | Consumer | |---|---|---| | Annotated wiki hero GLB | Reviewed chip body, actual manufacturer terminals, manufacturer markings, reviewed virtual MPN, plus footprint pad outlines, unique pad labels and silkscreen reference art. | Component page inspection hero. |-| Board component LOD GLBs, all four levels including high | Chip body, actual terminals/leads, manufacturer markings and the reviewed virtual MPN where legible at that detail level. No footprint copper/pad outlines, pad labels or numbers, silkscreen, courtyard, substrate or other board reference artwork. | EDA board, scaffold and digital-twin assembly viewers. |+| Board component LOD GLBs, all four levels including high | Chip body, actual terminals/leads, manufacturer markings and the reviewed virtual MPN where legible at that detail level. No footprint copper/pad outlines, pad labels or numbers, silkscreen, courtyard, external board substrate or other board reference artwork. | EDA board, scaffold and digital-twin assembly viewers. |  The EDA board supplies its own copper, pads and silkscreen. Never bake those into any component LOD, even high. Actual package terminals and exposed metal pads are physical chip geometry and MUST remain; do not remove them by matching the word "pad" or by deleting all transparent materials. The virtual laser-etched MPN is reviewed chip identification artwork and stays in high/medium at its approved location. Coarse levels may omit it when unreadable, with that omission recorded. @@ -620,3 +620,5 @@ Remove only explicitly identified nonphysical footprint/silkscreen/label helper 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.  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.++Validate the actual written LOD transforms and visible MPNs; micrometre offsets must survive serialization. See wiki-component-lod generation guidance. Internal physical module substrates remain part of the chip model. Use the shared component-widgets skill for image-first, authenticated sandbox LOD inspection.