remember

To save debugging lessons into a knowledge base, you parse the input lesson, assign a target domain, and update the corresponding memory file. This creates a persistent, actionable instruction set for future reference.

Domain-organized memory categorizes development best practices and debugging insights into specific domains like git-workflow. This self-organizing knowledge base prevents repeated mistakes by storing actionable instructions globally or per workspace.

Yes, you can store memories separately by managing scope during the memory creation process. The system supports both global persistence and current workspace context to ensure specific or broad recall as needed.

You automatically categorize best practices by globbing existing memory files, analyzing the lesson, and determining the target domain. The system then reads the relevant file and updates it with succinct, actionable instructions or creates a new file.

If no existing memory file matches your debugging insight, the system creates a new memory file. It determines the target domain and file path automatically to maintain a self-organizing knowledge base without manual folder setup.