Feature: Cross-project knowledge sharing for docs/solutions/

Aperta
#494 4 commenti 3 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
typescript

Direzione di ricerca

Start by reading the learnings-researcher entry point and the ce:compound pipeline that creates and searches docs/solutions/. Compare the proposed configurable paths, import/export, and global directory approaches, then identify how external results should be tagged and adapted. Done means cross-project solutions are discoverable through a defined approach; the issue does not specify files or tests.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

The ce:compound → docs/solutions/ → learnings-researcher → ce:plan/ce:review pipeline builds a valuable knowledge store per repo. But learnings from one project are invisible when working in another project. The learnings-researcher only searches the current repo's docs/solutions/.

For users who work across multiple related projects (e.g., multiple Obsidian vaults with similar agent/skill workflows, a main app + supporting repos, or a monorepo user who splits into multiple repos), lessons learned in one project should be discoverable in the others.

Use Case

I maintain multiple Obsidian vaults with Claude Code skills. Over 40+ documented solutions in one vault cover patterns like:

  • Agent/skill design (gate language, delegation, compliance)
  • MCP integration patterns (KanBox, Slack, email)
  • Token optimization (CLI bypass, subagent delegation, batch pre-computation)
  • Enrichment workflow patterns

When I start a new vault or work in a different codebase with similar patterns, none of these learnings are discoverable. The learnings-researcher searches only the local docs/solutions/, finds nothing, and the agent starts from scratch.

Current Workarounds

Approach Limitation
Symlink docs/solutions/ from another repo learnings-researcher only searches docs/solutions/, not docs/shared-solutions/ or other paths
Copy files on project init Snapshot in time — diverges immediately, no sync
User-level ~/.claude/CLAUDE.md with path hint Fragile — depends on agent choosing to read an external path
Symlinked .claude/rules/ Rules are loaded into every conversation (context cost), no structured search via frontmatter

None of these integrate with the compound pipeline — the learnings-researcher doesn't know to look outside docs/solutions/.

Suggested Approaches

Option A: Configurable solutions_paths (lightweight)

Allow AGENTS.md (or CLAUDE.md) to declare additional solution directories the learnings-researcher should search:

# In AGENTS.md or a plugin config
solutions_paths:
  - docs/solutions/           # local (default)
  - ~/src/other-project/docs/solutions/  # cross-project

The learnings-researcher searches all listed paths. Results from external paths are tagged with their source so the agent knows they may need adaptation.

Option B: ce:compound-export / ce:compound-import (curated)
  • ce:compound-export — Curate a subset of docs/solutions/ into a portable bundle (strip repo-specific file paths, keep patterns and guidance)
  • ce:compound-import — Import a bundle into a new project's docs/solutions/, adapting references to the local codebase

This is more work but produces cleaner cross-project docs since repo-specific details (file paths, component names) are adapted.

Option C: Global solutions directory (simple)

Support a user-level ~/docs/solutions/ (or configurable path) that the learnings-researcher always searches in addition to the local docs/solutions/. Users manually symlink or copy their most portable learnings there.

Related Issues

  • #111 — Project scaffolding for docs/solutions/ (same theme: bootstrapping the knowledge store)
  • #171 — Closed-loop self-improvement (proposed knowledge seeding, but repo-local)

Impact

Without cross-project sharing, the compound philosophy ("each unit of work makes subsequent units easier") resets to zero at project boundaries. The first project compounds knowledge beautifully; the second project starts from scratch even when the same user has already solved similar problems.

Lingua principale
TypeScript
Stelle
25.6k
Fork
2.1k
Merge medio
3h 57m
PR unite (30g)
170

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di EveryInc/compound-engineering-plugin

Tutte le issue di EveryInc/compound-engineering-plugin

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.