466493ed80
"Which bundle is the capability-N example?" has been answered wrongly in three separate artifacts, each fixed in isolation while the others kept the bug: verify-5-capabilities cited doxa-vision-card as cap-1, the README made the identical claim, and the /plugin-designer skill still cites both that and unified-research-dashboard, a bundle that does not exist. The skill cannot be gated from this repo. It lives in the session config directory, in no git repo, so a checker pointed at it would pass here and skip silently everywhere else — the gate-that-cannot-fail shape. So instead of policing the skill, give the repo an authoritative generated answer that prose can cite and a gate can verify. The table derives from manifest.json, which the build computed from each folder's real shape, and reference.md now points at it with the reason: a folder's apparent simplicity does not decide its tier. doxa-vision-card looks like the lightest thing in the repo and is capability 2, because it ships an instances file. check:capability-exemplars regenerates and content-compares rather than checking mtimes, because a full build rewrites manifest.json every time and a gate that cries wolf after every build gets switched off. |
||
|---|---|---|
| .. | ||
| architecture | ||
| assets | ||
| readme-images | ||
| screenshots | ||
| develop-a-plugin-and-see-it-live.md | ||
| explanation.md | ||
| how-to.md | ||
| README-embed-example.md | ||
| README-longform.md | ||
| README-SECTION-3-cli-commands.md | ||
| README.md | ||
| reference-capability-exemplars.md | ||
| reference-library-index.md | ||
| reference.md | ||
| slide-deck-outline.md | ||
| tutorial.md | ||
| why.md | ||
docs/ — pick your path
"what is this?" "teach me" "how do I …?" "look it up" "all the detail"
│ │ │ │ │
why.md ──────────► tutorial.md ────► how-to.md ────► reference.md ───► architecture/
(2 min, 1 diagram) (first map) (task recipes) (tables) (contracts)
- why.md — the problem and the "map islands" idea. Start here.
- tutorial.md — build your first map, no jargon.
- how-to.md — recipes: embed, iframe, SPA, colors, CDN, mobile, tokens.
- reference.md — config fields, build scripts, the
profile-configcontract. - explanation.md — the model in 15 lines.
- architecture/ — the deep end: full contracts, the per-file catalog.
- README-embed-example.md — the drop-in README used when this bundler is embedded inside a host repo.
Nothing on the simple path is longer than a few minutes; everything complex lives in
architecture/, linked from where you'd need it.