Add Windsurf Cascade output

README.md

@@ -2,7 +2,7 @@
 
 Shared source for WordPress-focused agent skills and plugin packaging.
 
-This repo currently packages shared skills and setup files for Codex, Claude Code, Cursor, Continue, GitHub Copilot, Gemini, and Roo Code as separate outputs:
+This repo currently packages shared skills and setup files for Codex, Claude Code, Cursor, Continue, GitHub Copilot, Gemini, Roo Code, and Windsurf/Cascade as separate 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
@@ -16,6 +16,7 @@ This repo currently packages shared skills and setup files for Codex, Claude Cod
 - keeps skills shared so other surfaces can reuse them later
 - includes Continue-native setup files for WordPress.com rules, prompts, and MCP configuration
 - adds Roo Code workspace rules and project MCP config without introducing a Roo-specific backend service
+- adds Windsurf/Cascade workspace rules and MCP config without introducing a Windsurf-specific backend service
 
 ## Testing
 
@@ -117,6 +118,17 @@ claude --plugin-dir ./plugins/claude-code
 3. In Continue, copy the `.continue/` examples into a project or merge the `config.yaml` MCP snippet into `~/.continue/config.yaml`.
 4. Use Continue Agent mode for WordPress.com MCP tool access.
 
+### Test in Windsurf/Cascade
+
+1. Install Devin Desktop / Windsurf and complete onboarding.
+2. Build the generated output with `pnpm build`.
+3. Confirm the generated Cascade rules exist at `plugins/windsurf/.devin/rules/`.
+4. Confirm the generated MCP config exists at `plugins/windsurf/mcp_config.json`.
+5. Confirm the bundled telemetry server exists at `plugins/windsurf/scripts/wordpress-telemetry-mcp.mjs`.
+6. Copy the servers from `plugins/windsurf/mcp_config.json` into `~/.codeium/windsurf/mcp_config.json`.
+7. In Cascade MCP settings, confirm `wordpress-studio` and `wordpress-telemetry` are enabled.
+8. Try representative WordPress.com tasks such as site review, theme edits, block validation, or plugin planning.
+
 ## Current scope
 
 - Shared skills for:
@@ -137,6 +149,7 @@ claude --plugin-dir ./plugins/claude-code
 - Roo Code workspace output in `plugins/roo-code/`
 - Gemini packaging output in `plugins/gemini/`
 - GitHub Copilot packaging output in `plugins/copilot/`
+- Windsurf/Cascade workspace output in `plugins/windsurf/`
 - Bundled telemetry artifact in `dist/`
 - `pnpm` scripts for build and verification
 
@@ -153,6 +166,7 @@ The build packages the shared skills into:
 - `plugins/roo-code/skills/`
 - `plugins/gemini/skills/`
 - `plugins/copilot/skills/`
+- `plugins/windsurf/skills/`
 
 It also generates plugin-specific MCP configs for each surface:
 
@@ -163,6 +177,7 @@ It also generates plugin-specific MCP configs for each surface:
 - Roo Code: `plugins/roo-code/.roo/mcp.json`
 - Gemini: `plugins/gemini/.gemini/settings.json`
 - GitHub Copilot: `plugins/copilot/.vscode/mcp.json`
+- Windsurf/Cascade: `plugins/windsurf/mcp_config.json`
 
 The telemetry server source lives in `scripts/wordpress-telemetry-mcp.mjs` and is bundled to:
 

plugins/windsurf/.devin/rules/wordpress-com-mcp.md

@@ -0,0 +1,12 @@
+---
+trigger: model_decision
+description: Use when configuring or troubleshooting Cascade MCP access for WordPress.com and Jetpack-connected sites.
+---
+
+# WordPress.com MCP
+
+- Cascade reaches WordPress.com through the existing WordPress.com / Jetpack MCP flow exposed by the configured `wordpress-studio` MCP server.
+- Do not create a new backend service for WordPress.com access.
+- Keep the `wordpress-studio` server enabled for site operations, screenshots, block validation, audits, and WP-CLI access.
+- Keep the `wordpress-telemetry` server enabled when workflow telemetry is needed.
+- If Cascade cannot see WordPress.com tools, check Cascade MCP settings and the user's `~/.codeium/windsurf/mcp_config.json` file.

plugins/windsurf/.devin/rules/wordpress-com.md

@@ -0,0 +1,12 @@
+---
+trigger: always_on
+---
+
+# WordPress.com
+
+- Treat this workspace as a WordPress.com-aware build environment.
+- Use the configured WordPress.com MCP tools before falling back to shell or manual WordPress operations.
+- Prefer the smallest fitting WordPress abstraction: existing blocks first, then theme work, custom blocks, and plugins only when reusable functionality is required.
+- Keep user-facing product text as WordPress.com.
+- Ask for the target site only when the available MCP context does not identify it.
+- Verify WordPress work through MCP-backed screenshots, block validation, audits, or WP-CLI commands when those tools are available.

plugins/windsurf/README.md

@@ -0,0 +1,51 @@
+# WordPress.com for Windsurf Cascade
+
+This Windsurf/Cascade output packages the shared WordPress agent substrate from the `build-with-wordpress` source repo for WordPress.com work.
+
+## What is Windsurf-specific
+
+- Cascade rules live in `.devin/rules/*.md`, which the official docs list as the preferred workspace rule location.
+- `mcp_config.json` is shaped for Cascade's MCP configuration file at `~/.codeium/windsurf/mcp_config.json`.
+- The rules tell Cascade when to use WordPress.com MCP tools and how to route WordPress implementation work.
+
+## What is shared
+
+- The WordPress.com MCP path uses the existing `wordpress-studio` MCP server; this output does not add a new backend service.
+- Jetpack-connected site access stays part of the existing WordPress.com / Jetpack MCP flow.
+- The bundled `wordpress-telemetry` MCP server is the same repo-local telemetry server used by the other outputs.
+- Shared WordPress skills are copied into `skills/` so routing, Studio-backed workflows, auditing, theme, block, and plugin guidance stay aligned across agent surfaces.
+
+## Setup
+
+1. Install Devin Desktop / Windsurf and complete onboarding.
+2. Optionally install the `windsurf` command in `PATH` during onboarding.
+3. Build this repo with `pnpm build`.
+4. Copy the servers from `plugins/windsurf/mcp_config.json` into `~/.codeium/windsurf/mcp_config.json`.
+5. In Cascade MCP settings, confirm both servers are enabled:
+   - `wordpress-studio`
+   - `wordpress-telemetry`
+6. Open this output folder or copy `.devin/rules/` into the workspace where Cascade should be WordPress.com-aware.
+7. Ask Cascade for a WordPress.com site task and confirm it uses MCP tools before shell fallbacks.
+
+## Included Cascade rules
+
+- `.devin/rules/wordpress-com.md`: always-on WordPress.com routing and product guidance.
+- `.devin/rules/wordpress-com-mcp.md`: model-decision MCP setup and troubleshooting guidance.
+
+## Official references
+
+- Rules and memories: https://docs.windsurf.com/windsurf/cascade/memories
+- MCP configuration: https://docs.windsurf.com/windsurf/cascade/mcp
+- AGENTS.md discovery: https://docs.devin.ai/desktop/cascade/agents-md
+- Installation and onboarding: https://docs.windsurf.com/windsurf/getting-started
+
+## Included shared skills
+
+- `auditing`
+- `block-creator`
+- `design-previews-creator`
+- `plugin-creator`
+- `site-creator`
+- `studio`
+- `theme-creator`
+- `wordpress-creator`