Adom Wiki Skill Pack

@@ -193,3 +193,7 @@ retroactively change their loaded context.  The cache widget focuses on chip outlines and their reuse; the component page’s 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.

@@ -130,3 +130,5 @@ MPN markings, cached chip thumbnails and central symbol outlines, read instructions already loaded in an AI conversation are separate states.  For component LOD/LDO caches, zoom-driven detail, heavy board scenes or GPU/memory freezes, read `wiki-component-lod`. It covers both asset generation and runtime qualification.++For annotated wiki hero versus clean board LOD separation, footprint overlays leaking into high detail, or image-first LOD previews, read `wiki-component-lod` and `wiki-component`. All four board LODs exclude footprint, pad-label and silkscreen helpers; wiki heroes retain them.

@@ -1,12 +1,12 @@ {   "slug": "adom-wiki-skillpack",   "title": "Adom Wiki Skill Pack",-  "version": "0.8.9",+  "version": "0.8.10",   "type": "skill",   "hero": {     "path": "screenshots/hero.png"   },-  "description": "The Adom Wiki Skill Pack \u2014 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.",+  "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.",   "discovery_triggers": [     "publish to the wiki",     "the wiki",@@ -68,7 +68,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"   ],   "dependencies": {     "adom/adom-wiki-hero-image": "^0.2.2",

@@ -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,8 +124,8 @@       "prompt": "Before I create this wiki page, check whether the thing already has a home."     }   ],-  "version": "0.8.9",-  "description": "The Adom Wiki Skill Pack \u2014 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.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. 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"@@ -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

@@ -6,9 +6,9 @@ description: "Create and reuse high, medium, low and super-low component GLB det  Use this skill when a component page publishes multiple detail levels, a board/scaffold viewer consumes them, or a user reports a slow/frozen 3D view. Read `wiki-component` for page ownership, manufacturer provenance and reviewed markings. Reuse the existing component repo and cache; do not create a repo for each detail level. -The reviewed component appearance is an asset contract. Its virtual MPN, chosen marking surface, manufacturer logo, pin-1 information, material colors and footprint coordinate frame must carry through to the assembled board and digital twin. Replacing that with an unmarked STEP tessellation silently loses reviewed work. Keep the original manufacturer STEP unchanged for physical CAD and retain the reviewed GLB as the presentation authority.+The reviewed component appearance is an asset contract. Its virtual MPN, chosen marking surface, manufacturer logo, pin-1 information, material colors and footprint coordinate frame must carry through to the assembled board and digital twin. Replacing that with an unmarked STEP tessellation silently loses reviewed work. Keep the original manufacturer STEP unchanged for physical CAD and retain the reviewed chip geometry and markings as the presentation authority, with separate annotated-hero and clean board-use products. -Publish four levels: **high, medium, low, super-low**. High preserves the reviewed geometry and markings; compatible primitive batching is allowed with geometric/material equivalence checks. Lower levels are measured derivatives of that source, reviewed at their intended display sizes. Coarse detail must not become an invented generic package or erase the distinguishing silhouette, terminals or optical openings. All levels share units, pivot, handedness and Z-up footprint pose. No per-level recentering or automatic rotation.+Publish four levels: **high, medium, low, super-low**. High preserves the reviewed physical chip geometry and markings, excluding hero-only footprint annotations; compatible primitive batching is allowed with geometric/material equivalence checks. Lower levels are measured derivatives of that source, reviewed at their intended display sizes. Coarse detail must not become an invented generic package or erase the distinguishing silhouette, terminals or optical openings. All levels share units, pivot, handedness and Z-up footprint pose. No per-level recentering or automatic rotation.  Read the focused guidance needed for the work: @@ -17,3 +17,20 @@ Read the focused guidance needed for the work: - [Verification and incident handling](references/verification.md): visual parity, actual draw calls and GPU resources, repeated zoom tests, recording, performance regressions and safe recovery.  These are requirements and review procedures, not a claim that every Adom viewer already implements streaming LOD. Check the actual app version and runtime capabilities. A generated four-file set is not a tested LOD viewer; a single successful zoom is not proof of bounded memory.++## Separate wiki hero art from board LOD assets++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. |++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.++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.++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.

@@ -4,7 +4,7 @@ 2. Preserve the original source files. Generate under the same component repo, for example `lod/high.glb`, `lod/medium.glb`, `lod/low.glb`, `lod/super-low.glb`, with one manifest. Do not rewrite another author's preexisting component pages if the user excluded them. 3. Count primitives and decoded data before optimizing. A GLB with 79 mesh definitions can contain almost 12,000 primitives and create a corresponding number of Babylon render meshes. Small archive size is not evidence of cheap rendering. Batch only compatible triangle primitives/materials; preserve part identities, transforms, optical features, signal-label semantics and animation joints. Compare indexed positions/normals and material assignment before/after lossless batching. Handle normalized/quantized accessors correctly. 4. Generate lower levels with an error-bounded simplifier and measured output counts. Ratios are targets, not results: topology and error limits may prevent reduction. Weld compatible split vertices first when needed. Do not aggressively simplify text outlines, pin-1 indicators or optical interfaces without a specific visual review. Preserve their high-detail sources and restore full fidelity before they become readable on screen. If protected detail dominates the low-level budget, split it into an independently streamed detail layer instead of pretending the budget passed.-5. Maintain exact units, physical pivot and source-to-footprint pose for every level. Frame the hero around the asset; never recenter the asset to improve a screenshot. Preserve the same material colors. Record annotations (virtual MPN, pad outlines, signal labels) separately from manufacturer geometry so assemblies can control helper overlays without losing the actual chip markings.+5. Maintain exact units, physical pivot and source-to-footprint pose for every level. Frame the hero around the asset; never recenter the asset to improve a screenshot. Preserve the same material colors. Separate reviewed virtual MPN marking from hero-only pad outlines, signal labels and silkscreen. Remove the hero-only helpers before producing board-use high and every lower level; retain physical terminals and high/medium MPN. Record the removed helper subtrees and geometric equivalence of retained chip geometry. 6. Each manifest level records its relative path, SHA-256, compressed bytes, decoded attribute/index bytes, triangles, primitive instances/draw-call estimate, bounds, approximation/error settings and review status. Include generator versions, source hashes, source-to-display matrix, up axis, marking metadata and known exceptions. Use immutable content-addressed versions for consumers. No login tokens in published URLs or manifests. 7. The high asset must support close inspection of the exact MPN in its reviewed location. Coarse variants must be checked for silhouette, underside/terminal shape, package seating, optical opening shape and pin-1 ambiguity. Do not publish a numerical simplification result as visually approved. 

@@ -23,3 +23,9 @@ Choose explicit startup, resident-memory, triangle, draw-call, texture and concu Runtime/source version, generated assets, installed package and painted UI are separate evidence. Do not claim streaming/eviction works merely because `addLODLevel` was called.  Primary reference: [Babylon LOD](https://doc.babylonjs.com/features/featuresDeepDive/mesh/LOD/).++## Image-first component-page LOD widget++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.

@@ -5,7 +5,7 @@ Before opening a large assembly on the user's desktop, inspect the actual GLB pr Required evidence for a complete LOD implementation:  - All four levels exist, hashes match their source manifest, and units, axes, pivots and footprint transforms agree. Missing/stale cache files produce actionable diagnostics.-- Close-up high detail matches the reviewed component page: exact virtual MPN and placement, manufacturer markings, colors, terminal geometry and relevant pin-1 indicator. The same comparison is made in the assembled board. Shared symbol thumbnails remain derived from the reviewed art.+- Close-up high detail matches the physical chip portion of the reviewed component page (hero-only footprint/silkscreen/label overlays must be absent): exact virtual MPN and placement, manufacturer markings, colors, terminal geometry and relevant pin-1 indicator. The same comparison is made in the assembled board. Shared symbol thumbnails remain derived from the reviewed art. - Coarse silhouettes and critical features remain recognizable. Zoom transitions do not jump, flip or visibly change component placement. Orthographic/perspective, large/small packages, viewport resizing and scaffold-wide views are covered. - Cold start fetches coarse assets only. Repeated near/far zoom cycles demonstrate lazy detail fetch, hysteresis, reuse across identical parts, canceled stale requests and eventual eviction. Network logs and resource counters prove the behavior. Bound memory after repeated cycles, including reload/dispose and switching boards; one FPS sample is insufficient. - Capture startup evidence before the first screen-size promotion. A large part may legitimately request more detail immediately after coarse startup finishes. Verify request ordering and the initial coarse inventory; do not confuse later promotion with eagerly downloading high assets before the first usable frame.@@ -17,3 +17,5 @@ Required evidence for a complete LOD implementation: Recording is a separate resource user. Verify the actual recorder target, engine, frame progression and saved file. Hardware/GPU acceleration can help capture but cannot repair excessive scene draw calls or retained meshes. Stop this thread's recording and pause its renderer when the user reports slowdown; do not disturb other threads or take OS foreground. Record purposeful inspection motion after the resource checks pass. Keep per-take metadata so wrong-target, stalled or failed checks are excluded from product footage and retained only when useful for an explicitly chosen engineering edit.  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.

@@ -602,4 +602,21 @@ Official reference: https://dev-docs.kicad.org/en/addons/index.html  ## Board appearance, component LOD and freeze prevention -The assembled board must inherit the reviewed component wiki GLB, including virtual MPN placement and manufacturer markings. A raw STEP export does not include those enhancements automatically. For high/medium/low/super-low caches, coarse-first Babylon loading, bounded memory, eviction, idle rendering and full-scene performance checks, read `../wiki-component-lod/SKILL.md`. Generating detail files is distinct from qualifying an actual streaming viewer.+The assembled board must inherit a clean board-use derivative of the reviewed component chip, including virtual MPN placement and manufacturer markings. Do not place the annotated wiki hero GLB on the board: its footprint pad outlines, labels and silkscreen are hero-only helpers supplied independently by the EDA board. A raw STEP export does not include those enhancements automatically. For high/medium/low/super-low caches, coarse-first Babylon loading, bounded memory, eviction, idle rendering and full-scene performance checks, read `../wiki-component-lod/SKILL.md`. Generating detail files is distinct from qualifying an actual streaming viewer.++## Separate wiki hero art from board LOD assets++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. |++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.++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.++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.