Adom Wiki Skill Pack
Public Made by Adomby adom
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.
name: wiki-breadcrumbs description: >- 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.
Parent skill: adom-wiki-skillpack
Breadcrumbs: third-party "a path leads here" links
Status: Implemented (basic). GET /api/v1/pages/:slug/breadcrumbs is live and
returns a breadcrumb list ({"breadcrumbs":[]} on a page with none). The attach
write-path and UI are still settling, confirm the exact POST schema with the wiki
team before relying on automated attachment, and don't claim it works without
reading the API response.
The idea (Hansel & Gretel)
A breadcrumb is a small link a third party drops on someone else's page to mark a trail to a related thing they built, without needing edit rights on that page. The metaphor is the fairy tale: drop breadcrumbs through the forest so a path can be followed.
The motivating case: someone builds a new OrCAD bridge for adom-desktop.
They don't own adom-desktop and shouldn't edit it, but adom-desktop (and its
users, and the AI) should be able to discover that a new add-on bridge exists. So
they drop a breadcrumb on adom-desktop pointing at their bridge page. Now the
anchor surfaces "add-ons that lead here," and the trail is followable both ways.
How it fits the archetypes
Breadcrumbs are the discovery glue for the Family archetype (see wiki-family), especially when children are owned by third parties:
- A Family child announces itself to its anchor with a breadcrumb (in addition to
the
<parent>-pluginfamily tag and the anchor's registry table). - This is what lets a family grow without the anchor's owner doing anything , the third party drops the breadcrumb; the anchor lists it.
Reading breadcrumbs
curl -s -H "User-Agent: `adom-wiki pkg`/2.1.0" \
"https://wiki.adom.inc/api/v1/pages/<anchor-slug>/breadcrumbs"
# → {"breadcrumbs":[ ... ]}
Attaching a breadcrumb
The intended author flow: from your add-on's page, attach a breadcrumb targeting
the anchor page with a short label and your page's slug, so it appears in the
anchor's breadcrumb list. Verify the current POST endpoint/schema with the wiki
team (Colby) before automating, this skill documents the model; the exact
write contract is still firming up. Until then, treat breadcrumb attachment as a
manual/confirmed step and always read back the anchor's breadcrumbs to confirm.
---
name: wiki-breadcrumbs
description: >-
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.
---
Parent skill: **adom-wiki-skillpack**
# Breadcrumbs: third-party "a path leads here" links
**Status: Implemented (basic).** `GET /api/v1/pages/:slug/breadcrumbs` is live and
returns a breadcrumb list (`{"breadcrumbs":[]}` on a page with none). The attach
write-path and UI are still settling, confirm the exact POST schema with the wiki
team before relying on automated attachment, and don't claim it works without
reading the API response.
## The idea (Hansel & Gretel)
A **breadcrumb** is a small link a third party drops *on someone else's page* to
mark a trail to a related thing they built, without needing edit rights on that
page. The metaphor is the fairy tale: drop breadcrumbs through the forest so a
path can be followed.
The motivating case: someone builds a **new OrCAD bridge** for `adom-desktop`.
They don't own `adom-desktop` and shouldn't edit it, but `adom-desktop` (and its
users, and the AI) should be able to discover that a new add-on bridge exists. So
they drop a breadcrumb on `adom-desktop` pointing at their bridge page. Now the
anchor surfaces "add-ons that lead here," and the trail is followable both ways.
## How it fits the archetypes
Breadcrumbs are the discovery glue for the **Family** archetype (see
**wiki-family**), especially when children are owned by third parties:
- A Family child announces itself to its anchor with a breadcrumb (in addition to
the `<parent>-plugin` family tag and the anchor's registry table).
- This is what lets a family grow *without* the anchor's owner doing anything ,
the third party drops the breadcrumb; the anchor lists it.
## Reading breadcrumbs
```bash
curl -s -H "User-Agent: `adom-wiki pkg`/2.1.0" \
"https://wiki.adom.inc/api/v1/pages/<anchor-slug>/breadcrumbs"
# → {"breadcrumbs":[ ... ]}
```
## Attaching a breadcrumb
The intended author flow: from your add-on's page, attach a breadcrumb targeting
the anchor page with a short label and your page's slug, so it appears in the
anchor's breadcrumb list. **Verify the current POST endpoint/schema with the wiki
team** (Colby) before automating, this skill documents the model; the exact
write contract is still firming up. Until then, treat breadcrumb attachment as a
manual/confirmed step and always read back the anchor's `breadcrumbs` to confirm.