npx claudepluginhub zhizdev/overgrow --plugin overgrowThis skill is limited to using the following tools:
This skill turns a flat set of pages into a **semantic graph** organized around pillars. It maps every page to its pillar(s), builds the hub-and-spoke links that should exist (pillar ↔ supporting pages, supporting ↔ supporting where topically adjacent), and proposes the insertions needed to close the gaps.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Processes PDFs: extracts text/tables/images, merges/splits/rotates pages, adds watermarks, creates/fills forms, encrypts/decrypts, OCRs scans. Activates on PDF mentions or output requests.
Share bugs, ideas, or general feedback.
This skill turns a flat set of pages into a semantic graph organized around pillars. It maps every page to its pillar(s), builds the hub-and-spoke links that should exist (pillar ↔ supporting pages, supporting ↔ supporting where topically adjacent), and proposes the insertions needed to close the gaps.
.overgrow/inventory.md. If missing, run init first..overgrow/audit.md if present — orphan and dead-end flags are the primary targets.$ARGUMENTS: if a pillar name is given, scope to it. Otherwise run across all pillars.Before mapping, read from the plugin's knowledge/ directory:
knowledge/geo.md — authority, topical clusters, and internal-link sections. The hub-and-spoke / pillar-cluster pattern and anchor-text rules live here.knowledge/pages.md — H-tag and content-structure rules that the link anchors should align with.If those files are not reachable, fall back to the summary below but prefer the reference.
spawn-pages (for solutions/feature pillars) or spawn-blogs (for topic pillars with a "what is X" hub)..overgrow/inventory.md. If a target page is missing, flag it as a spawn-pages or spawn-blogs candidate instead of emitting a broken link.Write .overgrow/internal-links.md:
# Overgrow — Internal Link Plan
_Run: <YYYY-MM-DD>_
_Scope: <all | pillar>_
## Pillar map
### <Pillar>
- Hub: <route> — <source path>
- Supporting:
- <route> — <source path>
- ...
## Proposed insertions
### <Source route> (<source path>)
- **Insert:** link to `<target route>` with anchor `"<anchor text>"` — near `"<excerpt from source that identifies the insertion point>"`
- Reason: <e.g. "supporting → pillar hub; currently orphan from pillar">
- ...
## Orphan pages after plan
<routes that will still have < 2 inbound content links even after insertions — candidates for new supporting content or reconsideration of placement>
## Missing targets
<list of would-be link targets that do not exist yet — feed these into `spawn-pages` or `spawn-blogs`>
If the user explicitly asks to apply the insertions, make the edits directly in the source files. Otherwise leave them as a plan and let the user review.
.md/.mdx, JSX anchor or <Link> for React routes, etc.). Match the framework's idiom.spawn-pages or spawn-blogs.