Knowledge Compounding (deprecated — use /clavain:compound)
From interknownpx claudepluginhub mistakeknot/interagency-marketplace --plugin interknowThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.
Deprecated: Knowledge entries have been converged into
docs/solutions/. Use/clavain:compoundinstead, which writes todocs/solutions/with enum-validated schema and provenance tracking.
Extract durable patterns from review findings and save them as knowledge entries.
After a flux-drive review completes, or when you discover a reusable pattern worth preserving across sessions.
Preferred: Use /clavain:compound instead — it writes to docs/solutions/ with the converged schema (compound docs format + interknow provenance fields).
Provide either:
For each finding, decide: compound or skip?
Compound (save as knowledge entry) when the finding is:
Skip when:
Write markdown files to ${CLAUDE_PLUGIN_ROOT}/config/knowledge/:
Filename: {short-kebab-case-description}.md
---
lastConfirmed: {today's date YYYY-MM-DD}
provenance: independent
---
{1-3 sentence finding description, phrased as a generalizable heuristic}
Evidence: {file paths, symbol names, line ranges from the review}
Verify: {1-3 concrete steps to confirm this finding is still valid}
If intersense is available, detect the project domain and include it in the finding description. This helps future retrieval prioritize domain-relevant knowledge.
provenance: independentlastConfirmed, set provenance: independentlastConfirmedBefore writing ANY entry:
Good: "Auth middleware often swallows context cancellation errors" Bad: "auth.go:47 in ProjectX has a bug"
After compounding, scan existing entries:
lastConfirmed dateconfig/knowledge/archive/Compounding is best-effort. If it fails, the review/session is still complete.