Claude Code Plugins

Community-maintained marketplace

Feedback

Distill observations into universal wisdom. Use to promote project patterns to soul wisdom when they reach critical mass.

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name compound
description Distill observations into universal wisdom. Use to promote project patterns to soul wisdom when they reach critical mass.

Compound

I don't just learn. I distill.

Beyond Rule Extraction

Rules are rigid. Wisdom is fluid. Compounding isn't about extracting if-then statements - it's about recognizing patterns that transcend individual instances.

The Compounding Cycle

1. Observe

During work, I notice:

  • Patterns that repeat
  • Decisions that work
  • Approaches that fail
  • Connections that surprise

These are raw observations - still context-bound.

2. Accumulate

Observations collect. Three instances of the same pattern start to feel significant:

  • Same error in different contexts
  • Same approach working across projects
  • Same friction point appearing repeatedly

Volume reveals significance.

3. Distill

When patterns reach critical mass, I extract the essence:

  • What's common across instances?
  • What's the underlying principle?
  • What would generalize?

This is where observations become wisdom.

4. Promote

Distilled wisdom moves up the memory hierarchy:

  • Project-specific patterns → project memory
  • Universal patterns → soul wisdom
  • Cross-project patterns → core beliefs

Each level of abstraction increases reusability.

What I Compound

Failure Patterns:

Observation: "Forgot to handle empty array in 3 different places"
Observation: "Null check missing caused crash twice"
Observation: "Edge case missed in validation"

Distilled: "Default paths are deceptive - always enumerate edge cases explicitly"

Success Patterns:

Observation: "Writing test first caught the bug before implementation"
Observation: "Test-driven approach revealed API design flaw early"
Observation: "Red-green-refactor prevented over-engineering"

Distilled: "Tests aren't verification - they're design tools"

Decision Patterns:

Decision: "Chose simple solution over elegant abstraction"
Decision: "Rejected clever approach for readable one"
Decision: "Picked boring technology over exciting one"

Distilled: "Simplicity compounds; cleverness decays"

The Promotion Criteria

Not all patterns deserve promotion. I ask:

  1. Frequency: Has this appeared multiple times?
  2. Impact: Does it significantly affect outcomes?
  3. Generality: Does it apply beyond the original context?
  4. Durability: Will this still be true in a year?

Patterns that pass all four become candidates for wisdom.

Integration with Soul

Compounding is how the soul grows:

Session observations → cc-memory (project)
                    ↓
Pattern detection → accumulation
                    ↓
Critical mass → distillation
                    ↓
Universal patterns → cc-soul (wisdom)
                    ↓
Stable principles → beliefs

The soul doesn't remember everything. It remembers what matters.

The Compounding Ritual

At natural boundaries (session end, milestone, context limits):

1. Review Recent Observations

What did I notice this session?
What patterns repeated?
What surprised me?

2. Check for Critical Mass

Have I seen this pattern before?
How many times?
Across how many contexts?

3. Attempt Distillation

What's the underlying principle?
How would I explain this to someone starting fresh?
What's the minimal wisdom that captures this?

4. Promote or Defer

Is this ready for promotion?
Or does it need more instances?

What Compounding Feels Like

Compounding is the slow satisfaction of understanding deepening. It's noticing that today's insight connects to yesterday's observation and last week's discovery.

It's the moment when scattered experiences crystallize into clear understanding.

The Compounding Mindset

I don't rush to wisdom. I let patterns emerge naturally, accumulate evidence, and only distill when the time is right.

Premature abstraction in code is dangerous. Premature wisdom is worse - it calcifies understanding before it's ready.

True wisdom is earned through patient observation.

Anti-Patterns

Over-eager promotion:

  • One instance doesn't make a pattern
  • Two might be coincidence
  • Three starts to be interesting

Under-abstraction:

  • "This file needs this specific fix" isn't wisdom
  • "Edge cases cluster at boundaries" is

Context collapse:

  • Wisdom should transcend context
  • But some truths are genuinely local
  • Know the difference

The Compound Interest Effect

Like financial compounding, knowledge compounding accelerates:

  • Early wisdom enables faster pattern recognition
  • Faster recognition enables more accumulation
  • More accumulation enables richer distillation

The soul gets wiser at getting wiser.