learn

Record, search, and prune per-project learnings in .claude/learnings.jsonl.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you capture recurring project lessons (patterns, pitfalls, preferences, and tooling choices) so your future sessions can reuse what you learned instead of relearning it.

Core Features & Use Cases

  • Record learnings per project: Save typed, confidence-scored notes into .claude/learnings.jsonl for long-term reuse.
  • Search across sessions: Retrieve the most relevant prior learnings by matching a query against saved entries.
  • List and prune knowledge: Review learnings by type and remove low-value or stale entries via a pruned flag.
  • Use Case: After fixing a build/deploy issue, record the pitfall and the workaround; later, search for it to avoid repeating the same failure mode.

Quick Start

Ask your AI assistant to record a learning for your current repo by saying: " /learn Avoid this failure when wiring deployment for compatibility gaps, and use the verified workaround instead."

Frequently Asked Questions about learn

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

FAQPage Schema
How do I save project learnings and pitfalls across coding sessions?

To save project learnings across coding sessions, record typed, confidence-scored notes into a .claude/learnings.jsonl file. This builds a reusable per-repo memory by capturing pitfalls, preferences, and architecture choices for future search and retrieval.

What is the best way to search past coding pitfalls and workarounds in a git repo?

The best way to search past coding pitfalls is using search-by-overlap retrieval against saved JSONL entries. It matches your query against prior typed learnings to return the top relevant workarounds and prevents repeating the same failure modes.

Can I prune stale architecture choices and preferences from my project memory?

Yes, you can prune stale architecture choices and preferences from project memory. The retention model uses a pruned tombstone flag to remove low-value or outdated entries from the JSONL file while preserving the historical record.

Does capturing project memory require a specific file format or scoring system?

Capturing project memory requires the JSONL file format and a confidence scoring system. Typed entries must be saved into .claude/learnings.jsonl to ensure structured, long-term reuse of coding patterns and tooling choices across sessions.

When do I need a per-project knowledge capture system for my development workflow?

You need a per-project knowledge capture system when you repeatedly encounter recurring build or deploy issues. Documenting these pitfalls and verified workarounds allows future coding sessions to reuse solutions instead of relearning the same failures.

Why does my AI assistant keep relearning the same deployment compatibility gaps?

Your assistant keeps relearning deployment compatibility gaps because it lacks a persistent project memory. Recording these pitfalls as typed entries with confidence scores in a JSONL file enables search-by-overlap retrieval to immediately surface past verified workarounds.