self-improvement

Log coding errors and corrections by writing them to markdown files within a project workspace `.learnings` directory, centralizing insights and fixes for persistent reference across sessions.

The best way to capture learnings is by logging errors, corrections, and new capabilities to markdown files whenever issues arise, enabling validation and promotion to central guidance files for future reuse.

Yes, you can use a YAML frontmatter `SKILL.md` with a name and description to enable cross-session knowledge sharing and promote important learnings to central guidance files across projects and agents.

Initialize the `.learnings` directory and log files on first use, guided by OpenClaw integration and initialization setup, ensuring a consistent, repeatable environment for recording project memory across sessions.

Yes, OpenClaw integration supports automated prompts and hook triggers through optional references, assets, and scripts, providing tooling for extended workflows when logging corrections and learnings.

Promote logged learnings to central guidance files when patterns are validated and require cross-project knowledge sharing, elevating them from local markdown logs to persistent project memory for continuous improvement.