self-improvement

To capture learnings and errors for continuous improvement, initialize a `.learnings` directory with `LEARNINGS.md`, `ERRORS.md`, and `FEATURE_REQUESTS.md`, then log standardized entries when commands fail or corrections are made.

The logging mechanism triggers entries when commands fail, users correct outputs, external tools fail, knowledge is outdated, missing features are requested, or better approaches are discovered during development.

To promote logged learnings to assistant instructions, move standardized entries from the `.learnings` log files into `CLAUDE.md`, `AGENTS.md`, or `copilot-instructions.md` so broadly applicable insights are preserved and reusable.

Yes, you need to manually create the `.learnings` directory containing `LEARNINGS.md`, `ERRORS.md`, and `FEATURE_REQUESTS.md` in your project root before the hook-driven reminders can log structured entries.

Yes, you can use hook-driven reminders to automatically prompt logging after tool runs or user prompts, ensuring corrections and errors are captured in the standardized `.learnings` directory format.

The best way to track missing features and knowledge gaps is logging them into `FEATURE_REQUESTS.md` and `LEARNINGS.md` within a `.learnings` directory, using hook-driven reminders to capture entries as they occur.