learn

Document learnings, gotchas, and decisions into CLAUDE.md with structured entries.

21|6|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/mintuz/claude-plugins --skill learn-mintuz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learn
Source: https://github.com/mintuz/claude-plugins/tree/main/plugins/core/skills/learn
Command: npx skills add https://github.com/mintuz/claude-plugins --skill learn-mintuz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to capturing hard-won learnings, gotchas, and decisions into CLAUDE.md, ensuring critical knowledge is preserved and discoverable for future work.

Core Features & Use Cases

  • Guided documentation: Defines what should be recorded (context, decision, outcomes) and where it lives within CLAUDE.md.
  • Standardized format: Promotes a consistent entry structure to facilitate search and reuse.
  • Onboarding and maintenance: Accelerates onboarding by surfacing lessons learned during development and debugging.

Quick Start

Log a CLAUDE.md learning entry for a recent learning, including context, decision, and outcome.

Frequently Asked Questions about learn

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

FAQPage Schema
How do I document architectural decisions and gotchas in CLAUDE.md?

To document architectural decisions in CLAUDE.md, you log structured entries containing the problem or context, the decision or solution, and the outcomes, preserving critical knowledge for future development and debugging.

What is the best way to structure knowledge transfer entries for project onboarding?

The best way to structure knowledge transfer entries is using a standardized format of problem/context, decision/solution, and outcomes, referencing a specific location within CLAUDE.md to accelerate onboarding and ensure easy discovery.

When should I record learnings and decisions into CLAUDE.md?

You should record learnings into CLAUDE.md during active development, debugging sessions, onboarding, and when making architectural decisions across projects to ensure consistent capture of hard-won insights.

Can I use a structured format for documenting debugging outcomes in CLAUDE.md?

Yes, you can use a structured format for documenting debugging outcomes in CLAUDE.md by enforcing entries that capture the problem context, the applied solution, and the final outcomes for consistent knowledge preservation.

Does documenting context and outcomes in CLAUDE.md require external dependencies?

Documenting context and outcomes in CLAUDE.md requires no external dependencies, operating as a standalone approach to capture hard-won learnings, gotchas, and architectural decisions directly within your project.