learn

Save, list, search, prune, and export project learnings in .context/learnings/.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/ckallum/calsuite --skill learn-ckallum
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learn
Source: https://github.com/ckallum/calsuite/tree/main/skills/learn
Command: npx skills add https://github.com/ckallum/calsuite --skill learn-ckallum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill provides a durable, per-project memory of learnings, patterns, pitfalls, and preferences, so Claude can recall important insights across sessions and between teammates.

Core Features & Use Cases

  • Save and organize cross-session learnings in a dedicated per-repo store (.context/learnings/).
  • List, search, and prune learnings to keep memory current and relevant.
  • Export learnings to share or audit, with an INDEX.md index for quick reference.

Quick Start

Run the /learn save command to capture a new learning from this session.

Frequently Asked Questions about learn

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save and organize cross-session learnings for a code project?

You can save and organize cross-session learnings by running the /learn save command, which captures project insights into a dedicated per-repo store under .context/learnings/ for durable recall across sessions.

What is the best way to maintain a durable project memory for code patterns and pitfalls?

Maintaining a durable project memory involves storing patterns and pitfalls in a per-repo memory directory, automatically indexing them in INDEX.md, and allowing you to list, search, and prune entries to keep knowledge current and relevant.

Can I search and prune outdated project notes to keep my repository context relevant?

Yes, you can search and prune outdated project notes directly within the per-repo learning store, ensuring your captured insights remain current and relevant as the codebase evolves across different sessions.

How do I export project learnings to share or audit knowledge across teammates?

You can export project learnings to share or audit knowledge across teammates, utilizing the generated INDEX.md file for quick discovery and reference of stored patterns and preferences.

Does this per-repo memory approach work for capturing knowledge across different code sessions?

Yes, this per-repo memory approach works specifically for capturing knowledge across different code sessions, storing durable learnings locally in the .context/learnings/ directory to preserve insights between teammates and future interactions.