← All Pull Requests

Make component pages reusable and ship discoverable Z-up hero guidance #4

Closed opened by John Lauer

Component pages currently drift into the first consuming project's progress log, and the component skill does not explain how manufacturer STEP axes relate to Adom's Z-up world. This change makes a component README a reusable exact-MPN catalog record, routes project-specific decisions to their existing project, and adds model/hero validation guidance and discovery triggers.

The package draft also repairs malformed YAML in the root and wiki-bloat descriptions, installs the advertised component-page generator, and includes three existing skills missing from files[] and install.sh. The installer and uninstaller agree on all 21 skills. The component viewer route example now includes the owner observed in the live wiki.

Validation: packed 0.8.4 locally; all 21 packaged skill frontmatters pass strict YAML parsing; isolated install and repeated install preserve byte-identical skills and all three documented generator assets; uninstall cleans the isolated destination. Tarball SHA256: 80e0717555d1fbd61f537bf3fdae25d3a4df956a531abe4fbce272118239690f.

This is a contribution for owner review and package release, not a claim that all users have received it. The existing installer targets Claude's skills directory; cross-runtime catalog propagation still needs its normal ecosystem distribution path. PR #3's wiki-bloat content is separate; the only overlap here is its identical YAML scalar fix. Preserve that content when merging either order. No new wiki page or hero is introduced.

Diff Skip to comments (4)

--- a/SKILL.md+++ b/SKILL.md@@ -1,121 +1,124 @@ --- name: adom-wiki-skillpack user-invocable: true-description: >-, wiki bloat, too many wiki pages, should this be a page.+description: >-   The Adom Wiki Skill Pack, the entry point for working with the Adom Wiki   (wiki.adom.inc). Read this BEFORE creating, publishing, or restructuring any   wiki page. The wiki is six tools in one (git host + wiki package manager (`adom-wiki pkg`) +   release database + discussion forum + pull requests + discovery), and three repo   archetypes have emerged from real use: Page, Skillpack, and Family. This pack-  routes to 16 focused sub-skills and carries the hard rules that keep pages from+  routes to 20 focused sub-skills and carries the hard rules that keep pages from   breaking. Trigger words: adompkg (deprecated old name), the wiki, adom wiki, wiki.adom.inc, publish to the   wiki, wiki repo, wiki page, what kind of wiki repo, repo archetype, skillpack,   super-skill, wiki family, parent child repo, wiki readme, hero unlinked,   proprietary wiki page, private source public app, wiki breadcrumb, fork a wiki   page, wiki discovery, page not surfacing, wiki scoring, trending, high five,   adom-wiki pkg publish, publish a chip, component page, chip page, molecule page,-  tape and reel, pin 1 orientation.+  tape and reel, pin 1 orientation, reusable component README, generic component+  page, component hero, chip hero, GLB orientation, Z-up, Y-up, wiki bloat,+  too many wiki pages, should this be a page. ---  # Adom Wiki Skill Pack⋯ 74 unchanged lines ⋯ | **wiki-sub-readme** | Make a sub-readme: a 2nd doc in the page repo, linked from the README. The repo-push / relative-link / image-path gotchas. | | **wiki-visibility** | Public vs private source, public releases, the private readme, open vs closed pages. | | **wiki-repo-styles** | The archetype taxonomy (Page / Skillpack / Family) and how to choose. |-| **wiki-component** | Publish a component page: chip / molecule / board; the tabbed chip CAD-hub README. |+| **wiki-component** | Publish a reusable component page for all users; generic README versus project notes, manufacturer provenance, Z-up GLB and chip hero checks, symbol/footprint/3D viewers. | | **wiki-family** | Build a Family: naming convention, family tag, anchor registry, breadcrumbs. | | **wiki-skillpack** | Build a Skillpack: layout, install.sh, files[], skill map, the `-skillpack` suffix. | | **wiki-hero** | The hero image: generate it (adom-wiki-hero-image), and never let it get unlinked. |⋯ 17 unchanged lines ⋯ - "Bundle these skills into one package" → wiki-skillpack - "Add a child plugin to adom-usb" → wiki-family - "Publish this chip / molecule / board to the wiki" → wiki-component+--- a/README.md+++ b/README.md@@ -1,179 +1,184 @@ # Adom Wiki Skill Pack -**One install, 15 skills that teach the AI to use the Adom Wiki without breaking+**One install, 21 skills that teach the AI to use the Adom Wiki without breaking pages, plus a write-up of the wiki repo archetypes that have emerged from real use.** ⋯ 20 unchanged lines ⋯ adom-wiki pkg install adom-wiki-skillpack ``` -This drops the main `adom-wiki-skillpack` skill plus 14 sub-skills onto your+This drops the main `adom-wiki-skillpack` skill plus 20 sub-skills onto your container, and pulls in **`adom-wiki-hero-image`** (a dependency) for hero generation. +## Component pages and 3D heroes++Read [wiki-component](skills/wiki-component/SKILL.md) before publishing a chip or purchased part. It covers reusable descriptions for all users, separation from project notes, manufacturer provenance, Z-up GLB orientation, and verified hardware hero renders. [wiki-hero](skills/wiki-hero/SKILL.md) covers registration. The component-page generator is installed beside the component skill.+ ## The wiki is six tools in one  It feels like a wiki, but it's a fusion of six tools you already know, all keyed⋯ 140 unchanged lines ⋯ ## License  MIT.+--- a/package.json+++ b/package.json@@ -1,122 +1,134 @@ {   "slug": "adom-wiki-skillpack",   "title": "Adom Wiki Skill Pack",-  "version": "0.8.3",+  "version": "0.8.4",   "type": "skill",   "hero": {     "path": "screenshots/hero.png"⋯ 47 unchanged lines ⋯     "too many wiki pages",     "should this be a page",     "where should this skill live",-    "add a skill to the pack"+    "add a skill to the pack",+    "reusable component README",+    "generic component page",+    "component hero",+    "chip hero",+    "GLB orientation",+    "Z-up",+    "Y-up",+    "chip standing on edge"   ],   "dependencies": {     "adom/adom-wiki-hero-image": "^0.2.2"⋯ 25 unchanged lines ⋯     "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-hero-studio/SKILL.md",+    "skills/wiki-sub-readme/SKILL.md",+    "skills/wiki-subreadme/SKILL.md"   ],   "scripts": {     "install": "./install.sh",⋯ 26 unchanged lines ⋯   ],   "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)." }+--- a/page.json+++ b/page.json@@ -1,165 +1,174 @@⋯ 1 unchanged line ⋯   "type": "skill",   "slug": "adom-wiki-skillpack",   "title": "Adom Wiki Skill Pack",-  "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.",+  "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.",   "hero": {     "type": "image",     "path": "screenshots/hero.png"⋯ 31 unchanged lines ⋯       "wiki breadcrumb",       "fork a wiki page",       "wiki scoring",-      "wiki trending"+      "wiki trending",+      "component page",+      "reusable component README",+      "generic component page",+      "component hero",+      "chip hero",+      "GLB orientation",+      "Z-up",+      "Y-up"     ]   },   "discovery_triggers": [⋯ 62 unchanged lines ⋯     }   ],   "version": "0.8.2",-  "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.",+  "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.",   "dependencies": {     "adom/adom-wiki-hero-image": "^0.2.2"   },⋯ 47 unchanged lines ⋯   },   "org": "adom" }+--- a/install.sh+++ b/install.sh@@ -1,31 +1,41 @@⋯ 17 unchanged lines ⋯ install_skill wiki-visibility     skills/wiki-visibility/SKILL.md install_skill wiki-repo-styles    skills/wiki-repo-styles/SKILL.md install_skill wiki-component      skills/wiki-component/SKILL.md+mkdir -p "$DEST/wiki-component/component-page-generator"+cp skills/wiki-component/component-page-generator/gen_chip.py \+   skills/wiki-component/component-page-generator/template.html \+   skills/wiki-component/component-page-generator/mkviewers.sh \+   "$DEST/wiki-component/component-page-generator/" install_skill wiki-family         skills/wiki-family/SKILL.md install_skill wiki-skillpack      skills/wiki-skillpack/SKILL.md install_skill wiki-hero           skills/wiki-hero/SKILL.md⋯ 3 unchanged lines ⋯ install_skill wiki-scoring        skills/wiki-scoring/SKILL.md install_skill wiki-bloat          skills/wiki-bloat/SKILL.md -echo "OK: Installed the Adom Wiki Skill Pack plus 16 bundled skills to $DEST/."+install_skill wiki-hero-studio skills/wiki-hero-studio/SKILL.md+install_skill wiki-sub-readme skills/wiki-sub-readme/SKILL.md+install_skill wiki-subreadme skills/wiki-subreadme/SKILL.md++echo "OK: Installed the Adom Wiki Skill Pack plus 20 bundled skills to $DEST/." echo "Hint: Ask Claude 'publish this to the wiki', 'what kind of wiki repo should this be', 'how do I make a readme', or 'why isn't my wiki page surfacing'."+--- a/uninstall.sh+++ b/uninstall.sh@@ -1,10 +1,12 @@⋯ 3 unchanged lines ⋯ for n in adom-wiki-skillpack \          wiki-anatomy wiki-api wiki-publish-safely wiki-readme wiki-readme-html wiki-visibility \          wiki-repo-styles wiki-component wiki-family wiki-skillpack wiki-hero \-         wiki-breadcrumbs wiki-forking wiki-discovery wiki-scoring wiki-bloat; do+         wiki-breadcrumbs wiki-forking wiki-discovery wiki-scoring wiki-bloat \+         wiki-readme-slideshow wiki-hero-studio wiki-sub-readme wiki-subreadme; do   rm -rf "$DEST/$n" done-echo "OK: Removed the Adom Wiki Skill Pack and its 14 bundled skills."+echo "OK: Removed the Adom Wiki Skill Pack and its 20 bundled skills."+--- a/skills/wiki-component/SKILL.md+++ b/skills/wiki-component/SKILL.md@@ -1,328 +1,386 @@⋯ 13 unchanged lines ⋯   molecule page, pcb component, tape and reel, pin 1 orientation, pick and place,   kicad altium orcad fusion library, parametric specs, mouser digikey price stock,   provenance, prove the data, datasheet page citation, embed symbol footprint-  viewer, open chip in tool.+  viewer, open chip in tool, reusable component README, generic component page,+  component hero, chip hero, GLB orientation, Z-up, Y-up, chip standing on edge. ---  Parent skill: **adom-wiki-skillpack**  # Publishing a component (chip / molecule / PCB) +## Write for every user of the component++A purchased component page is a shared catalog record for the exact manufacturer+part number. Its title, description, Overview and README must make sense to an+engineer who has never seen the project that first used it. Lead with manufacturer,+exact MPN, function, package and source-backed capabilities. Explain general pin+functions, operating constraints, manufacturer resources and reusable library status.++Keep a particular board's reference designators, chosen resistor values, rail names,+selection rationale, experiment progress, desktop permissions and machine-specific+bridge status in that project's existing umbrella or molecule page. A short Related+link to a consuming project is useful; it must not turn the component description+into that project's progress report. Label application examples as examples, not+universal requirements. Keep shared artifact limitations on the component page when+they affect any user, with exact file/revision and evidence rather than session history.++Before publishing, search and reuse the exact component record, read its current+remote files, preserve other contributors' content and manufacturer originals, and+check which README actually renders. `readme.html` can shadow `README.md`; update+the visible prose too. Verify the live identity, generic description and source links.+Put board-specific notes in the existing project, not a new documentation repo.++## Component GLB, Z-up and hero workflow++Read `adom-step`, `adom-lbr-component-fidelity` and `chip-thumbnailer` before+converting or posing a component; read [wiki-hero](../wiki-hero/SKILL.md) for hero+registration and the current `hero-studio` hardware workflow for composition.+If one is absent from the installed catalog, search the wiki by its name and read+the owning package's SKILL.md. An absent installed trigger is not evidence that+the workflow does not exist.++Adom's component/board world is **Z-up**, with the component seating plane on XY.+An original manufacturer STEP can use different axes. Preserve its bytes and hash;+record source units, source up axis, seating plane and pin-1 evidence separately+from the derived display transform. Standard glTF uses Y-up, while an Adom viewer+may already apply an axis conversion. Inspect both the GLB node transforms and the+actual viewer import/camera convention. Do not apply a blanket 90-degree rotation+twice or fix an orientation problem by changing only the camera.++For a derived GLB, retain provenance and the explicit source-to-Adom transform.+Check physical dimensions, underside/seat plane, pin-1-to-pad alignment and top+markings in the target viewer using top and oblique views before producing the+hero. A bounding box or successful conversion alone does not establish pin 1 or+seating. A manufacturer's dimension mismatch remains a mismatch after rotation;+do not scale its geometry to conceal it. Preserve unverified status until checked.++Use the actual verified component geometry for a hardware hero. Virtual MPN marks+are labeled display derivatives or overlays, not claimed manufacturer markings.+Generate the matching symbol's central chip outline from the same oriented source,+preserve intelligent pin groups, and inspect symbol/footprint/model together.+Register the hero in page.json without duplicating it in the README; open the+authenticated live page in a work pane, preserve the editor and foreground, and+verify that the published model and hero have the same correct pose.+ `component` is a first-class **wiki page type** (alongside `app` and `skill`, see **wiki-api**). Structurally a component is usually the **Page** archetype; chip families use the **Family** archetype (see **wiki-repo-styles**), e.g. an `stm32f4`⋯ 31 unchanged lines ⋯   blobs) from the `.kicad_mod`, - a **datasheet** section, and a **CAD downloads grid** (typed icons per file). -These are served at `https://wiki.adom.inc/viewer/{3d,symbol,footprint}/component/<slug>`+Resolve viewer links from the current component page. The owner-qualified route+verified on 9 September 2026 is+`https://wiki.adom.inc/viewer/{3d,symbol,footprint}/<owner>/component/<slug>` and are genuinely interactive (drag, zoom, layer toggle). They embed anywhere (the wiki dropped `frame-ancestors`), so you can `<iframe>` them into a custom page. ⋯ 261 unchanged lines ⋯ > ⏳ This skill records the live constraints as of its writing (README.md is > sanitized, but `readme.html` custom pages SHIPPED, verified 2026-07-15; still > no page→desktop bridge). Re-verify and update when the bridge ships.+--- a/skills/wiki-hero/SKILL.md+++ b/skills/wiki-hero/SKILL.md@@ -1,103 +1,112 @@⋯ 24 unchanged lines ⋯  ## Generating it +For a **hardware component**, first read+[wiki-component](../wiki-component/SKILL.md), especially its Z-up GLB and hero+workflow. Use the verified physical component render and a generic part description.+Read the current `hero-studio` hardware guidance for composition; an app screenshot+inside window chrome is not the component hero recipe. Preserve the manufacturer's+original model, validate the derived pose in the actual viewer and keep virtual MPN+markings identified as overlays. The app-specific composition below applies to apps.+ Use the **adom-wiki-hero-image** package, it's a declared **dependency of this pack**, so `adom-wiki pkg install adom-wiki-skillpack` pulls it automatically. It bundles the brand fonts + ADOM wordmark + the render pipeline, so it works⋯ 70 unchanged lines ⋯ - [ ] Complete `page.json` pushed AFTER `adom-wiki pkg publish` - [ ] `GET /pages/<slug>` → `hero_path` set - [ ] Hero visually confirmed in pup+--- a/skills/wiki-bloat/SKILL.md+++ b/skills/wiki-bloat/SKILL.md@@ -1,153 +1,155 @@ --- name: wiki-bloat-description: Wiki-bloat is when wayyyy too many wiki pages are being made. THE rule against it, straight from John (Adom's founder): before creating ANYTHING on the wiki, first find where that thing should already live, and put it there. "Add it to the skillpack" means literally that, locate the existing pack's repo and add a SKILL.md file to it; it never means mint a new page. Read this BEFORE any POST /pages, any new slug, any "should this be its own page" moment. Trigger words: wiki bloat, wiki-bloat, too many wiki pages, too many pages, should this be a page, new wiki page, create a wiki page, standalone page or skillpack, where should this skill live, add a skill to the pack, fold into existing, one page too many, page sprawl, new slug.+description: >-+  Wiki-bloat is when wayyyy too many wiki pages are being made. THE rule against it, straight from John (Adom's founder): before creating ANYTHING on the wiki, first find where that thing should already live, and put it there. "Add it to the skillpack" means literally that, locate the existing pack's repo and add a SKILL.md file to it; it never means mint a new page. Read this BEFORE any POST /pages, any new slug, any "should this be its own page" moment. Trigger words: wiki bloat, wiki-bloat, too many wiki pages, too many pages, should this be a page, new wiki page, create a wiki page, standalone page or skillpack, where should this skill live, add a skill to the pack, fold into existing, one page too many, page sprawl, new slug. ---  # Wiki-bloat, and how not to cause it⋯ 144 unchanged lines ⋯ wiki-repo-styles (the archetypes and when each is right), wiki-skillpack (the mechanics of adding a sub-skill to a pack), wiki-hero + wiki-hero-studio (the human gate), wiki-forking (the PR path into pages you do not own), wiki-discovery (why overlapping triggers hurt).+

Comments

John Lauer ·

Additional user requirements are consolidated in the attached updated wiki-component skill and patch against PR 4. They cover exact signal labels, teal pad dashes at alpha 0.50, silkscreen at alpha 0.30, top MPN via adom-chip-laser, suppressed internal CAD tooltips, every-IC grouped artwork, schematic role comments, manufacturer provenance, Basic Parts/Mouser sourcing, native parity and motion clip evidence.

Validation: strict YAML frontmatter parse passed. Viewer material, marking and persistence checks remain tracked separately in the consuming project. This comment attaches a candidate update; it does not change PR 4's submitted head or claim a released/installed package. Please apply the patch together with the existing PR changes.

SKILL.md

wiki-component-presentation.patch

John Lauer ·

Updated component creation guidance from live component review: restrict edits to an explicit project-created page allowlist when requested; compare manufacturer standalone and bundled STEP contacts; prefer actual signal names with unique pad-number fallback for unnamed terminals; select a clear MPN etch surface from actual geometry, including optical-housing side walls; default original Adom-authored content to open source while retaining upstream terms; identify the manufacturer in Source and keep creation tools in artifact provenance.

The attached complete SKILL.md and patch consolidate these rules with the prior PR proposal. This comment supplies revised reviewable content; it does not change the submitted PR diff, merge the package or install the shared skill.

SKILL.md

wiki-component-latest-guidance.patch

John Lauer ·

The component-creation guidance has now been published in adom/adom-wiki-skillpack 0.8.5, with component-widgets 1.1.7. This supersedes the earlier attached candidate in this PR; the old file set should not be merged over the released source.

The released guidance covers manufacturer model provenance, Z-up reference artwork, unique pad labels, reviewed virtual MPN placement, reusable chip outlines and cache manifests, and an outline-only cache widget. The installer preserves and installs all 21 bundled skills to both Claude and Codex. Strict YAML, package coverage and isolated installation passed; actual installed wiki-component hashes match release source. Core 4.13.16 now includes the wiki skill pack in the default dependency graph. Running AI contexts still need an explicit skill read or a fresh session.

The live TMF8829 page demonstrates the corrected side-wall marking and cached outline: https://wiki.adom.inc/adom/tmf8829-1a

Colby Knox ·

Closing without merging, per your own last comment here: the component-page guidance in this PR was superseded by the 0.8.5 through 0.8.11 publishes, which already carry the reusable-README section, the Z-up and hero workflow, the owner-qualified viewer route, the YAML frontmatter fixes, the files[] and installer coverage, and the wiki-component-lod skill. Merging this file set now would have rolled wiki-component back by about 240 lines.

The one piece that had not landed was the wiki-hero "For a hardware component" paragraph. That is now on master and in 0.8.12 (commit 1f02713), credited to this PR. Thanks for the work, John.

Log in to comment.