learned-lessons

You record solved debugging problems by running the /til command after finding a solution. This writes a structured entry with the date, title, problem, symptoms, solution, and tags into a centralized knowledge base. New entries are prepended so the latest lessons appear first.

Yes, you can check your existing knowledge base for a solution before performing a new web search by using the /lessons or /search-lessons command. The system automatically retrieves relevant past solutions during debugging to prevent repeating previous work.

Recorded lessons and solved problems are stored in the ~/.claude/knowledge-base.md file. This ensures persistence across sessions by keeping all entries in a structured markdown format with the newest solutions added to the top.

The best way to maintain a searchable memory of technical solutions is to capture them into a structured knowledge base immediately after solving them via web search. Recording entries with specific tags and symptoms allows for instant retrieval during future debugging.

No external dependencies or tools are needed to start recording lessons into a knowledge base. The system operates independently by writing structured problem and solution entries directly to a local markdown file in your environment.

A limitation of using a local markdown file for debugging knowledge retrieval is that entries are text-based and stored locally. Retrieval effectiveness depends on the consistency of your recorded tags and symptoms rather than a relational database query system.