# roo-code-memory-bank **Repository Path**: mirrors_gbozee/roo-code-memory-bank ## Basic Information - **Project Name**: roo-code-memory-bank - **Description**: ๐Ÿง  Roo Code Memory Bank: Seamless project context in Roo Code. No more repetition, just continuous development. Includes Architect, Code, Ask, Debug and Test modes! - **Primary Language**: Unknown - **License**: Apache-2.0 - **Default Branch**: main - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 0 - **Created**: 2025-03-20 - **Last Updated**: 2026-04-11 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README
### Be sure to give ๐Ÿš€[RooFlow](https://github.com/GreatScottyMac/RooFlow)๐ŸŒŠ a try!
# ๐Ÿง  Roo Code Memory Bank **Persistent Project Context for AI-Assisted Development** [![VS Code Extension](https://img.shields.io/badge/VS%20Code-Extension-blue.svg)](https://github.com/RooVetGit/Roo-Code) [![GitHub](https://img.shields.io/badge/View%20on-GitHub-lightgrey.svg)](https://github.com/GreatScottyMac/roo-code-memory-bank)
## ๐ŸŽฏ Overview Roo Code Memory Bank solves a critical challenge in AI-assisted development: **maintaining context across sessions**. By providing a structured memory system integrated with VS Code, it ensures your AI assistant maintains a deep understanding of your project across sessions. ### Key Components ```mermaid graph LR A[Memory Bank] --> B[Core Files] A --> C[Mode Rules] A --> D[VS Code UI] B --> E[Project Context] B --> F[Decisions] B --> G[Progress] C --> H[Architect] C --> I[Code] C --> J[Ask] C --> K1[Debug] C --> K2[Test] K[Real-time Updates] --> B K --> L[Continuous Sync] L --> M[Auto-save] L --> N[Event Tracking] ``` - ๐Ÿง  **Memory Bank**: Persistent storage for project knowledge - ๐Ÿ“‹ **Mode Rules**: YAML-based behavior configuration - ๐Ÿ”ง **VS Code Integration**: Seamless development experience - โšก **Real-time Updates**: Continuous context synchronization ## ๐Ÿš€ Quick Start ### 1. Configure Custom Instructions #### a. Copy Rule and Mode Files Download and copy these files to your project's **root** directory: | Mode | Rule File | Purpose | |------|-----------|----------| | Code | [`.clinerules-code`](https://github.com/GreatScottyMac/roo-code-memory-bank/blob/main/.clinerules-code) | Implementation and coding tasks | | Architect | [`.clinerules-architect`](https://github.com/GreatScottyMac/roo-code-memory-bank/blob/main/.clinerules-architect) | System design and architecture | | Ask | [`.clinerules-ask`](https://github.com/GreatScottyMac/roo-code-memory-bank/blob/main/.clinerules-ask) | Information and assistance | | Debug | [`.clinerules-debug`](https://github.com/GreatScottyMac/roo-code-memory-bank/blob/main/.clinerules-debug) | Troubleshooting and problem-solving | | Test | [`.clinerules-test`](https://github.com/GreatScottyMac/roo-code-memory-bank/blob/main/.clinerules-test) | Test-driven development and quality assurance | | Mode | [`.roomodes`](https://github.com/GreatScottyMac/roo-code-memory-bank/blob/main/.roomodes) | Custom mode configuration file for Test mode | > ๐Ÿ“ **Special Note for Test Mode**: Test mode requires both the [`.clinerules-test`](https://github.com/GreatScottyMac/roo-code-memory-bank/blob/main/.clinerules-test) file AND [`.roomodes`](https://github.com/GreatScottyMac/roo-code-memory-bank/blob/main/.roomodes) file in your project root for proper functionality. #### b. Configure Roo Code Prompt Settings > โš ๏ธ **Important**: The system default descriptions in the Role Definition boxes can remain but leave the Mode-specific Custom Instructions boxes empty. ### 2. Initialize Memory Bank 1. Switch to **Architect** or **Code** mode in Roo Code chat 2. Send a message (e.g., "hello") 3. Roo will automatically: - ๐Ÿ” Scan for `memory-bank/` directory - ๐Ÿ“ Create it if missing (with your approval) - ๐Ÿ“ Initialize core files - ๐Ÿšฆ Provide next steps
๐Ÿ’ก Pro Tip: Project Brief Create a `projectBrief.md` in your project root **before** initialization to give Roo immediate project context.
### File Organization ``` project-root/ โ”œโ”€โ”€ .clinerules-architect โ”œโ”€โ”€ .clinerules-code โ”œโ”€โ”€ .clinerules-ask โ”œโ”€โ”€ .clinerules-debug โ”œโ”€โ”€ .clinerules-test โ”œโ”€โ”€ .roomodes โ”œโ”€โ”€ memory-bank/ โ”‚ โ”œโ”€โ”€ activeContext.md โ”‚ โ”œโ”€โ”€ productContext.md โ”‚ โ”œโ”€โ”€ progress.md โ”‚ โ””โ”€โ”€ decisionLog.md โ””โ”€โ”€ projectBrief.md ``` ## ๐Ÿ“š Memory Bank Structure ```mermaid graph TD MB[memory-bank/] --> AC[activeContext.md] MB --> DL[decisionLog.md] MB --> PC[productContext.md] MB --> PR[progress.md] MB --> PB[projectBrief.md] MB --> SP[systemPatterns.md] subgraph Core Files AC[Current Session State] DL[Technical Decisions] PC[Project Overview] PR[Progress Tracking] end subgraph Optional PB[Project Brief] SP[System Patterns] end ```
๐Ÿ“– View File Descriptions | File | Purpose | |------|----------| | `activeContext.md` | Tracks current goals, decisions, and session state | | `decisionLog.md` | Records architectural choices and their rationale | | `productContext.md` | Maintains high-level project context and knowledge | | `progress.md` | Documents completed work and upcoming tasks | | `projectBrief.md` | Contains initial project requirements (optional) | | `systemPatterns.md` | Documents recurring patterns and standards |
## โœจ Features ### ๐Ÿง  Persistent Context - Remembers project details across sessions - Maintains consistent understanding of your codebase - Tracks decisions and their rationale ### ๐Ÿ”„ Smart Workflows ```mermaid graph LR A[Architect Mode] -->|Real-time Design Updates| B[Memory Bank] C[Code Mode] -->|Real-time Implementation| B D[Ask Mode] -->|Real-time Insights| B F[Debug Mode] -->|Real-time Analysis| B G[Test Mode] -->|Real-time Testing| B B -->|Instant Context| A B -->|Instant Context| C B -->|Instant Context| D B -->|Instant Context| F B -->|Instant Context| G E[Event Monitor] -->|Continuous Sync| B ``` - Mode-based operation for specialized tasks - Automatic context switching - Project-specific customization via rules ### ๐Ÿ“Š Knowledge Management - Structured documentation with clear purposes - Technical decision tracking with rationale - Automated progress monitoring - Cross-referenced project knowledge ## ๐Ÿ’ก Pro Tips ### Architect Mode Roo Code Memory Bank's Architect mode is designed for high-level system design and project organization. This mode focuses on architectural decisions, system structure, and maintaining project-wide consistency. #### Key Capabilities - ๐Ÿ—๏ธ **System Design**: Create and maintain architecture - ๐Ÿ“ **Pattern Definition**: Establish coding patterns and standards - ๐Ÿ”„ **Project Structure**: Organize code and resources - ๐Ÿ“‹ **Documentation**: Maintain technical documentation - ๐Ÿค **Team Collaboration**: Guide implementation standards #### Real-time Update Triggers Architect mode actively monitors and updates Memory Bank files based on: - ๐ŸŽฏ Architectural decisions and changes - ๐Ÿ“Š System pattern definitions - ๐Ÿ”„ Project structure updates - ๐Ÿ“ Documentation requirements - โšก Implementation guidance needs #### Memory Bank Integration ```mermaid graph TD A[Architect Mode] --> B[Design Decisions] A --> C[Pattern Definition] B --> D[Memory Bank Updates] C --> D D --> E[activeContext.md] D --> F[progress.md] D --> G[decisionLog.md] E --> H[Design Status] F --> I[Architecture Progress] G --> J[Design Decisions] ``` Switch to Architect mode when you need to: - Design system architecture - Define coding patterns - Structure new projects - Guide implementations - Make architectural decisions ### Code Mode Roo Code Memory Bank's Code mode is your primary interface for implementation and development. This mode specializes in writing, modifying, and maintaining code while following established patterns. #### Key Capabilities - ๐Ÿ’ป **Code Creation**: Write new code and features - ๐Ÿ”ง **Code Modification**: Update existing implementations - ๐Ÿ“š **Documentation**: Add code comments and docs - โœจ **Quality Control**: Maintain code standards - ๐Ÿ”„ **Refactoring**: Improve code structure #### Real-time Update Triggers Code mode actively monitors and updates Memory Bank files based on: - ๐Ÿ“ Code implementations - ๐Ÿ”„ Feature updates - ๐ŸŽฏ Pattern applications - โšก Performance improvements - ๐Ÿ“š Documentation updates #### Memory Bank Integration ```mermaid graph TD A[Code Mode] --> B[Implementation] A --> C[Documentation] B --> D[Memory Bank Updates] C --> D D --> E[activeContext.md] D --> F[progress.md] D --> G[decisionLog.md] E --> H[Current Tasks] F --> I[Code Progress] G --> J[Implementation Decisions] ``` Switch to Code mode when you need to: - Implement new features - Modify existing code - Add documentation - Apply coding patterns - Refactor code ### Ask Mode Roo Code Memory Bank's Ask mode serves as your knowledge base interface and documentation assistant. This mode excels at providing information, explaining concepts, and maintaining project knowledge. #### Key Capabilities - ๐Ÿ’ก **Knowledge Sharing**: Access project insights - ๐Ÿ“š **Documentation**: Create and update docs - ๐Ÿ” **Code Explanation**: Clarify implementations - ๐Ÿค **Collaboration**: Share understanding - ๐Ÿ“– **Pattern Education**: Explain system patterns #### Real-time Update Triggers Ask mode actively monitors and updates Memory Bank files based on: - โ“ Knowledge requests - ๐Ÿ“ Documentation needs - ๐Ÿ”„ Pattern explanations - ๐Ÿ’ก Implementation insights - ๐Ÿ“š Learning outcomes #### Memory Bank Integration ```mermaid graph TD A[Ask Mode] --> B[Knowledge Sharing] A --> C[Documentation] B --> D[Memory Bank Updates] C --> D D --> E[activeContext.md] D --> F[progress.md] D --> G[decisionLog.md] E --> H[Current Topics] F --> I[Documentation Progress] G --> J[Knowledge Decisions] ``` Switch to Ask mode when you need to: - Understand code patterns - Get implementation guidance - Create documentation - Share knowledge - Learn system concepts ### Debug Mode Roo Code Memory Bank's Debug mode specializes in systematic problem-solving and troubleshooting. This mode employs strategic analysis and verification to identify and resolve issues. #### Key Capabilities - ๐Ÿ” **Issue Investigation**: Analyze problems systematically - ๐Ÿ“Š **Error Analysis**: Track error patterns - ๐ŸŽฏ **Root Cause Finding**: Identify core issues - โœ… **Solution Verification**: Validate fixes - ๐Ÿ“ **Problem Documentation**: Record findings #### Real-time Update Triggers Debug mode actively monitors and updates Memory Bank files based on: - ๐Ÿ› Bug discoveries - ๐Ÿ“ˆ Performance issues - ๐Ÿ”„ Error patterns - โšก System bottlenecks - ๐Ÿ“ Fix verifications #### Memory Bank Integration ```mermaid graph TD A[Debug Mode] --> B[Investigation] A --> C[Analysis] B --> D[Memory Bank Updates] C --> D D --> E[activeContext.md] D --> F[progress.md] D --> G[decisionLog.md] E --> H[Current Issues] F --> I[Debug Progress] G --> J[Solution Decisions] ``` Switch to Debug mode when you need to: - Investigate issues - Analyze errors - Find root causes - Verify fixes - Document problems ### Test Mode Roo Code Memory Bank includes a powerful Test mode for test-driven development and quality assurance. This mode operates with a focus on test creation, execution, and validation while maintaining code quality. #### Key Capabilities - ๐Ÿงช **Test-Driven Development**: Write tests before implementation - ๐Ÿ“Š **Test Execution**: Run and monitor test suites - ๐Ÿ” **Coverage Analysis**: Track and improve test coverage - ๐ŸŽฏ **Quality Assurance**: Validate code against requirements - โœ… **Test Result Management**: Track and report test outcomes #### Real-time Update Triggers Test mode actively monitors and updates Memory Bank files based on: - ๐Ÿ”„ Test executions and results - ๐Ÿ“ˆ Coverage metrics and gaps - ๐Ÿ› Test failure patterns - โœจ New test requirements - ๐Ÿ“ Test documentation needs #### Memory Bank Integration ```mermaid graph TD A[Test Mode] --> B[Test Creation] A --> C[Test Execution] B --> D[Memory Bank Updates] C --> D D --> E[activeContext.md] D --> F[progress.md] D --> G[decisionLog.md] E --> H[Test Status] F --> I[Test Progress] G --> J[Test Decisions] ``` Switch to Test mode when you need to: - Write new tests - Run test suites - Analyze test coverage - Validate code quality - Document test results ### Session Management - โšก **Real-time Updates**: Memory Bank automatically stays synchronized with your work - ๐Ÿ’พ **Manual Updates**: Use "UMB" or "update memory bank" as a fallback when: - Ending a session unexpectedly - Halting mid-task - Recovering from connection issues - Forcing a full synchronization ## ๐Ÿ“– Documentation - [Developer Deep Dive](https://github.com/GreatScottyMac/roo-code-memory-bank/blob/main/developer-primer.md) - [Update Log](https://github.com/GreatScottyMac/roo-code-memory-bank/blob/main/updates.md) ---
**[View on GitHub](https://github.com/GreatScottyMac/roo-code-memory-bank) โ€ข [Report Issues](https://github.com/GreatScottyMac/roo-code-memory-bank/issues) โ€ข [Get Roo Code](https://github.com/RooVetGit/Roo-Code)**
## License Apache 2.0 ยฉ 2025 [GreatScottyMac](LICENSE)