Add Roo Code output

Add a generated Roo Code workspace output with project MCP configuration, Roo rules, AGENTS.md guidance, shared skills, and verification coverage.

Author: chubes4

README.md

@@ -2,7 +2,7 @@
 
 Shared source for WordPress-focused agent skills and plugin packaging.
 
-This repo currently packages shared skills for Codex, Claude Code, Cursor, GitHub Copilot, and Gemini as separate plugin outputs:
+This repo currently packages shared skills for Codex, Claude Code, Cursor, GitHub Copilot, Gemini, and Roo Code as separate plugin outputs:
 
 - prefers the WordPress Studio MCP server for site management, screenshots, and block validation
 - falls back to the Studio CLI through a shared Studio skill when MCP is unavailable
@@ -14,6 +14,7 @@ This repo currently packages shared skills for Codex, Claude Code, Cursor, GitHu
 - can optionally generate three design preview directions before building a site theme
 - bundles a plugin-local telemetry MCP server so workflow events do not depend on Studio shipping telemetry support
 - keeps skills shared so other surfaces can reuse them later
+- adds Roo Code workspace rules and project MCP config without introducing a Roo-specific backend service
 
 ## Testing
 
@@ -60,6 +61,20 @@ claude --plugin-dir ./plugins/claude-code
    - running an audit request
 6. For workflow telemetry coverage, make sure the generated `wordpress-telemetry` MCP server starts alongside `wordpress-studio`.
 
+### Test in Roo Code
+
+1. Install the Roo Code VS Code extension.
+2. Open `./plugins/roo-code` as the VS Code workspace root, or copy that folder's contents into a target workspace root.
+3. Confirm the generated workspace rules exist at `plugins/roo-code/.roo/rules/wordpress-com.md` and `plugins/roo-code/.roo/rules-code/wordpress-com-code.md`.
+4. Confirm the generated project MCP config exists at `plugins/roo-code/.roo/mcp.json`.
+5. In Roo Code, enable MCP servers and confirm `wordpress-studio` and `wordpress-telemetry` are available.
+6. Try the same representative tasks:
+   - creating a new site
+   - building or editing a theme
+   - creating a custom block
+    - creating a custom plugin
+    - running an audit request
+
 ### Test in GitHub Copilot
 
 1. Copy or open `./plugins/copilot` as the project root in VS Code.
@@ -104,6 +119,7 @@ claude --plugin-dir ./plugins/claude-code
 - Codex packaging output in `plugins/codex/`
 - Claude Code packaging output in `plugins/claude-code/`
 - Cursor packaging output in `plugins/cursor/`
+- Roo Code workspace output in `plugins/roo-code/`
 - Gemini packaging output in `plugins/gemini/`
 - GitHub Copilot packaging output in `plugins/copilot/`
 - Bundled telemetry artifact in `dist/`
@@ -119,6 +135,7 @@ The build packages the shared skills into:
 - `plugins/codex/plugins/wordpress-studio/skills/`
 - `plugins/claude-code/skills/`
 - `plugins/cursor/skills/`
+- `plugins/roo-code/skills/`
 - `plugins/gemini/skills/`
 - `plugins/copilot/skills/`
 
@@ -127,6 +144,7 @@ It also generates plugin-specific MCP configs for each surface:
 - Codex: `plugins/codex/plugins/wordpress-studio/.mcp.json`
 - Claude Code: `plugins/claude-code/.mcp.json`
 - Cursor: `plugins/cursor/mcp.json`
+- Roo Code: `plugins/roo-code/.roo/mcp.json`
 - Gemini: `plugins/gemini/.gemini/settings.json`
 - GitHub Copilot: `plugins/copilot/.vscode/mcp.json`
 
@@ -232,3 +250,21 @@ That folder currently contains:
 - `README.md`
 
 The generated Gemini MCP config launches both `studio mcp` and the bundled `wordpress-telemetry` MCP server. `GEMINI.md` is the project-level instruction file for Gemini CLI and Gemini Code Assist workflows.
+
+The Roo Code workspace output is generated to:
+
+```text
+plugins/roo-code/
+```
+
+That folder currently contains:
+
+- `.roo/mcp.json`
+- `.roo/rules/wordpress-com.md`
+- `.roo/rules-code/wordpress-com-code.md`
+- `AGENTS.md`
+- `scripts/wordpress-telemetry-mcp.mjs`
+- `skills/`
+- `README.md`
+
+The generated Roo Code project MCP config launches both `studio mcp` and the bundled `wordpress-telemetry` MCP server. The `.roo/rules/` files are Roo-specific; the WordPress.com MCP and skill behavior is shared with the other outputs.

plugins/claude-code/skills/auditing/SKILL.md

@@ -106,7 +106,7 @@ Focus on issues this repo can realistically help with:
 - readability issues caused by font size, line height, or dense layouts
 - color choices that make important information hard to distinguish
 
-When the issue is visual, prefer `take_screenshot`-backed observations. Use `inspect_design` when the rendered DOM or computed styles would identify the root cause faster than code inspection alone.
+When the issue is visual, prefer `take_screenshot`-backed observations. Use `inspect_design` when the rendered DOM or computed styles would identify the root cause faster than code inspection.
 
 When the issue appears structural, inspect the relevant theme or plugin files before recommending a fix.
 

plugins/claude-code/skills/theme-creator/SKILL.md

@@ -21,7 +21,6 @@ Use `studio` for the review loop after making changes. Use `auditing` when the u
 ## Principles
 
 - Build block themes, not classic themes.
-- Use `scaffold_theme` when starting a new custom theme, then fill in design-specific templates, parts, and styles.
 - Use modern WordPress patterns: `theme.json`, template parts, templates, core blocks.
 - Prefer CSS and block composition over raw HTML blocks.
 - Keep the theme editable in the Site Editor.

plugins/codex/plugins/wordpress-studio/skills/auditing/SKILL.md

@@ -106,7 +106,7 @@ Focus on issues this repo can realistically help with:
 - readability issues caused by font size, line height, or dense layouts
 - color choices that make important information hard to distinguish
 
-When the issue is visual, prefer `take_screenshot`-backed observations. Use `inspect_design` when the rendered DOM or computed styles would identify the root cause faster than code inspection alone.
+When the issue is visual, prefer `take_screenshot`-backed observations. Use `inspect_design` when the rendered DOM or computed styles would identify the root cause faster than code inspection.
 
 When the issue appears structural, inspect the relevant theme or plugin files before recommending a fix.
 

plugins/codex/plugins/wordpress-studio/skills/theme-creator/SKILL.md

@@ -21,7 +21,6 @@ Use `studio` for the review loop after making changes. Use `auditing` when the u
 ## Principles
 
 - Build block themes, not classic themes.
-- Use `scaffold_theme` when starting a new custom theme, then fill in design-specific templates, parts, and styles.
 - Use modern WordPress patterns: `theme.json`, template parts, templates, core blocks.
 - Prefer CSS and block composition over raw HTML blocks.
 - Keep the theme editable in the Site Editor.

plugins/copilot/skills/auditing/SKILL.md

@@ -106,7 +106,7 @@ Focus on issues this repo can realistically help with:
 - readability issues caused by font size, line height, or dense layouts
 - color choices that make important information hard to distinguish
 
-When the issue is visual, prefer `take_screenshot`-backed observations. Use `inspect_design` when the rendered DOM or computed styles would identify the root cause faster than code inspection alone.
+When the issue is visual, prefer `take_screenshot`-backed observations. Use `inspect_design` when the rendered DOM or computed styles would identify the root cause faster than code inspection.
 
 When the issue appears structural, inspect the relevant theme or plugin files before recommending a fix.
 

plugins/copilot/skills/theme-creator/SKILL.md

@@ -21,7 +21,6 @@ Use `studio` for the review loop after making changes. Use `auditing` when the u
 ## Principles
 
 - Build block themes, not classic themes.
-- Use `scaffold_theme` when starting a new custom theme, then fill in design-specific templates, parts, and styles.
 - Use modern WordPress patterns: `theme.json`, template parts, templates, core blocks.
 - Prefer CSS and block composition over raw HTML blocks.
 - Keep the theme editable in the Site Editor.

plugins/cursor/skills/auditing/SKILL.md

@@ -106,7 +106,7 @@ Focus on issues this repo can realistically help with:
 - readability issues caused by font size, line height, or dense layouts
 - color choices that make important information hard to distinguish
 
-When the issue is visual, prefer `take_screenshot`-backed observations. Use `inspect_design` when the rendered DOM or computed styles would identify the root cause faster than code inspection alone.
+When the issue is visual, prefer `take_screenshot`-backed observations. Use `inspect_design` when the rendered DOM or computed styles would identify the root cause faster than code inspection.
 
 When the issue appears structural, inspect the relevant theme or plugin files before recommending a fix.
 

plugins/cursor/skills/theme-creator/SKILL.md

@@ -21,7 +21,6 @@ Use `studio` for the review loop after making changes. Use `auditing` when the u
 ## Principles
 
 - Build block themes, not classic themes.
-- Use `scaffold_theme` when starting a new custom theme, then fill in design-specific templates, parts, and styles.
 - Use modern WordPress patterns: `theme.json`, template parts, templates, core blocks.
 - Prefer CSS and block composition over raw HTML blocks.
 - Keep the theme editable in the Site Editor.

plugins/gemini/skills/auditing/SKILL.md

@@ -106,7 +106,7 @@ Focus on issues this repo can realistically help with:
 - readability issues caused by font size, line height, or dense layouts
 - color choices that make important information hard to distinguish
 
-When the issue is visual, prefer `take_screenshot`-backed observations. Use `inspect_design` when the rendered DOM or computed styles would identify the root cause faster than code inspection alone.
+When the issue is visual, prefer `take_screenshot`-backed observations. Use `inspect_design` when the rendered DOM or computed styles would identify the root cause faster than code inspection.
 
 When the issue appears structural, inspect the relevant theme or plugin files before recommending a fix.