Add Continue output (#12)

* Add Continue output

* Revert "Update generated skills from shared Studio guidance"

This reverts commit d02642d, reversing
changes made to 4ccad40.

* Repair Continue plugin branch after trunk merge

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, Gemini, and Roo Code as separate plugin outputs:
+This repo currently packages shared skills and setup files for Codex, Claude Code, Cursor, Continue, GitHub Copilot, Gemini, and Roo Code 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
@@ -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
+- 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
 
 ## Testing
@@ -103,6 +104,19 @@ 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 Continue
+
+1. Review the generated Continue output in `./plugins/continue`.
+2. Confirm the generated setup files exist:
+   - `plugins/continue/README.md`
+   - `plugins/continue/config.yaml`
+   - `plugins/continue/.continue/rules/wordpress-com.md`
+   - `plugins/continue/.continue/prompts/create-wordpress-com-site.md`
+   - `plugins/continue/.continue/prompts/audit-wordpress-com-project.md`
+   - `plugins/continue/.continue/mcpServers/wordpress-com.yaml`
+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.
+
 ## Current scope
 
 - Shared skills for:
@@ -119,6 +133,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/`
+- Continue setup output in `plugins/continue/`
 - Roo Code workspace output in `plugins/roo-code/`
 - Gemini packaging output in `plugins/gemini/`
 - GitHub Copilot packaging output in `plugins/copilot/`
@@ -144,6 +159,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`
+- Continue: `plugins/continue/.continue/mcpServers/wordpress-com.yaml`
 - Roo Code: `plugins/roo-code/.roo/mcp.json`
 - Gemini: `plugins/gemini/.gemini/settings.json`
 - GitHub Copilot: `plugins/copilot/.vscode/mcp.json`
@@ -233,6 +249,25 @@ That folder currently contains:
 - `skills/`
 - `README.md`
 
+The generated Cursor MCP config launches both `studio mcp` and the bundled `wordpress-telemetry` MCP server.
+
+The Continue setup output is generated to:
+
+```text
+plugins/continue/
+```
+
+That folder currently contains:
+
+- `README.md`
+- `config.yaml`
+- `.continue/rules/wordpress-com.md`
+- `.continue/prompts/create-wordpress-com-site.md`
+- `.continue/prompts/audit-wordpress-com-project.md`
+- `.continue/mcpServers/wordpress-com.yaml`
+
+The generated Continue MCP guidance uses the same existing `studio mcp` entrypoint as the shared WordPress.com MCP substrate. Continue-specific files cover rules, prompts, and MCP block placement; they do not define a separate backend service.
+
 The generated Copilot MCP config launches both `studio mcp` and the bundled `wordpress-telemetry` MCP server through VS Code's MCP configuration.
 
 The Gemini plugin is generated to:

plugins/continue/.continue/mcpServers/wordpress-com.yaml

@@ -0,0 +1,9 @@
+name: WordPress.com MCP
+version: 0.0.1
+schema: v1
+mcpServers:
+  - name: WordPress.com MCP
+    type: stdio
+    command: studio
+    args:
+      - mcp

plugins/continue/.continue/prompts/audit-wordpress-com-project.md

@@ -0,0 +1,20 @@
+---
+name: Audit WordPress.com project
+description: Review a WordPress.com project for implementation, accessibility, performance, and editing quality.
+invokable: true
+---
+
+# Audit WordPress.com Project
+
+Review the selected WordPress.com project or change set.
+
+Focus on:
+
+- correctness and regressions
+- block validity and editor compatibility
+- accessibility
+- responsive behavior
+- frontend performance
+- maintainability and WordPress conventions
+
+Use the configured WordPress.com MCP tools when available. Report findings first, ordered by severity, with file or tool evidence where possible.

plugins/continue/.continue/prompts/create-wordpress-com-site.md

@@ -0,0 +1,15 @@
+---
+name: Create WordPress.com site
+description: Plan and build a WordPress.com site change using Continue and MCP tools.
+invokable: true
+---
+
+# Create WordPress.com Site Work
+
+Use Continue Agent mode and the configured WordPress.com MCP tools to help create or update a WordPress.com site.
+
+1. Inspect the current project and available WordPress.com MCP tools.
+2. Identify whether the task is best handled with blocks, a theme, a plugin, content edits, or site settings.
+3. Make the smallest complete implementation that matches the existing project conventions.
+4. Validate the result with available WordPress.com MCP tools, screenshots, block validation, WP-CLI, or project tests.
+5. Summarize what changed, what was verified, and any remaining manual review steps.

plugins/continue/.continue/rules/wordpress-com.md

@@ -0,0 +1,15 @@
+---
+name: WordPress.com
+alwaysApply: true
+description: WordPress.com guidance for Continue Agent, Chat, and Edit requests.
+---
+
+# WordPress.com
+
+- Use the product name WordPress.com in user-facing text.
+- Prefer the WordPress.com and Jetpack MCP tools for site discovery, site changes, screenshots, validation, and WordPress operations when they are available.
+- Use Continue Agent mode for tasks that need MCP tools.
+- Preserve existing project conventions and make the smallest complete change.
+- For themes, blocks, plugins, and content changes, inspect the current WordPress project structure before editing.
+- Use WordPress APIs, Gutenberg block markup, and WP-CLI-compatible operations instead of custom one-off storage or service layers.
+- Explain whether a recommendation depends on Continue configuration or the shared WordPress.com MCP substrate.

plugins/continue/README.md

@@ -0,0 +1,44 @@
+# WordPress.com for Continue
+
+This output shows how to configure the Continue IDE assistant for WordPress.com work using Continue-native configuration files.
+
+Continue does not install this repository as a plugin. Instead, copy the example files into your Continue workspace or user configuration:
+
+- `.continue/rules/wordpress-com.md` contains WordPress.com instructions for Agent, Chat, and Edit modes
+- `.continue/prompts/create-wordpress-com-site.md` adds a reusable slash-command prompt for new site work
+- `.continue/prompts/audit-wordpress-com-project.md` adds a reusable slash-command prompt for review work
+- `.continue/mcpServers/wordpress-com.yaml` shows the MCP server block Continue can load in Agent mode
+- `config.yaml` shows the equivalent user-level `~/.continue/config.yaml` snippet
+
+## Setup
+
+1. Install Continue in VS Code or JetBrains.
+2. Copy the example `.continue/` directory from this folder into the root of the project you want Continue to help with.
+3. Open Continue's local config at `~/.continue/config.yaml` and merge in the relevant parts of `config.yaml` if you prefer user-level configuration.
+4. Keep using the existing WordPress.com and Jetpack MCP flow. The example MCP block launches `studio mcp`, matching the shared WordPress.com MCP substrate used by the other outputs in this repository. If your environment exposes the WordPress.com or Jetpack MCP bridge through a different command, replace only the `command` and `args` values with that existing entrypoint.
+5. Use Continue Agent mode when you need MCP tools; Continue exposes MCP tools to Agent mode.
+
+## Continue-specific pieces
+
+These files are specific to Continue:
+
+- local rule files under `.continue/rules/`
+- local prompt files under `.continue/prompts/` with `invokable: true`
+- local MCP server blocks under `.continue/mcpServers/`
+- optional user-level `~/.continue/config.yaml` snippets
+
+## Shared WordPress.com substrate
+
+The WordPress.com behavior remains shared across agent surfaces:
+
+- WordPress.com and Jetpack access comes from the existing MCP flow, not a Continue-only backend
+- site management, WordPress operations, and Jetpack-connected tools should use that MCP substrate when available
+- implementation guidance stays aligned with the shared WordPress skills in this repository
+- Continue contributes the IDE-specific packaging format around the same WordPress.com workflow
+
+## Continue references
+
+- Configuration: https://docs.continue.dev/customize/deep-dives/configuration
+- Rules: https://docs.continue.dev/customize/deep-dives/rules
+- Prompts: https://docs.continue.dev/customize/deep-dives/prompts
+- MCP tools: https://docs.continue.dev/customize/deep-dives/mcp

plugins/continue/config.yaml

@@ -0,0 +1,22 @@
+# Merge the relevant sections into ~/.continue/config.yaml.
+# Continue also loads project-local files from .continue/rules,
+# .continue/prompts, and .continue/mcpServers when they are present in a workspace.
+
+name: WordPress.com
+version: 0.0.1
+schema: v1
+
+# Project-local rule and prompt files can stay in .continue/rules and
+# .continue/prompts. If you publish them to Continue Hub, reference them here:
+# rules:
+#   - uses: your-org/wordpress-com
+# prompts:
+#   - uses: your-org/create-wordpress-com-site
+#   - uses: your-org/audit-wordpress-com-project
+
+mcpServers:
+  - name: WordPress.com MCP
+    type: stdio
+    command: studio
+    args:
+      - mcp