Merge pull request #1 from Zoo-Code-Org/roo-to-zoo

Author: hannesrudolph

.roo/rules-ask/AGENTS.md

@@ -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).

.roo/rules-documentation-writer/1_writing_style.xml

@@ -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>

.roo/rules-documentation-writer/2_docusaurus_conventions.xml

@@ -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>
 

.roo/rules-release-notes-writer/1_main_workflow.xml

@@ -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>

.roo/rules-release-notes-writer/2_content_standards.xml

@@ -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)

.roo/rules-release-notes-writer/3_user_interactions.xml

@@ -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>

.roomodes

@@ -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",

.roorules

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

README.md

@@ -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
 

docs/advanced-usage/available-tools/access-mcp-resource.md

@@ -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.
 
 ---