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

Đang mở
#494 4 bình luận 3 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
5/5
Thời gian dự kiến
Hơn một tuần
Mức phù hợp với người mới
35/100
Loại issue
Tính năng
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Ít trao đổi
Công nghệ
typescript
Lĩnh vực
developer-experience

Hướng nghiên cứu

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.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

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.

Ngôn ngữ chính
TypeScript
Star
25.6k
Fork
2.1k
Merge trung bình
3 giờ 57 phút
Pull request đã merge (30 ngày)
170

Chuẩn bị môi trường

Dự án này không cung cấp dev container, Dockerfile hay hướng dẫn đóng góp, nên bạn cần tự thiết lập môi trường: hãy bắt đầu từ README và xem hướng dẫn đóng góp lần đầu của chúng tôi để biết các bước chung.

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của EveryInc/compound-engineering-plugin

Tất cả issue của EveryInc/compound-engineering-plugin

Issue tương tự

Thêm issue về TypeScript

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.