self-improvement

To log command failures, API errors, and user corrections across sessions, you write structured entries to a centralized `.learnings/` directory. This stores development insights for later processing and reuse.

The best way to capture workflow learnings from command and API tool failures is to log them into a centralized learning store. Applying structured templates ensures these development insights are formatted as actionable entries for later processing.

You structure recurring development insights into broader memory by promoting recurring entries from the `.learnings/` directory. Guidelines and templates help format these discoveries so they can be reused by other agents across tasks.

Yes, this logging workflow applies to outdated knowledge and feature requests. It captures these development tasks as structured entries in the `.learnings/` directory for continuous improvement.

Yes, you need a `.learnings/` directory structure to log learnings and errors. The skill requires this specific folder structure alongside a SKILL.md file to store entries and apply recommended logging formats.