learning

You can extract reusable debugging patterns from development sessions by running this skill at session end to automatically categorize and archive errors, workarounds, and project knowledge into a structured knowledge base.

The best way to preserve project knowledge is to run this skill at the end of your session, which extracts debugging insights and stores them in structured folders like errors, debugging, and workarounds for future reference.

Yes, you can configure knowledge base paths and extraction thresholds for session learnings by adjusting settings in the config.json file to match your project's specific directory structure and requirements.

No, this pattern extraction skill operates without external dependencies, using frontmatter-driven templates and optional automation scripts to safely handle and store your development session data.

Extracted development learnings are organized into a structured knowledge base with dedicated folders for errors, debugging tips, workarounds, patterns, and project-specific knowledge to ensure easy retrieval.

You should run the session knowledge extraction process at the end of a development or debugging session to capture ad hoc learnings and transform them into reusable patterns before context is lost.