From db1ce43ee118bf3f712e3a9bf33ffef83f32a98f Mon Sep 17 00:00:00 2001 From: admin Date: Sat, 30 May 2026 10:30:25 +0100 Subject: [PATCH] Align sp skill traversal paths with relocated docs tree The Architecture index row and the four-tier traversal described navigation via packages/ (genesis-monorepo naming). Point them at the actual ${CLAUDE_PLUGIN_ROOT}/docs/ tree with relative child links, keeping the accurate note that the tree mirrors the monorepo packages/. Co-Authored-By: Claude Opus 4.8 (1M context) --- plugins/document-navigator/skills/sp/SKILL.md | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/plugins/document-navigator/skills/sp/SKILL.md b/plugins/document-navigator/skills/sp/SKILL.md index 2d7b1d7..7b3a663 100644 --- a/plugins/document-navigator/skills/sp/SKILL.md +++ b/plugins/document-navigator/skills/sp/SKILL.md @@ -12,7 +12,7 @@ Match natural-language intent to `@suaveplan/*` packages and extract working cod | Layer | Source | |-------|--------| | User intent | Natural language via `/sp` or direct invocation | -| Package index | `packages/README.md` → category READMEs → subcategory READMEs → package READMEs | +| Package index | `${CLAUDE_PLUGIN_ROOT}/docs/README.md` → category READMEs → subcategory READMEs → package READMEs | | Docs tree | `${CLAUDE_PLUGIN_ROOT}/docs/` (`.md`-only mirror of `packages/`, maintained externally) | | Examples | Linked `.md` files inside each package (`src/**/*.md`) | @@ -47,22 +47,22 @@ grep -ri "twilio" ${CLAUDE_PLUGIN_ROOT}/docs/ ### Traversing the hierarchy -The documentation is a four-tier chain. Each tier summarizes its children and links to their READMEs: +The documentation is a four-tier chain rooted at `${CLAUDE_PLUGIN_ROOT}/docs/`. Each tier summarizes its children and links to their READMEs (links inside the tree are relative, e.g. `.//README.md`): -1. **Root index** — `packages/README.md` +1. **Root index** — `${CLAUDE_PLUGIN_ROOT}/docs/README.md` - Lists every category with a one-line summary. - - Links to each `packages//README.md`. + - Links to each `/README.md`. -2. **Category index** — `packages//README.md` +2. **Category index** — `/README.md` - Lists every subcategory with a one-line summary. - - Links to each `packages///README.md`. + - Links to each `//README.md`. -3. **Subcategory index** — `packages///README.md` +3. **Subcategory index** — `//README.md` - Contains a table of every package in that subcategory. - - Each row has the package name, a one-line description, and a link to `packages////README.md`. + - Each row has the package name, a one-line description, and a link to `///README.md`. - Read this to identify candidate packages before drilling deeper. -4. **Package README** — `packages////README.md` +4. **Package README** — `///README.md` - Full description, install command (`bun add @suaveplan/`), and quick-start code block. - Contains a **documentation tree** that links to every module-level `.md` file inside `src/`. - Follow those links to find API usage patterns and typed examples. @@ -73,7 +73,7 @@ Module `.md` files (e.g., `src/analysis/analysis-op.md`) contain API usage patte ## Constraints -- Only reference packages that exist nested within `packages/`. Do not invent package names. +- Only reference packages that exist under `${CLAUDE_PLUGIN_ROOT}/docs/`. Do not invent package names. - Use exact `@suaveplan/` identifiers from `package.json`. - Extract code examples verbatim from `.md` files; do not fabricate import paths. - Assume the docs tree is current; do not concern yourself with how it is maintained.