Adom Wiki Skill Pack

@@ -1,46 +1,87 @@ {-  "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, adompkg, releases, discussions, PRs, discovery), and three repo archetypes have emerged from real use: Page, Skillpack, and Family. One install, 14 skills, plus a write-up of the design patterns for the people who build the wiki.",-  "hero": {-    "type": "image",-    "path": "screenshots/hero.png"+  "version": "0.3.0",+  "type": "skill",+  "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, adompkg, releases, discussions, pull requests, and discovery. One adompkg install drops the whole set onto your container.",+  "discovery_triggers": [+    "publish to the wiki",+    "the wiki",+    "adompkg publish",+    "what kind of wiki repo",+    "wiki repo archetype",+    "publish a chip",+    "chip component page",+    "component readme",+    "molecule page",+    "tape and reel",+    "pin 1 orientation",+    "skillpack",+    "super skill",+    "wiki family repo",+    "parent child wiki",+    "how to make a wiki readme",+    "wiki page presentation",+    "hero in readme",+    "hero shows twice",+    "duplicate hero",+    "don't repeat the hero",+    "hero unlinked",+    "hero disappeared",+    "name a child page",+    "family child title",+    "private source public app",+    "proprietary wiki page",+    "wiki breadcrumb",+    "fork a wiki page",+    "wiki discovery",+    "page not surfacing",+    "discover endpoint",+    "wiki scoring",+    "wiki trending"+  ],+  "dependencies": {+    "john/adom-wiki-hero-image": "^0.2.1"   },-  "visibility": {-    "public": true+  "files": [+    "SKILL.md",+    "README.md",+    "page.json",+    "install.sh",+    "uninstall.sh",+    "screenshots/hero.png",+    "screenshots/archetypes.png",+    "skills/wiki-anatomy/SKILL.md",+    "skills/wiki-api/SKILL.md",+    "skills/wiki-publish-safely/SKILL.md",+    "skills/wiki-readme/SKILL.md",+    "skills/wiki-visibility/SKILL.md",+    "skills/wiki-repo-styles/SKILL.md",+    "skills/wiki-component/SKILL.md",+    "skills/wiki-family/SKILL.md",+    "skills/wiki-skillpack/SKILL.md",+    "skills/wiki-hero/SKILL.md",+    "skills/wiki-breadcrumbs/SKILL.md",+    "skills/wiki-forking/SKILL.md",+    "skills/wiki-discovery/SKILL.md",+    "skills/wiki-scoring/SKILL.md"+  ],+  "scripts": {+    "install": "./install.sh",+    "uninstall": "./uninstall.sh"   },-  "metadata": {-    "tags": [-      "wiki",-      "adompkg",-      "publishing",-      "skillpack",-      "guidelines",-      "documentation",-      "repo-archetypes",-      "open-source",-      "mit"-    ],-    "discovery_triggers": [-      "publish to the wiki",-      "the wiki",-      "adompkg publish",-      "what kind of wiki repo",-      "wiki repo archetype",-      "skillpack",-      "super skill",-      "wiki family repo",-      "parent child wiki",-      "wiki readme",-      "hero disappeared",-      "hero unlinked",-      "private source public app",-      "proprietary wiki page",-      "wiki breadcrumb",-      "fork a wiki page",-      "wiki scoring",-      "wiki trending"-    ]+  "tags": [+    "wiki",+    "adompkg",+    "publishing",+    "skillpack",+    "guidelines",+    "documentation",+    "repo-archetypes",+    "open-source",+    "mit"+  ],+  "author": {+    "name": "John Lauer",+    "email": "[email protected]"   }-}+}\ No newline at end of file

@@ -0,0 +1,257 @@+---+name: wiki-component+description: >-+  How to publish a "component" page to the Adom Wiki — a single chip, a molecule,+  or a PCB that isn't a molecule. `component` is a real wiki page TYPE (peer to+  app/skill). Centerpiece is the CHIP page: a mini-datasheet-plus-CAD-hub with a+  serious tabbed/accordion readme.html (Overview, Symbol, Footprint, 3D, Pin+  mapping, Specifications, Sourcing, CAD downloads, Variants, Related), sourced+  from Adom's own tools (chip-fetcher, ds2sf, adom-symbol/footprint/lbr, chipfit,+  step2glb, chip-thumbnailer). Read this when publishing a chip/molecule/board, or+  designing a component README. Trigger words: publish a component, component page,+  chip page, chip wiki page, publish a chip, component readme, chip readme,+  symbol footprint 3d page, datasheet page, molecule page, pcb component, tape and+  reel, pin 1 orientation, pick and place orientation, kicad altium orcad fusion+  library, parametric specs page, mouser digikey price stock, cad downloads tabs.+---++Parent skill: **adom-wiki-skillpack**++# Publishing a component (chip / molecule / PCB)++`component` is a first-class **wiki page type** (alongside `app` and `skill` — see+**wiki-api**). Structurally a component is usually the **Page** archetype, and chip+families use the **Family** archetype (see **wiki-repo-styles**): e.g. an+`stm32f4` anchor with `stm32f405`, `stm32f407` … children.++Three kinds of component, by what they are:++1. **Chip** — a single part / IC (MCU, MOSFET, sensor, passive, connector). The+   richest case; most of this skill is about it.+2. **Molecule** — a reusable sub-circuit / breakout published via `adom-molecule`+   (a GLB + KiCad PCB + schematic + symbol/footprint JSON).+3. **PCB (non-molecule)** — a finished board that isn't meant to be dropped into+   other designs as a part (a full product PCB, a dev board).++---++# The CHIP component page (the big one)++A chip page is a **mini datasheet + CAD hub + sourcing desk** in one. It is far too+much for a flat README — use a **tabbed / accordion `readme.html`** (see *Layout*+below). The canonical tab set:++> **Overview · Symbol · Footprint · 3D Model · Pin Mapping · Specifications ·+> Sourcing · CAD Downloads · Variants · Related**++## 0. Source every artifact from Adom's tools (don't hand-make these)++| Artifact on the page | Tool | Command → output |+|---|---|---|+| STEP + KiCad sym/mod + Altium IntLib + Fusion .lbr + datasheet PDF + stock | **chip-fetcher** | `chip-fetcher fetch <MPN>` → `library/<MPN>/` (`.step`, `.kicad_sym`, `.kicad_mod`, `.IntLib`, `*-fusion.lbr`, `.pdf`, `stock.json`, `info.json`) |+| Pin list w/ descriptions + symbol/footprint extraction + **per-pin datasheet page citations** | **ds2sf** | `ds2sf extract <chip-dir>` → `*-symbol.extracted.json`, `*-footprint.extracted.json`, `*-extraction.provenance.json` |+| Datasheet → wiki markdown + cropped diagram PNGs | **process-datasheets** / datasheet-parser | `*-wiki-markdown.md`, `*-diagrams/*.png`, `*-metadata.json` |+| Clean schematic symbol (+ interactive SymView) | **adom-symbol** | `.kicad_sym`, `-metadata.json` (pin + group descriptions), `.svg`, `-viewer.html` (SymView) |+| Footprint (+ FpView w/ layer toggle + solder-paste micro-dot preview) | **adom-footprint** | `.kicad_mod`, `-metadata.json`, `.svg`, `-fpview.html` |+| Fusion/EAGLE library | **adom-lbr** | `adom-lbr generate --sym <f>.kicad_sym` → `.lbr` |+| 3D: STEP → web GLB | **step2glb** | `step2glb convert <f>.step` → `.glb` (+ stats JSON) |+| Pin-1 alignment + seat-plane check + **pin-1-baked GLB** + composite | **adom-chipfit** | `adom-chipfit bake --footprint <f>.kicad_mod --glb <f>.glb` → `*-3d-pin1.glb`, `*-chipfit-composite.glb` |+| Symbol/footprint SVGs + 3D iso PNGs (160/320/800) + manifest | **chip-thumbnailer** | `chip-thumbnailer once <MPN>` → `*-symbol.svg`, `*-footprint.svg`, `*-3d-iso{,-sm,-lg}.png`, `*-thumbs.json` |++Push all the **source files** to the git repo (so the Files tab is a real CAD+library) and the **thumbnails/SVGs/GLB** for the README to render against. Follow+the publish workflow + the hero rule in **wiki-api** / **wiki-publish-safely** /+**wiki-hero**.++## 1. The tabs, and what goes in each++**Overview** — MPN, manufacturer, one-line description, **lifecycle badge**+(Active / NRND / Obsolete / Last-Time-Buy), package, pin count, operating voltage,+datasheet link. A 3D iso thumbnail (`*-3d-iso.png`). (The page *header* hero shows+separately — never re-embed it, see **wiki-hero**.)++**Symbol** — the symbol SVG (`*-symbol.svg`, dark Adom theme) inline; pin/group+overview; a **deep link** to the interactive SymView for tooltips/zoom. Note which+tool/standard generated it.++**Footprint / Land Pattern** — the footprint SVG (`*-footprint.svg`) inline, with:+- the **pin-1 marker** clearly shown (square pad / silk dot — see *Pin-1* below);+- a **solder-paste aperture preview** — the paste layer rendered as apertures /+  micro-dot fill, with **leaded vs lead-free** options, so the community can flag+  where the default paste pattern risks **solder bridging** or starved joints (use+  the page's **Discussions** for this feedback loop);+- courtyard + IPC land-pattern reference.++**3D Model** — a web preview of the **GLB** (the pin-1-baked GLB from chipfit is+ideal); the **chipfit validation** snapshot (pin-1 pad, seat-plane Δz, size-match);+STEP + WRL downloads. The 3D model's pin-1 corner MUST agree with the footprint and+the placement zero orientation (see *Pin-1*).++**Pin Mapping** — the **pin list with descriptions** (from ds2sf / adom-symbol+`-metadata.json`: per-pin function + alt-functions, grouped by POWER/IO/…), and the+symbol-pin ↔ footprint-pad correspondence. Cite the **datasheet page** per pin where+available (ds2sf provenance).++**Specifications** — **class-aware** parametric set; render the field block that+fits the part:+- **MCU**: core, core size (8/16/32-bit), max clock, flash, RAM, GPIO count,+  peripherals (UART/SPI/I²C/ADC/PWM/DMA/timers), connectivity, V-supply, temp,+  package.+- **MOSFET**: channel (N/P), Vds, Id (@Ta), Rds(on) max (@Id,Vgs), Vgs(th),+  gate charge Qg, Ciss, power dissipation, package.+- **Passive (R/L/C)**: value, tolerance, V-rated, power/current, dielectric/temp-co+  (C0G/X7R…), EIA size (0402/0603/0805…), temp.+- **Op-amp / analog**: channels, GBW, slew rate, Vos, Ib, V-supply (single/±),+  output type (RRO), temp.++**Sourcing** — price-break table (qty 1/10/100/1k…), stock/availability, lifecycle,+**RoHS / lead-free**, **MSL** (moisture sensitivity level 1–6 + floor life),+**tape & reel** (see below), and **buy links to Mouser and DigiKey** (one each).+Pull live numbers from `stock.json` (chip-fetcher) where present, and date them.++**CAD Downloads** — a **per-tool row** so any EDA user is covered:+| Tool | Files |+|---|---|+| KiCad | `.kicad_sym` + `.pretty/.kicad_mod` + STEP + WRL |+| Fusion 360 / EAGLE | `.lbr` (symbol+package+device) + STEP |+| Altium | `.IntLib` (compiled from `.SchLib` + `.PcbLib`, 3D body embedded) |+| OrCAD / Allegro | Capture `.olb` + `.dra`/`.psm` + `.pad` padstack |+| Universal | **STEP** (.step) + **GLB** (web/3D) + datasheet PDF |++**Variants** — symbol variants, footprint variants (e.g. nominal vs hand-solder+vs paste-tuned), and **3D / package variants** (same die, different package), each+with its own download. Disambiguate by body size where packages collide.++**Related** — links to **molecules that use this chip** (query `adom-molecules`),+**family** siblings (other packages/speed grades — the Family anchor; see+**wiki-family**), and alternates / second sources.++## 2. Tape & reel + pick-and-place orientation (don't skip)++- **Packaging**: Cut Tape (CT), Tape & Reel (T&R), Tube, Tray, Bulk; state the+  **reel quantity** and that custom-cut reels exist (Digi-Reel / MouseReel).+- **EIA-481 carrier tape**: pocket position is referenced to the **sprocket holes**+  (feed pitch 4.0 mm), not the tape edge. Convention puts **pin 1 in Quadrant 1+  (top-left)** with sprocket holes along the top, feeding from the right — **but the+  authoritative orientation is the manufacturer's tape-and-reel drawing**, never an+  assumption. Show the orientation so P&P programmers get rotation right.+- **MSL**: 1 (unlimited) → 6 (bake-before-use); state floor life so assemblers+  handle reflow correctly.++## 3. Pin-1 orientation — the rule that makes placement correct++The footprint pin-1, the 3D model pin-1 corner, and the placement **zero+orientation** must all agree, or the part lands rotated 90°/180° even though every+file "looks right."++- **IPC-7351 zero orientation**: ICs → **pin 1 top-left**; two-terminal polarized+  parts → **pin 1 (+) on the LEFT** at 0°; positive rotation = CCW. ⚠️ **IEC 61188-7+  uses pin-1 bottom-left** — call out which convention a library follows.+- **Markers**: SOIC dot/notch; QFP/QFN chamfer/dot; BGA = A1 corner; footprint+  pin-1 = **square pad** + silk dot. Polarity gotcha: SMD **tantalum** stripe = **+**,+  SMD **aluminum electrolytic** stripe = **−**.+- **adom-chipfit** validates this (pin-1 pad vs baked pin-1 dot, seat-plane Δz) and+  bakes a pin-1-marked GLB — use its output and show its verdict on the 3D tab.++## 4. Layout — a tabbed / accordion `readme.html`++This much content needs structure, not a wall of markdown. Use a **custom+`readme.html`** (see **wiki-readme**) with **CSS-only tabs (`:checked` radios)** or+**`<details>` accordions** — both work **without JavaScript**, which matters because+the readme.html sandbox is restrictive. Skeleton (accordion form, no JS, dark/brand):++```html+<style>+  .c-tab{border:1px solid #20303a;border-radius:10px;margin:10px 0;background:#0e141c}+  .c-tab>summary{cursor:pointer;padding:14px 16px;font-weight:700;color:#e6edf3;list-style:none}+  .c-tab[open]>summary{border-bottom:1px solid #20303a;color:#00e6dc}+  .c-body{padding:14px 16px;color:#aeb8c4}+  .badge{display:inline-block;padding:2px 10px;border-radius:999px;border:1px solid #2b6;color:#7fe3dd;font-size:12px}+  table{width:100%;border-collapse:collapse} td,th{border-top:1px solid #1d2832;padding:6px 8px;text-align:left}+</style>+<h1>RP2040 <span class="badge">Active</span></h1>+<p>Raspberry Pi · dual-core Cortex-M0+ · QFN-56 7×7mm · <a href="...">datasheet</a></p>++<details class="c-tab" open><summary>Overview</summary><div class="c-body">+  <img src="/blob/component/rp2040/screenshots/rp2040-3d-iso.png" width="320">+  …quick specs…+</div></details>++<details class="c-tab"><summary>Symbol</summary><div class="c-body">+  <img src="/blob/component/rp2040/rp2040-symbol.svg" width="100%">+  <p><a href="…SymView…">Open interactive symbol viewer →</a></p>+</div></details>++<details class="c-tab"><summary>Footprint &amp; solder paste</summary><div class="c-body">+  <img src="/blob/component/rp2040/rp2040-footprint.svg" width="100%">+  <p>Pin-1 = square pad (top-left). Paste: <b>lead-free micro-dot</b> default —+     report bridging in <a href="…discussions…">Discussions</a>.</p>+</div></details>++<details class="c-tab"><summary>3D model</summary><div class="c-body">+  <img src="/blob/component/rp2040/rp2040-3d-iso-lg.png" width="100%">+  <p>chipfit: pin-1 ✓, seat-plane Δz ≈ 0. <a href="…">STEP</a> · <a href="…">GLB</a> · <a href="…">WRL</a></p>+</div></details>++<!-- Pin Mapping · Specifications · Sourcing · CAD Downloads · Variants · Related: same pattern -->+```++Use `<img>` of the **static** SVG/PNG thumbnails (they render in the README) and a+**deep link** to the live interactive viewer for each.++### Live-embedded editors — the goal vs. today++The aspiration is to **embed adom-symbol / adom-footprint / adom-lbr live** in the+page so a user can tweak the symbol/footprint or generate a library on the fly.+**This does not work in the readme.html sandbox today**: the sandbox CSP is+`connect-src 'none'` and `/blob` serves assets as `application/octet-stream` ++`nosniff`, so an embedded viewer can't `fetch()` its model/data and an `<iframe>`+of a repo `.html` force-downloads on mobile. **So today: ship static SVG/PNG/GLB+previews inline + deep-link the interactive tools** (SymView `:8781`, FpView+`:8782`, `adom-step`, `adom-chipfit`). Track the live-embed as a platform ask+(below); revisit when the sandbox allows same-origin fetch / proper content-types.++---++# Molecule component pages++A molecule is published via **adom-molecule** (`create --source kicad|fusion …`),+producing a GLB + KiCad PCB + schematic + symbol/footprint JSON, addressed by SKU+`owner/name/version`. The page should show: the 3D GLB preview, the schematic,+the **pin map** (`adom-pin-mapping` → `MoleculePinMapping.md`: IC pin → net → silk+label → alt-functions), the BOM, and **Related** (the chips it's built from — link+back to their chip component pages, and they link forward to it).++# PCB (non-molecule) component pages++A finished board not meant to be reused as a part. Lighter than a chip: Overview ++3D/photos + schematic/board downloads + BOM + assembly notes (tape&reel of its+parts is the assembler's concern, not the board's). Use the Page archetype.++---++# Publishing++Publish as **`type: "component"`** via the standard flow (**wiki-api**): create the+page, push all source files (text plain, binaries base64, UA header), `adompkg+publish`, then push a **complete `page.json` LAST** (hero linked — **wiki-hero**),+and **verify in pup** (**wiki-publish-safely**). For chip families, follow the+Family naming/title rules (**wiki-family**).++## 📋 TODO — what component pages still need (for Colby)++- **Live-embeddable editors in readme.html**: allow same-origin `fetch()` (loosen+  the readme CSP) and serve repo assets with real content-types (not octet-stream+  + nosniff) so adom-symbol / adom-footprint / a GLB viewer can run *inside* the+  page — the on-the-fly tweak/generate experience. (Same gap logged for the+  interactive-readme feature.)+- **A `component` page sub-type / template** so the wiki knows a page is a chip vs+  molecule vs board and can render the right tab scaffold + class-aware spec fields.+- **Per-class spec schema** (MCU/MOSFET/passive/op-amp) the page can fill from a+  structured source instead of hand-tables.+- **Live price/stock** widgets (Mouser/DigiKey) rather than dated `stock.json`+  snapshots.+- **A "molecules using this chip" backlink index** so Related populates itself.++> ⏳ Update this skill's "today" constraints once the readme sandbox + content-types+> are fixed and component sub-types ship. Re-verify before claiming live embeds work.