Adom Wiki Skill Pack

@@ -1,7 +1,7 @@ {   "slug": "adom-wiki-skillpack",   "title": "Adom Wiki Skill Pack",-  "version": "0.7.8",+  "version": "0.7.9",   "type": "skill",   "hero": {     "path": "screenshots/hero.png"@@ -41,7 +41,16 @@     "page not surfacing",     "discover endpoint",     "wiki scoring",-    "wiki trending"+    "wiki trending",+    "readme.html",+    "readme html",+    "custom html readme",+    "readme iframe height",+    "readme-height",+    "resize readme iframe",+    "readme scrollbars",+    "readme iframe stuck at 600px",+    "wiki iframe resize"   ],   "dependencies": {     "adom/adom-wiki-hero-image": "^0.2.2"@@ -88,4 +97,4 @@     "open-source",     "mit"   ]-}\ No newline at end of file+}

@@ -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"@@ -77,7 +77,16 @@     "page not surfacing",     "discover endpoint",     "wiki scoring",-    "wiki trending"+    "wiki trending",+    "readme.html",+    "readme html",+    "custom html readme",+    "readme iframe height",+    "readme-height",+    "resize readme iframe",+    "readme scrollbars",+    "readme iframe stuck at 600px",+    "wiki iframe resize"   ],   "discovery_pitch": "The entry point for working with the Adom Wiki: 15 focused skills covering repo archetypes, publishing safely, READMEs (markdown and custom readme.html), heroes, components, families, and discovery.",   "sample_prompts": [@@ -94,8 +103,8 @@       "prompt": "Publish this chip as a component page on the wiki with symbol, footprint, and 3D viewers."     }   ],-  "version": "0.7.8",-  "description": "The Adom Wiki Skill Pack \u2014 one main skill plus 14 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.7.9",+  "description": "The Adom Wiki Skill Pack — one main skill plus 14 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"   },@@ -144,5 +153,6 @@   "author": {     "name": "John Lauer",     "email": "[email protected]"-  }+  },+  "org": "adom" }\ No newline at end of file

@@ -108,17 +108,56 @@ with the private-readme system for private-source/public-releases pages 1. **curl the endpoint**, confirm your exact bytes are live:    `curl -s "https://wiki.adom.inc/readme/<owner>/<type>/<slug>?variant=public"` 2. **Open the page in pup** (cache-bust `?v=<ver>`) and screenshot, confirm the-   iframe shows your layout, styles applied, at a sane height with no clipping-   or double scrollbars. Iframe sizing is controlled by the page, not you ,-   if your content clips, restructure toward a natural document flow and-   re-verify. (Sizing behavior is not yet fully characterized; report surprises-   on adom/wiki.)+   iframe shows your layout, styles applied, at full height with no clipping+   or double scrollbars. The iframe starts at a ~600px fallback; use the+   readme-height contract (next section) so it grows to fit your content. 3. **Check any JS ran**, bake a visible self-test into the page while    iterating (an element whose text a script rewrites), remove it when done. +## Sizing: the readme-height contract (ask the parent to fit you)++Verified against the live wiki bundle 2026-07-25. The page renders your readme+in the sandboxed iframe at a **~600px fallback min-height**. You cannot size it+from CSS, but the parent LISTENS: post it your height and it resizes the iframe+to fit, and clears the fallback so short readmes fit exactly.++```js+parent.postMessage({ type: 'readme-height', height: N }, '*');+// { type: 'resize', height: N } is also accepted+```++Drop-in reporter (load + layout changes + a slow safety interval, deduped):++```js+(function(){+  var last = 0;+  function report(){+    var h = Math.ceil(document.documentElement.scrollHeight) + 2;+    if (Math.abs(h - last) > 2) { last = h; parent.postMessage({ type: 'readme-height', height: h }, '*'); }+  }+  window.addEventListener('load', report);+  if (window.ResizeObserver) new ResizeObserver(report).observe(document.documentElement);+  setInterval(report, 1200);+  report();+})();+```++**THE TRAP: no vh units once you auto-resize.** `100vh` inside the iframe means+"the iframe's height", so a viewport-sized section makes scrollHeight grow every+time the parent grows the iframe: an unbounded feedback loop. Give full-bleed+sections a FIXED pixel height in the readme build and let the document flow;+report scrollHeight; done. (Learned live on adom/orbital-lab: the 100vh app+stage chased its own resize until it was pinned at 780px.)++Verify it worked: from the parent page,+`document.querySelector('iframe[src*=readme]').getBoundingClientRect().height`+should read your content height, not 600.+ ## Pitfalls recap  - Edited README.md, page unchanged → shadowing rule; edit readme.html.+- Iframe stuck at ~600px / inner scrollbars -> you never posted readme-height; add the reporter above.+- Iframe grows forever -> a vh-sized section is chasing the resize; pin it to fixed pixels. - Renders but unstyled/white → you assumed wiki CSS; the iframe gets nothing. - Buttons/links dead → sandbox blocks popups/top-nav; keep interactions in-frame. - Fetch to the wiki API fails → no same-origin; the readme is display-only.