learn

Document reusable problem-solving patterns from development sessions to Markdown files.

2|Updated Apr 28, 2025
One-click install
npx skills add https://github.com/gunubin/dotfiles --skill learn-gunubin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: learn
Source: https://github.com/gunubin/dotfiles/tree/main/claude/.claude/skills/learn
Command: npx skills add https://github.com/gunubin/dotfiles --skill learn-gunubin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you capture and document valuable, reusable problem-solving patterns discovered during development sessions, preventing knowledge loss and accelerating future debugging.

Core Features & Use Cases

  • Pattern Identification: Extracts solutions for errors, debugging techniques, and library workarounds from conversation history.
  • Structured Documentation: Saves patterns in a standardized Markdown format for easy retrieval and application.
  • Use Case: After a complex debugging session, use this Skill to save the specific steps and insights gained into a pattern named "Supabase RLS Policy Debugging" for future reference.

Quick Start

Use the learn skill to document a new reusable pattern.

Frequently Asked Questions about learn

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

FAQPage Schema
How do I document reusable debugging patterns after resolving library errors?▼

You can document reusable debugging patterns by extracting error resolutions and library workarounds from your session, saving them as structured Markdown files in ~/.claude/learned/ for future retrieval and application.

What is the best way to save problem-solving techniques to prevent knowledge loss?▼

Saving problem-solving techniques involves capturing debugging insights into standardized Markdown files, preventing knowledge loss by creating a persistent repository of reusable development patterns.

Can I capture library quirks and workarounds into a named pattern file?▼

Yes, you can capture library quirks and workarounds into a named pattern file. The pattern is saved directly to ~/.claude/learned/[pattern-name].md, allowing you to reference specific debugging steps later.

Does this knowledge management approach require any external dependencies?▼

No external dependencies are required for this knowledge management approach. It operates independently to extract problem-solving patterns from conversation history and writes them to local Markdown files.

How do I retrieve saved error resolution patterns for future development sessions?▼

Saved error resolution patterns are retrieved as structured Markdown files stored in ~/.claude/learned/[pattern-name].md, allowing you to directly access and apply documented debugging techniques during future sessions.

When should I document a debugging workaround instead of just fixing the code?▼

You should document a debugging workaround when the solution involves complex error resolutions or library quirks that represent a reusable problem-solving pattern worth referencing for future development.