Zoo-Code-Org · hannesrudolph · May 14, 2026 · May 6, 2026 · May 8, 2026 · May 11, 2026
@@ -2,7 +2,7 @@
 
 This file provides guidance to agents when working with code in this repository.
 
-- Docusaurus docs, not source code. This is documentation for the Roo Code VS Code extension at docs.roocode.com.
+- Docusaurus docs, not source code. This is documentation for the Zoo Code VS Code extension at docs.zoocode.dev.
 - Legacy [Rakefile](Rakefile) is from old Jekyll site. Ignore it; current build uses Docusaurus/npm scripts.
 - Tutorial videos defined in [docs/tutorial-videos.json](docs/tutorial-videos.json), dynamically loaded in [sidebars.ts](sidebars.ts:37-42). Titles truncated to 40 chars.
 - Release notes have thanking exclusions: don't thank daniel-lxs, cte, hannesrudolph, jr, roomote, app/roomote, dleffel, mrubens per [.roorules](.roorules:14).

@@ -1,6 +1,6 @@
 <writing_style_guide>
   <overview>
-    Writing style for Roo Code documentation. The goal is clarity and trust, not personality.
+    Writing style for Zoo Code documentation. The goal is clarity and trust, not personality.
     Optimize for reader momentum and capability discovery, not author completeness.
     All output must be markdown.
   </overview>

@@ -1,6 +1,6 @@
 <docusaurus_conventions>
   <overview>
-    Docusaurus-specific formatting rules for Roo Code documentation.
+    Docusaurus-specific formatting rules for Zoo Code documentation.
     Always explore the project structure to understand the actual directory layout before applying these conventions.
   </overview>
 

@@ -1,6 +1,6 @@
 <workflow_instructions>
   <mode_overview>
-    Automates creating release notes for new Roo Code versions. Fetches pull requests
+    Automates creating release notes for new Zoo Code versions. Fetches pull requests
     from GitHub, analyzes changes, generates user-focused notes, and handles Discord and Reddit
     formatting. Supports bare version requests (runs full workflow) and auto-detection of missing versions.
   </mode_overview>
@@ -534,7 +534,7 @@ Which features should I highlight with expanded sections in the release notes?
             - If there is no persisted path file OR it does not start with "/img/", skip inline insertion
           </behavior>
           <html_snippet><![CDATA[
-<img src="[FRONTMATTER_IMAGE_PATH]" alt="Roo Code v[VERSION] Release" width="600" />
+<img src="[FRONTMATTER_IMAGE_PATH]" alt="Zoo Code v[VERSION] Release" width="600" />
           ]]></html_snippet>
         </inline_hero_image>
       </step>
@@ -583,7 +583,7 @@ Which features should I highlight with expanded sections in the release notes?
         - Wrap entire output in markdown code block
       </transformations>
       <formatting_rules>
-        <rule>Title format: # Roo Code X.Y.Z Release Updates (no emoji)</rule>
+        <rule>Title format: # Zoo Code X.Y.Z Release Updates (no emoji)</rule>
         <rule>Preserve all section headings EXACTLY as in source docs</rule>
         <rule>Preserve section order EXACTLY as in source docs</rule>
         <rule>Copy all bullet points exactly (only change * to -)</rule>
@@ -607,7 +607,7 @@ Which features should I highlight with expanded sections in the release notes?
         <step>Apply minimal Discord transformations</step>
       </steps>
       <formatting_rules>
-        <rule>Title format: # Roo Code X.Y.Z-X.Y.Z Release Updates (no emoji)</rule>
+        <rule>Title format: # Zoo Code X.Y.Z-X.Y.Z Release Updates (no emoji)</rule>
         <rule>Preserve all section headings EXACTLY as in source docs</rule>
         <rule>Footer with links to each version: [vX.Y.Z](link) | [vX.Y.Z](link)</rule>
         <rule>Wrap entire output in ```markdown code block</rule>

@@ -23,15 +23,15 @@
 ---
 description: A concise summary of the release.
 keywords:
-  - roo code x.y.z
+  - Zoo Code x.y.z
   - new features
   - bug fixes
 ---
         </format>
       </element>
 
       <element name="title">
-        <format># Roo Code X.Y.Z Release Notes (YYYY-MM-DD)</format>
+        <format># Zoo Code X.Y.Z Release Notes (YYYY-MM-DD)</format>
         <requirements>
           - Include version number
           - Include release date in ISO 8601 format
@@ -49,10 +49,10 @@ keywords:
         <rules>
           - Insert only if frontmatter image path resolves to "/img/..." and is not "/img/social-share.jpg"
           - Use an HTML image tag per site rules with width="600"
-          - Set src from .roo/tmp/release-notes/frontmatter_image_v[version].txt and alt to "Roo Code v[VERSION] Release"
+          - Set src from .roo/tmp/release-notes/frontmatter_image_v[version].txt and alt to "Zoo Code v[VERSION] Release"
         </rules>
         <template>
-<img src="/img/vX.Y.Z/vX.Y.Z.png" alt="Roo Code vX.Y.Z Release" width="600" />
+<img src="/img/vX.Y.Z/vX.Y.Z.png" alt="Zoo Code vX.Y.Z Release" width="600" />
         </template>
       </element>
     </required_elements>
@@ -251,8 +251,8 @@ keywords:
       </element>
 
       <element name="title">
-        <format># Roo Code X.Y.Z Release Updates</format>
-        <format_combined># Roo Code X.Y.Z-X.Y.Z Release Updates</format_combined>
+        <format># Zoo Code X.Y.Z Release Updates</format>
+        <format_combined># Zoo Code X.Y.Z-X.Y.Z Release Updates</format_combined>
         <rules>
           - No emoji in title
           - Use "Release Updates" for both single and combined versions
@@ -352,8 +352,8 @@ See full release notes [vX.Y.Z](https://docs.roocode.com/update-notes/vX.Y.Z) |
       </element>
 
       <element name="title">
-        <format>Roo Code X.Y.Z Release Updates | [key feature 1] | [key feature 2] | [key feature 3]</format>
-        <format_combined>Roo Code X.Y.Z-X.Y.Z Release Updates | [key feature 1] | [key feature 2] | [key feature 3]</format_combined>
+        <format>Zoo Code X.Y.Z Release Updates | [key feature 1] | [key feature 2] | [key feature 3]</format>
+        <format_combined>Zoo Code X.Y.Z-X.Y.Z Release Updates | [key feature 1] | [key feature 2] | [key feature 3]</format_combined>
         <rules>
           - Plain text line (no leading "#")
           - Derive key features from source intro sentence (not hardcoded examples)

@@ -198,7 +198,7 @@ Which would you like to process?</question>
       <rule>Only ask if the user requests "compress"/"condense".</rule>
     </behavior>
     <formatting_checklist>
-      <item>Title: "# Roo Code X.Y.Z Release Updates" (no emoji)</item>
+      <item>Title: "# Zoo Code X.Y.Z Release Updates" (no emoji)</item>
       <item>Include "@everyone" tagline derived from source intro sentence</item>
       <item>Preserve section headings EXACTLY as they appear in source docs</item>
       <item>Preserve section order EXACTLY as in source docs</item>
@@ -234,7 +234,7 @@ Which would you like to process?</question>
       <rule>Preserve original section headings and structure from source docs exactly.</rule>
     </behavior>
     <formatting_checklist>
-      <item>Title (plain text): "Roo Code X.Y.Z Release Updates | [key feature 1] | [key feature 2]" (derived from source)</item>
+      <item>Title (plain text): "Zoo Code X.Y.Z Release Updates | [key feature 1] | [key feature 2]" (derived from source)</item>
       <item>Intro italic note present</item>
       <item>Preserve section headings EXACTLY as they appear in source docs</item>
       <item>Preserve section order EXACTLY as in source docs</item>
@@ -257,7 +257,7 @@ Which would you like to process?</question>
       <step>Present formatted output in markdown code block</step>
     </workflow>
     <formatting_checklist>
-      <item>Title: "# Roo Code X.Y.Z-X.Y.Z Release Updates" (no emoji, version range)</item>
+      <item>Title: "# Zoo Code X.Y.Z-X.Y.Z Release Updates" (no emoji, version range)</item>
       <item>Include "@everyone" tagline derived from source intro sentences</item>
       <item>Preserve all section headings EXACTLY as they appear in source docs</item>
       <item>Merge content from same-named sections across versions</item>

@@ -2,7 +2,7 @@ customModes:
   - slug: documentation-writer
     name: 📖 Documentation Writer
     roleDefinition: |-
-      You are Roo Code, a documentation specialist who sounds like a careful engineering teammate.
+      You are Zoo Code, a documentation specialist who sounds like a careful engineering teammate.
       Calm, precise, focused on what will happen next. The goal is clarity and trust, not personality.
 
       Core behaviors:
@@ -34,7 +34,7 @@ customModes:
     source: project
   - slug: release-notes-writer
     name: 📝 Release Notes Writer
-    roleDefinition: "You are a technical writer for Roo Code release notes. Your job is to: - Automate release note creation. - Fetch and analyze GitHub pull requests. - Convert technical changes into user benefits. - Ensure updates align with documentation standards. - Update all required documentation files in the docs/update-notes directory."
+    roleDefinition: "You are a technical writer for Zoo Code release notes. Your job is to: - Automate release note creation. - Fetch and analyze GitHub pull requests. - Convert technical changes into user benefits. - Ensure updates align with documentation standards. - Update all required documentation files in the docs/update-notes directory."
     whenToUse: |-
       Use this mode to create or update release notes from GitHub PRs and existing docs.
       Triggers: "Create release notes for X.Y.Z", "vX.Y.Z", bare version (e.g., "3.25.1"), "latest",

@@ -1,4 +1,4 @@
-# Roo Code Documentation Rules
+# Zoo Code Documentation Rules
 
 ## Documentation Links
 - Do not include .md extensions in documentation links

@@ -1,6 +1,6 @@
-# Roo Code Docs
+# Zoo Code Docs
 
-This website is built using [Docusaurus](https://docusaurus.io/), a modern static website generator, and lives at https://docs.roocode.com
+This website is built using [Docusaurus](https://docusaurus.io/), a modern static website generator, and lives at https://docs.zoocode.dev
 
 ### Installation
 

@@ -1,18 +1,18 @@
 ---
-description: Learn how the access_mcp_resource tool retrieves data from Model Context Protocol servers for additional context in Roo Code tasks.
+description: Learn how the access_mcp_resource tool retrieves data from Model Context Protocol servers for additional context in Zoo Code tasks.
 keywords:
   - access_mcp_resource
   - MCP
   - Model Context Protocol
   - MCP resources
-  - Roo Code tools
+  - Zoo Code tools
   - context retrieval
   - API integration
 ---
 
 # access_mcp_resource
 
-The `access_mcp_resource` tool retrieves data from resources exposed by connected Model Context Protocol (MCP) servers. It allows Roo to access files, API responses, documentation, or system information that provides additional context for tasks.
+The `access_mcp_resource` tool retrieves data from resources exposed by connected Model Context Protocol (MCP) servers. It allows Zoo to access files, API responses, documentation, or system information that provides additional context for tasks.
 
 ---
 

@@ -1,12 +1,12 @@
 ---
-description: Master the apply_diff tool for making surgical code changes using fuzzy matching and line hints in Roo Code with multi-file support.
+description: Master the apply_diff tool for making surgical code changes using fuzzy matching and line hints in Zoo Code with multi-file support.
 keywords:
   - apply_diff
   - file editing
   - code modifications
   - fuzzy matching
   - diff tool
-  - Roo Code tools
+  - Zoo Code tools
   - multi-file edits
 ---
 
@@ -35,7 +35,7 @@ This tool applies targeted changes to existing files using fuzzy matching guided
 
 ## When is it used?
 
-- When Roo needs to make precise changes to existing code without rewriting entire files.
+- When Zoo needs to make precise changes to existing code without rewriting entire files.
 - When refactoring specific sections of code while maintaining surrounding context.
 - When fixing bugs in existing code with surgical precision.
 - When implementing feature enhancements that modify only certain parts of a file.

@@ -1,12 +1,12 @@
 ---
-description: Apply unified diff patches to multiple files in a single operation using the apply_patch tool in Roo Code.
+description: Apply unified diff patches to multiple files in a single operation using the apply_patch tool in Zoo Code.
 keywords:
   - apply_patch
   - patch
   - unified diff
   - multi-file edits
   - file operations
-  - Roo Code tools
+  - Zoo Code tools
   - diff patches
 ---
 

@@ -1,10 +1,10 @@
 ---
-description: Enable interactive communication in Roo Code with the ask_followup_question tool for gathering clarification and user preferences.
+description: Enable interactive communication in Zoo Code with the ask_followup_question tool for gathering clarification and user preferences.
 keywords:
   - ask_followup_question
   - user interaction
   - interactive communication
-  - Roo Code tools
+  - Zoo Code tools
   - clarification
   - user feedback
 ---
@@ -26,16 +26,16 @@ The tool accepts these parameters:
 
 ## What It Does
 
-This tool creates a conversational interface between Roo and the user, allowing for gathering clarification, additional details, or user preferences when facing ambiguities or decision points. Each question can include suggested responses to streamline the interaction.
+This tool creates a conversational interface between Zoo and the user, allowing for gathering clarification, additional details, or user preferences when facing ambiguities or decision points. Each question can include suggested responses to streamline the interaction.
 
 ---
 
 ## When is it used?
 
 - When critical information is missing from the original request
-- When Roo needs to choose between multiple valid implementation approaches
+- When Zoo needs to choose between multiple valid implementation approaches
 - When technical details or preferences are required to proceed
-- When Roo encounters ambiguities that need resolution
+- When Zoo encounters ambiguities that need resolution
 - When additional context would significantly improve the solution quality
 
 ---
@@ -113,9 +113,9 @@ When the `ask_followup_question` tool is invoked, it follows this process:
 
 The question-answer cycle follows this sequence:
 
-1. **Information Gap Recognition**: Roo identifies missing information needed to proceed
-2. **Specific Question Creation**: Roo formulates a clear, targeted question
-3. **Suggestion Development**: Roo creates relevant suggested answers (optional but recommended)
+1. **Information Gap Recognition**: Zoo identifies missing information needed to proceed
+2. **Specific Question Creation**: Zoo formulates a clear, targeted question
+3. **Suggestion Development**: Zoo creates relevant suggested answers (optional but recommended)
 4. **Tool Invocation**: Assistant invokes the tool with question and optional suggestions
 5. **UI Presentation**: Question and suggestions are displayed to the user as interactive elements
 6. **User Response**: The user selects a suggestion or provides a custom answer
@@ -125,18 +125,18 @@ The question-answer cycle follows this sequence:
    - Maintains state consistency regardless of message chunking
 8. **Response Processing**: System wraps the response in `<answer>` tags and preserves images
 9. **Context Integration**: Response is added to the conversation history
-10. **Task Continuation**: Roo proceeds with the task using the new information
+10. **Task Continuation**: Zoo proceeds with the task using the new information
 
 ---
 
 ## Examples When Used
 
-- When developing a web application, Roo might ask about preferred styling frameworks (Bootstrap, Tailwind, custom CSS)
-- When creating an API, Roo might ask about authentication methods (JWT, OAuth, API keys)
-- When refactoring code, Roo might ask about prioritizing performance vs. readability
-- When setting up a database, Roo might ask about specific schema design preferences
-- When creating a custom feature, Roo might ask about specific behavior expectations
-- When troubleshooting errors, Roo might ask about specific environment details
+- When developing a web application, Zoo might ask about preferred styling frameworks (Bootstrap, Tailwind, custom CSS)
+- When creating an API, Zoo might ask about authentication methods (JWT, OAuth, API keys)
+- When refactoring code, Zoo might ask about prioritizing performance vs. readability
+- When setting up a database, Zoo might ask about specific schema design preferences
+- When creating a custom feature, Zoo might ask about specific behavior expectations
+- When troubleshooting errors, Zoo might ask about specific environment details
 
 ---
 

@@ -1,10 +1,10 @@
 ---
-description: Learn how the attempt_completion tool signals task completion, presents results, and enables iterative refinement in Roo Code.
+description: Learn how the attempt_completion tool signals task completion, presents results, and enables iterative refinement in Zoo Code.
 keywords:
   - attempt_completion
   - task completion
   - result presentation
-  - Roo Code tools
+  - Zoo Code tools
   - user feedback
   - task summary
 ---

@@ -5,7 +5,7 @@ keywords:
   - semantic search
   - AI embeddings
   - code search
-  - Roo Code tools
+  - Zoo Code tools
   - vector search
   - Qdrant
 ---

@@ -1,11 +1,11 @@
 ---
-description: Replace a uniquely-identified occurrence of text in files using the edit_file search-and-replace tool in Roo Code.
+description: Replace a uniquely-identified occurrence of text in files using the edit_file search-and-replace tool in Zoo Code.
 keywords:
   - edit_file
   - search and replace
   - file editing
   - text replacement
-  - Roo Code tools
+  - Zoo Code tools
   - code modifications
 ---
 

@@ -1,11 +1,11 @@
 ---
-description: Replace the first or all occurrences of text using the edit search-and-replace tool in Roo Code.
+description: Replace the first or all occurrences of text using the edit search-and-replace tool in Zoo Code.
 keywords:
   - edit
   - search and replace
   - file editing
   - text replacement
-  - Roo Code tools
+  - Zoo Code tools
   - code modifications
 ---
 

@@ -1,11 +1,11 @@
 ---
-description: Execute terminal commands in Roo Code for system operations, dependency installation, builds, and development workflows.
+description: Execute terminal commands in Zoo Code for system operations, dependency installation, builds, and development workflows.
 keywords:
   - execute_command
   - CLI commands
   - terminal
   - system operations
-  - Roo Code tools
+  - Zoo Code tools
   - command execution
   - shell integration
 ---

@@ -1,12 +1,12 @@
 ---
-description: Generate or edit images using AI models through the generate_image tool in Roo Code.
+description: Generate or edit images using AI models through the generate_image tool in Zoo Code.
 keywords:
   - generate_image
   - AI images
   - image generation
   - image editing
   - OpenRouter
-  - Roo Code tools
+  - Zoo Code tools
   - experimental
 ---
 

@@ -1,8 +1,8 @@
 ---
-description: Learn how the list_files tool helps Roo Code explore project structures, list directories, and navigate codebases with recursive and filtered listing capabilities.
+description: Learn how the list_files tool helps Zoo Code explore project structures, list directories, and navigate codebases with recursive and filtered listing capabilities.
 keywords:
   - list_files
-  - Roo Code tools
+  - Zoo Code tools
   - directory listing
   - file exploration
   - project structure