Advanced Roo Code Memory Bank
A modular, graph-based task management system that integrates with Roo Code custom modes for efficient, structured development workflows.
graph TD
Main["Memory Bank System"] --> Modes["Custom Modes"]
Main --> Rules["JIT Rule Loading"]
Main --> Visual["Visual Process Maps"]
Modes --> VAN["VAN: Initialization"]
Modes --> PLAN["PLAN: Task Planning"]
Modes --> CREATIVE["CREATIVE: Design"]
Modes --> IMPLEMENT["IMPLEMENT: Building"]
style Main fill:#4da6ff,stroke:#0066cc,color:white
style Modes fill:#f8d486,stroke:#e8b84d
style Rules fill:#80ffaa,stroke:#4dbb5f
style Visual fill:#d9b3ff,stroke:#b366ff
Overview
Memory Bank is a personal project that brings a structured, phase-based approach to development using Roo Code’s custom modes. It leverages Just-In-Time (JIT) rule loading, persistent memory files, and adaptive workflows for a seamless and intelligent development experience.
☕ Before exploring the key concepts and quick installation steps, grab your coffee-and if you enjoy my work, don’t forget to buy me a coffee!
Key Concepts
Modular, Graph-Based Workflow
- Interconnected Modes: Modes act as nodes in a workflow graph, enabling logical progression (VAN → PLAN → CREATIVE → IMPLEMENT).
- Persistent Memory: State and context are maintained across mode transitions via dedicated memory bank files.
- Adaptive Guidance: Each mode tailors its recommendations based on project complexity.
Isolated, Mode-Specific Rules
- No Global Rules: Only the active custom mode’s rules are loaded, keeping your main Roo Code environment unaffected.
- JIT Rule Loading: Loads only the rules needed for the current phase, optimizing context and performance.
- Future-Proofing: Global rules space remains open for future features.
- Inspired by Anthropic’s Claude “Think” tool, CREATIVE mode:
- Structures design exploration
- Documents pros/cons and alternatives
- Breaks down complex problems
- Records reasoning for future reference
See CREATIVE Mode and Claude’s “Think” Tool for more details.
Features
- Visual Workflow Maps: Clear diagrams for each development phase.
- Just-In-Time Rule Loading: Only relevant rules are active.
- Decision Trees & Checkpoints: Guided, phase-based workflows.
- QA Anywhere: Technical validation can be triggered from any mode.
- Platform-Aware: Commands adapt to your operating system.
Installation
Prerequisites
- Visual Studio Code
- Roo Code Extension: Install here
- AI Model: Claude 3.7 Sonnet recommended for best results (especially in CREATIVE mode).
Getting Started
1. Create Your Workspace
- Use this repository as a template:
- Click “Use this template” on the GitHub page.
- Create a new repository from the template.
- Clone your new repository:
git clone https://github.com/your-username/your-new-repo.git
2. Open in VS Code
- Launch VS Code.
- Open your cloned workspace folder.
3. Activate Roo Code Modes
- Ensure the Roo Code extension is installed.
- Use the Roo Code sidebar to switch between modes as described below.
Workflow Guide
1. Start with VAN Mode
- Switch to VAN mode in Roo Code.
- Type
VAN to initialize the project.
- VAN will analyze your project structure and assess task complexity.
2. Progress Through the Workflow
- Level 1 tasks: Proceed directly to IMPLEMENT after VAN.
- Level 2–4 tasks: Follow the full workflow:
VAN → PLAN → CREATIVE → IMPLEMENT
- At any point: Type
QA to perform a technical validation.
3. Mode Descriptions
- VAN: Initialize the project and determine complexity.
- PLAN: Create a detailed implementation plan.
- CREATIVE: Explore and document design options for complex components.
- IMPLEMENT: Systematically build the planned components.
- QA: Validate technical implementation (can be used in any mode).
Tip:
Switch modes at any time using the Roo Code sidebar or command palette for a seamless, guided workflow.
QA Functionality
QA is not a separate custom mode, but a set of validation functions available from any mode. Simply type QA in any mode to perform technical validation whenever needed.
Example Usage Video
Note: This repository was originally created for Cursor but has now been converted for Roo Code, so just follow prompts and usage steps in the video to understand the general logic.
Core Files and Their Purposes
graph LR
subgraph "Memory Bank Files"
Tasks["tasks.md<br>Source of Truth"]
Active["activeContext.md<br>Current Focus"]
Progress["progress.md<br>Implementation Status"]
Creative["creative-*.md<br>Design Decisions"]
end
style Tasks fill:#f9d77e,stroke:#d9b95c,stroke-width:3px
style Active fill:#a8d5ff,stroke:#88b5e0
style Progress fill:#c5e8b7,stroke:#a5c897
style Creative fill:#f4b8c4,stroke:#d498a4
- tasks.md: Central source of truth for task tracking.
- activeContext.md: Maintains focus of current development phase.
- progress.md: Tracks implementation status.
- creative-*.md: Design decision documents generated during CREATIVE mode.
Resources
评论