How chipphillips/new-project-rules-ultra-context-for-ai-memories-lessons-scratchpad-with-plan-and-act-modes works
Main Components
• Memory System – Representing the module that logs every interaction (from memories.md) with timestamps, tags, and version-controlled entries.
• Lessons Learned – A dedicated component (from lessons-learned.md) that captures issues, solutions, and impacts with links to specific examples.
• Scratchpad – This part (from scratchpad.md) is used for managing the current phase, tasks, statuses, and dependencies.
• Mode Handling – Differentiate between “Plan Mode” (gathering information, generating questions, and planning tasks) and “Agent Mode” (which executes actions once confidence and readiness criteria are met).
• Rules & Specifications – File directories like .cursor/rules and .cursorrules, along with RULESFORAI.md, embody the guidelines and operational triggers that structure how the overall system behaves.
• Project Requirements – The file project-requirements.md that specifies system needs and could affect how the other modules interact.
Interactions and Relationships
• Data Flow & Updates:
• The Memory System continuously logs interactions and decisions.
• The Lessons Learned module collects post-action feedback and tracks best practices.
• The Scratchpad ties in real-time task tracking and updates, feeding directly into the mode system.
• Mode System Transitions:
• Cross-referencing:
• How different modules reference each other (for example, @memories.md ↔️ @lessons-learned.md ↔️ @scratchpad.md).
Architectural Patterns and Design Principles
• Modular Organization – Separate files and directories indicate a modular design where each file/component has a dedicated responsibility.
• Documentation and Version Control – Emphasize that every module logs and updates its data consistently (noting the [v1.0.0] style).
Incorporate Relevant Technologies, Frameworks, or Libraries
• Markdown-based formats for documentation indicate a file-driven approach.
• Although not described as using web or UI frameworks, the structure could be extended by integrating APIs or storage systems if necessary. For now, focus on the protocol and file I/O mechanisms as the “technology” behind the scenes.