skill

Make a Wiki Component Page

Public Made by Adom

by adom

Create a wiki component page the RIGHT way. Pages are keyed manufacturer-mpn and scoped to ONE DATASHEET, so a datasheet covering six voltages and three packages is ONE page covering all of them, never six pages. Two manufacturers publishing the same MPN are two pages, because their limits genuinely differ. Renders through a hand-built readme.html on the Adom theme tokens with a fixed ten-section shape (identity, at a glance, specifications, symbol+footprint viewers, pin map, variants, assets, i

skillwikicomponentdatasheetfamilympnmanufacturerkicadedapublishdedupreadme-htmlprovenance
Overview Files Skills Discover Packages Releases Dependencies Issues1 Breadcrumbs Pull Requests Activity
Make a Wiki Component Page

Install?

Create a wiki component page the RIGHT way. Pages are keyed manufacturer-mpn and scoped to ONE DATASHEET, so a datasheet covering six voltages and three packages is ONE page covering all of them, never six pages. Two manufacturers publishing the same MPN are two pages, because their limits genuinely differ. Renders through a hand-built readme.html on the Adom theme tokens with a fixed ten-section shape (identity, at a glance, specifications, symbol+footprint viewers, pin map, variants, assets, implementation, datasheet, provenance). Anything not available yet gets a 'not available, open a pull request' placeholder rather than being silently dropped. Covers the boundary decision, dedup against existing and legacy bare-MPN pages, pulling CAD from KiCad's official library, the adom-footprint empty-fab-layer workaround, publishing both the registry and page-repo layers, deprecating a page so it actually looks deprecated, and linking into a library.

adom-wiki pkg install adom/adom-component-page

Latest: v2.0.1, published

Dependencies 5 apps, 1 skill

Optional dependencies 1 app

Install is attempted but failures are non-fatal. Useful for nice-to-have integrations that shouldn't block the main package.

Contents

README

markdown

adom-component-page

Create a wiki component page the right way.

The three rules

  1. Slug is <manufacturer>-<mpn>. ams-ams1117, umw-ams1117, microchip-lan7800. A bare MPN cannot express the case where one part number has two manufacturers, two datasheets and two sets of limits.
  2. One page per datasheet. The datasheet draws the family boundary. A datasheet covering six voltages and three packages is one page covering all of them, never six pages. Two manufacturers with two datasheets for the same MPN are two pages.
  3. readme.html is the page. Hand-built, on the Adom theme tokens, following a fixed ten-section shape. README.md is shadowed by it.

What is in here

Path What
SKILL.md The procedure: boundary decision, slug and title, dedup, CAD, the section shape, placeholders, publishing, deprecating, libraries
templates/readme.html The section skeleton with the Adom studio-dark tokens
templates/page.json Manifest skeleton with the component block
scripts/inject_layers.py Fills the fab, silk and courtyard groups that adom-footprint 1.0.20 leaves empty, so component outlines are visible
scripts/build_switcher.py Wraps N footprint embeds into one package switcher
reference/worked-example.md The AMS1117 build end to end, every command in order, including the two places it went wrong first

Anything missing gets a placeholder, not silence

If a file or a fact is not available, the page says so and invites a pull request. A missing row reads as "this part has no Altium library". A placeholder reads as "nobody has contributed one yet", which is true and actionable.

Reference pages

adom/ams-ams1117 and adom/microchip-lan7800 are the standard. Open one before you build.

See SKILL.md for the full procedure.