repository·main·Indexed 19 days ago
https://github.com/michaelzag/roocode-tips-tricksA collection of utilities, documentation, and frameworks to optimize the Roo Code AI coding assistant experience. It features the Handoff Manager system for context management, custom mode configuration, and handling large files through automated conversation extraction, milestone organization, and a modular system prompt assembly process.
The Handoff Manager is a system designed to facilitate and manage handoffs between developers. It provides a structured way to transfer context and tasks using Roo-Code. The system consists of:
personal_roo_docs/technical/ directory contains in-depth technical documentation regarding Roo Code's internal workings. This documentation is divided into two main categories: Core Implementation (covering specific feature architectures like Browser Automation and Checkpoint Systems) and Core Systems (covering operational mechanisms like File Filtering and MCP Server Integration).Implementing context optimization techniques in Roo-Code provides the following measurable improvements:
personal_roo_docs/normal/ directory provides practical, non-technical guides for everyday Roo Code users. These guides are categorized into Core Features (basic usage and customization) and Advanced Features (optimization and external integrations).The personal_roo_docs/ directory serves as a centralized knowledge base for Roo Code, categorized by technical depth. Use the following categories to find information:
normal/ directory. These are user guides designed to help you maximize Roo's potential through practical usage.technical/ directory. These provide in-depth implementation details, architecture, and advanced usage patterns. These are specifically optimized to be used as references for the LLM when working with Roo features.A Component Set is a modular collection of files designed to provide specific functionality within the Handoff Publisher system. It is the primary unit of organization for code and configurations.
A Component Set must satisfy four requirements:
1-utils.js, 2-backup.js) to control execution/loading order.src-config.json or system-prompt-config.json).publish-config.json file under the componentSets array.The Handoff Publisher uses a modular architecture to separate concerns, making it easy to maintain and extend. The core logic is distributed across the following modules:
index.js: The main entry point for the publisher script.system-prompt.js: Responsible for assembling the system prompt and processing root files.src-assembler.js: Responsible for assembling source code components.installer-assembler.js: Responsible for processing directories and generating the final installer script.config-merger.js: Handles the merging of various configuration files.file-utils.js: Provides general file operation utilities.Modes control capabilities through TOOL_GROUPS. When a mode is active, the AI can only use tools belonging to the groups explicitly listed in its configuration.
Available Tool Groups:
read: Includes read_file, search_files, list_files, list_code_definition_names.edit: Includes apply_diff, write_to_file, insert_content, search_and_replace.browser: Includes browser_action.command: Includes execute_command.mcp: Includes use_mcp_tool, access_mcp_resource.File Restrictions:
To prevent a mode from modifying sensitive files, use a tuple in the groups array. For the edit group, providing a fileRegex ensures that tools like apply_diff or write_to_file only operate on files matching that pattern. If a tool attempts to access a file outside this pattern, a FileRestrictionError is thrown.
// Example of a group with a file restriction
["edit", {
"fileRegex": "\\.(ts|js)$",
"description": "TypeScript and JavaScript files only"
}]To optimize performance when filtering large codebases, apply filters in order of computational cost (fastest to slowest). This reduces the number of files processed by expensive operations. The recommended order is:
stat calls.// Example of optimized filtering approach
async function optimizedFileFiltering(options: FilterOptions): Promise<string[]> {
// 1. Start with fast, broad filters
const files = await getInitialFileList(options.directory);
// 2. Apply extension filtering (very fast)
const extensionFiltered = filterByExtension(files, options.extensions);
// 3. Apply ignore patterns (moderately fast with caching)
const ignoreFiltered = applyIgnorePatterns(extensionFiltered, options.ignorePatterns);
// 4. Apply size filtering (requires stat calls)
const sizeFiltered = await filterBySize(ignoreFiltered, options.maxSize);
// 5. Apply binary detection (expensive, do last)
const binaryFiltered = options.excludeBinary
? await filterOutBinaryFiles(sizeFiltered)
: sizeFiltered;
return binaryFiltered;
}Browser automation in Roo-Code follows a controller pattern using Puppeteer. The workflow follows a strict sequence: Launch $\rightarrow$ Interaction $\rightarrow$ Feedback $\rightarrow$ Close.
networkidle2 to ensure the page is loaded.X,Y) to perform a click and waits for network activity to settle.Roo-Code uses a multi-layered settings system to allow for both global preferences and project-specific overrides. When the system requests a setting, it resolves the value using the following priority order:
This hierarchy ensures that you can have general settings for all your coding tasks while maintaining specific configurations for individual repositories.