Adom Wiki Skill Pack

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 + adompkg package manager + release database + discussion forum + pull requests + discovery), and three repo archetypes have emerged from real use: Page, Skillpack, and Family. This pack routes to 15 focused sub-skills and carries the hard rules that keep pages from breaking. Trigger words: 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, adompkg publish, publish a chip, component page, chip page, molecule page, tape and reel, pin 1 orientation.

The mental model of the Adom Wiki (wiki.adom.inc): it is five familiar tools fused into one product keyed off a single slug per page — a git host, the adompkg package manager, a release database, a discussion forum, pull requests, and discovery — plus a presentation layer. Read this to understand WHAT the wiki is before learning HOW to drive it. Trigger words: what is the adom wiki, how does the wiki work, wiki architecture, wiki mental model, git plus npm plus releases, wiki page is a repo, two storage layers, why both git and registry, wiki anatomy, explain the wiki, six tools in one.

How to drive the Adom Wiki (wiki.adom.inc) programmatically: the adompkg CLI, the REST API (/api/v1/...), authentication, and the publish workflow that writes BOTH storage layers (git repo + package registry). Read this before any create-page, push-files, or publish call. Trigger words: wiki api, adompkg, adompkg publish, adompkg install, POST pages, push files to wiki, wiki rest api, publish to the wiki, create wiki page, commit to wiki repo, wiki bearer token, adompkg login, two storage layers, wiki tarball.

The breadcrumb system on the Adom Wiki — how a third party attaches a small "trail marker" link to someone else's page to announce a related thing they built ("I made a new OrCAD bridge, so adom-desktop should know an add-on exists"), without editing that page. Like Hansel & Gretel dropping breadcrumbs so a path can be followed back. Read this when an add-on/plugin/bridge for an existing page needs to be discoverable from it. Trigger words: wiki breadcrumb, attach a breadcrumb, announce an add-on, third party plugin link, new bridge for adom-desktop, link my page to another, trail marker, discover add-ons, breadcrumb api.

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) with NATIVE rendering: set a `component` block in page.json + push the CAD files and the wiki auto-renders interactive symbol + footprint + 3D viewers, a downloads grid, and a datasheet section. The chip page is the rich case: a mini-datasheet-plus-CAD-hub built from Adom's own tools (chip-fetcher, ds2sf, adom-symbol/footprint/lbr, step2glb, chipfit, chip-thumbnailer), with PROVENANCE on every datapoint and an Open-in toolbar. Read before publishing any chip/molecule/board. Trigger words: publish a component, component page, chip page, publish a chip, component readme, symbol footprint 3d page, datasheet page, 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.

Discovery on the Adom Wiki — a FIRST-CLASS component of the wiki, peer to git, adompkg, releases, discussions, and pull requests. How pages/skills get FOUND: the two layers (local installed-skill matching vs the registry /discover + search endpoints), how to make a page discoverable (manifest + page discovery_triggers), the current real state of what works and what doesn't, and the TODO list of what discovery still needs. Read this when a page won't surface, when setting discovery triggers, or when reasoning about how the AI finds the right skill. Trigger words: wiki discovery, discover endpoint, discovery_triggers, page not surfacing, skill not found, how does the AI find skills, wiki search, make a page discoverable, trigger words, /discover, registry discovery, why isn't my page showing up.

How to build a Family-style wiki repo on the Adom Wiki — an anchor page plus children published as their own pages, joined by a naming convention, a family tag, and breadcrumbs (e.g. adom-usb + adom-usb-sniffer-cdc, adom-desktop + bridges). Use this when a hub has parts that need their own owners or release cadence, or when adding a child/plugin to an existing family. Trigger words: wiki family repo, parent child wiki page, add a plugin to the family, anchor page, family tag, name a child page, adom-usb plugin, adom-desktop bridge, publish a child page, family naming convention, register a child.

Forking and community contribution on the Adom Wiki — how someone who doesn't own a page proposes changes to it. Pull requests are live (propose edits to a page's repo, the owner reviews and merges); a dedicated fork button is planned. Read this when contributing to a wiki repo you don't own, or planning the community-contribution path for a repo you do. Trigger words: fork a wiki page, fork wiki repo, contribute to a wiki page, propose changes wiki, wiki pull request, wiki PR, community update wiki, submit a change to someone's page, review a wiki PR, accept community changes.

The hero image for an Adom Wiki page — how to generate one (via the adom-wiki-hero-image package, a dependency of this pack) and, critically, how to stop it from getting unlinked. adompkg publish overwrites the repo's page.json (which has no hero), so the page-header hero is dropped on every publish unless you re-push a complete page.json LAST. Read this when adding a hero, or when a hero that used to show is suddenly gone. The hero lives in page.json ONLY — never embed it in the README body (that shows the human the same image twice). Trigger words: wiki hero, hero image, hero disappeared, hero unlinked, hero gone after publish, page shows placeholder icon, generate a hero, billboard image, adom-wiki-hero-image, re-link hero, hero_path empty, hero shows twice, duplicate hero, hero in readme, embed hero in readme.

The hard rules and operational pitfalls for editing Adom Wiki pages (wiki.adom.inc) without breaking them — write both storage layers, never base64 a text file, versions are immutable, soft-delete blocks re-creation, the hero gets clobbered on publish, rate limits, and the non-negotiable verify-in-pup step. Read this before AND after any publish, file push, README change, or metadata edit. Trigger words: wiki publish broke the page, page shows placeholder, readme is gibberish, files tab empty, hero disappeared, hero unlinked, UNIQUE constraint pages, immutable version, adompkg 429, ghost page, verify wiki in pup, wiki publish checklist, don't break the wiki page.

How to build a custom HTML readme (readme.html) for an Adom Wiki page — the fully designed, unsanitized alternative to README.md. Covers when to choose html over markdown, the shadowing rule (readme.html makes README.md invisible on the page), the sandboxed-iframe render pipeline and its exact limits (scripts run, but no same-origin, no cookies, no wiki API, external links and popups need care), self-containment (inline CSS/JS, base64 fonts/images, /blob/ asset URLs), the six readme variant slots (bare/public/private × html/md), dark-theme styling so the page doesn't flash white, and the curl + pup verification loop. Read this BEFORE writing a readme.html and when one renders blank, unstyled, clipped, or won't update. Trigger words: html readme, readme.html, custom readme, custom html readme, designed readme, readme with tabs, readme with accordion, readme iframe, readme sandbox, readme shadowed, README_SHADOWED, readme.html not rendering, readme not updating, fully custom page layout, custom page body, unsanitized readme.

How to make a great Adom Wiki page presentation — the README is the page. Covers the choice between a plain README.md and a fully custom readme.html, the mandatory sections every page needs, embedding live demos / videos / iframes, and referencing inline images from the repo. Read this when writing or fixing the Overview tab of a wiki page, and BEFORE adding any image to a README — NEVER embed the page hero in the README body (the page header already shows it, so embedding it makes the human see the same image twice). Trigger words: how to make a readme, wiki readme, readme.html, custom readme, write a readme for the wiki, wiki page overview, embed iframe wiki, embed demo, inline images readme, wiki page presentation, mandatory readme sections, readme renders blank, hero in readme, embed hero, hero image in readme, hero in the body, hero shows twice, duplicate hero, repeated hero, don't repeat the hero, readme hero image, add image to readme, readme screenshots.

The taxonomy of Adom Wiki repo archetypes that have emerged from real use, and how to choose between them BEFORE you publish: Page (open- or closed-source), Skillpack (one repo, many bundled sub-skills, suffix -skillpack), and Family (an anchor page plus separately-published children). Read this when starting any new wiki repo or deciding how to structure related pages. Trigger words: what kind of wiki repo, wiki repo archetype, wiki repo style, page vs skillpack vs family, parent child wiki, super skill repo, bundle skills or separate, how to structure a wiki repo, skillpack vs family, one repo or many, chip-fetcher structure.

The scoring / trending system on the Adom Wiki — the signals tracked to know whether a page is doing well (stars / high-fives, install counts, and a trending surface) and how an author legitimately earns them (great hero, strong README, working demo). Stars are live; install counts, high-fives, and a dedicated trending endpoint are still being surfaced. Read this when asked how a page is performing or how to make one trend. Trigger words: wiki scoring, wiki trending, high five, star a page, install count, is my page trending, page popularity, wiki metrics, how to trend, what's popular on the wiki, page score.

How to build a Skillpack — one Adom Wiki repo that bundles a main skill plus many sub-skills, installed together by a single adompkg install, with the slug suffix -skillpack so the class is recognizable. Covers the bundle layout (root SKILL.md + skills/<sub>/SKILL.md), an install.sh that lists every skill, the package.json files[] whitelist, frontmatter conventions, and the skill-map table. Read BEFORE creating a new skill set so you never make a repo per skill. Trigger words: make a skillpack, super skill, bundle skills, one repo many skills, skill bundle, do not make a repo per skill, skillpack suffix, author a skill set, SKILL.md bundle, install.sh skills, wiki skill package.

How visibility and licensing work on the Adom Wiki (wiki.adom.inc): a page can keep its git source PRIVATE while its releases / adompkg package stay PUBLIC, so people install the compiled app but can't read the code — the pattern for proprietary apps. Covers public vs private source, the private readme, and the open-source vs closed-source Page variants. Read this when deciding how much of a page to expose, or shipping a proprietary tool. Trigger words: private wiki source, public app private source, proprietary wiki page, closed source app, private readme, hide source code wiki, install compiled app no source, open source wiki repo, license a wiki repo, visibility settings wiki, who can see my source.