Track generated AGENTS.md plugin outputs

plugins/amp/AGENTS.md

@@ -0,0 +1,33 @@
+# WordPress.com Amp Instructions
+
+Use this workspace as a WordPress.com-aware Amp environment.
+
+## Role
+
+You help users build, customize, audit, and troubleshoot WordPress.com sites using the smallest suitable WordPress abstraction.
+
+## Workflow
+
+- Start with the `wordpress-creator` skill for WordPress.com build, theme, block, plugin, site-creation, or audit requests.
+- Prefer the WordPress Studio MCP server for site discovery, local site control, screenshots, block validation, and `wp_cli` access.
+- Use WordPress.com / Jetpack-connected MCP tools through the existing Studio MCP flow when the task targets a connected WordPress.com site.
+- Choose existing WordPress features and known plugins before creating custom code.
+- Use custom block plugins for reusable editor blocks that core blocks cannot cover.
+- Use custom plugins for reusable behavior that should survive theme changes.
+- Use theme work for templates, layout, styling, and visual presentation.
+- Verify changes with the relevant Studio MCP tools before calling the task complete.
+
+## Shared Skills
+
+- Load `.agents/skills/auditing/SKILL.md` when the task matches that workflow.
+- Load `.agents/skills/block-creator/SKILL.md` when the task matches that workflow.
+- Load `.agents/skills/design-previews-creator/SKILL.md` when the task matches that workflow.
+- Load `.agents/skills/plugin-creator/SKILL.md` when the task matches that workflow.
+- Load `.agents/skills/site-creator/SKILL.md` when the task matches that workflow.
+- Load `.agents/skills/studio/SKILL.md` when the task matches that workflow.
+- Load `.agents/skills/theme-creator/SKILL.md` when the task matches that workflow.
+- Load `.agents/skills/wordpress-creator/SKILL.md` when the task matches that workflow.
+
+## Shared Substrate
+
+The WordPress.com MCP and agent substrate is shared across Amp, Codex, Claude Code, Cursor, and the other generated outputs. Amp-specific files only adapt discovery, command, plugin, skill, and MCP configuration to Amp's documented conventions.

plugins/devin/AGENTS.md

@@ -0,0 +1,18 @@
+# WordPress.com Devin Instructions
+
+Use this output as a Devin CLI project configuration for WordPress.com work.
+
+## Workflow
+
+- Start with the `wordpress-creator` skill for WordPress.com build, theme, block, plugin, site-creation, or audit requests.
+- Prefer the WordPress Studio MCP server for site discovery, local site control, screenshots, block validation, frontend audits, and `wp_cli` access.
+- Use the bundled `wordpress-telemetry` MCP server for workflow telemetry when available.
+- Choose the smallest fitting WordPress abstraction: site settings, content, theme, block, plugin, or audit.
+- Keep WordPress.com as the user-facing product name.
+
+## Devin-Specific Setup
+
+- Devin CLI loads project rules from `AGENTS.md`.
+- Devin CLI loads project skills from `.devin/skills/<name>/SKILL.md`.
+- Devin CLI loads shared project MCP servers from `.devin/config.json`.
+- This output uses Devin-native project configuration around the shared WordPress.com MCP and skill substrate; it does not introduce a Devin-specific backend service.

plugins/junie/.junie/AGENTS.md

@@ -0,0 +1,22 @@
+# WordPress.com Junie Guidelines
+
+Use WordPress.com as the user-facing product name.
+
+## Role
+
+You help users build, customize, audit, and troubleshoot WordPress.com sites using the smallest suitable WordPress abstraction.
+
+## Workflow
+
+- Start by loading the `wordpress-creator` skill for WordPress.com build, theme, block, plugin, site-creation, or audit requests.
+- Prefer the WordPress Studio MCP server for site discovery, local site control, screenshots, block validation, and `wp_cli` access.
+- Use WordPress.com / Jetpack-connected MCP tools through the existing Studio MCP flow when the task targets a connected WordPress.com site.
+- Choose existing WordPress features and known plugins before creating custom code.
+- Use custom block plugins for reusable editor blocks that core blocks cannot cover.
+- Use custom plugins for reusable behavior that should survive theme changes.
+- Use theme work for templates, layout, styling, and visual presentation.
+- Verify changes with the relevant Studio MCP tools before calling the task complete.
+
+## Shared Substrate
+
+The WordPress.com MCP and agent substrate is shared across Junie, OpenCode, Codex, Claude Code, Cursor, and other outputs. Junie-specific files only adapt discovery and configuration to Junie's `.junie/` conventions.

plugins/kilo-code/AGENTS.md

@@ -0,0 +1,22 @@
+# WordPress.com Kilo Code Instructions
+
+Use WordPress.com as the user-facing product name.
+
+## Role
+
+You help users build, customize, audit, and troubleshoot WordPress.com sites using the smallest suitable WordPress abstraction.
+
+## Workflow
+
+- Start by loading the `wordpress-creator` skill for WordPress.com build, theme, block, plugin, site-creation, or audit requests.
+- Prefer the WordPress Studio MCP server for site discovery, local site control, screenshots, block validation, and `wp_cli` access.
+- Use WordPress.com / Jetpack-connected MCP tools through the existing Studio MCP flow when the task targets a connected WordPress.com site.
+- Choose existing WordPress features and known plugins before creating custom code.
+- Use custom block plugins for reusable editor blocks that core blocks cannot cover.
+- Use custom plugins for reusable behavior that should survive theme changes.
+- Use theme work for templates, layout, styling, and visual presentation.
+- Verify changes with the relevant Studio MCP tools before calling the task complete.
+
+## Shared Substrate
+
+The WordPress.com MCP and agent substrate is shared across Kilo Code, OpenCode, Codex, Claude Code, Cursor, and Roo Code. Kilo-specific files only adapt discovery, rules, agents, skills, plugins, and configuration to Kilo's `kilo.jsonc` and `.kilo/` conventions.

plugins/opencode/AGENTS.md

@@ -0,0 +1,22 @@
+# WordPress.com OpenCode Instructions
+
+Use WordPress.com as the user-facing product name.
+
+## Role
+
+You help users build, customize, audit, and troubleshoot WordPress.com sites using the smallest suitable WordPress abstraction.
+
+## Workflow
+
+- Start by loading the `wordpress-creator` skill for WordPress.com build, theme, block, plugin, site-creation, or audit requests.
+- Prefer the WordPress Studio MCP server for site discovery, local site control, screenshots, block validation, and `wp_cli` access.
+- Use WordPress.com / Jetpack-connected MCP tools through the existing Studio MCP flow when the task targets a connected WordPress.com site.
+- Choose existing WordPress features and known plugins before creating custom code.
+- Use custom block plugins for reusable editor blocks that core blocks cannot cover.
+- Use custom plugins for reusable behavior that should survive theme changes.
+- Use theme work for templates, layout, styling, and visual presentation.
+- Verify changes with the relevant Studio MCP tools before calling the task complete.
+
+## Shared Substrate
+
+The WordPress.com MCP and agent substrate is shared across OpenCode, Codex, Claude Code, and Cursor. OpenCode-specific files only adapt discovery, commands, and configuration to OpenCode's `opencode.json` and `.opencode/` conventions.

plugins/qodo/AGENTS.md

@@ -0,0 +1,27 @@
+# WordPress Studio for Qodo
+
+Use these instructions when Qodo IDE Plugin assists with WordPress site building, auditing, theme work, custom blocks, or plugins.
+
+## Operating model
+
+- Prefer WordPress Studio MCP tools for site management, screenshots, block validation, frontend audits, and WordPress operations when they are available in Qodo.
+- Use `wp_cli` through the Studio MCP server as the general-purpose WordPress escape hatch.
+- Route implementation requests through the smallest suitable WordPress abstraction: site settings, content, theme, block, plugin, or audit.
+- Preserve existing project conventions and inspect the current WordPress structure before editing.
+- Keep generated code accessible, performant, responsive, secure, and aligned with WordPress APIs and Gutenberg conventions.
+- Verify changes with relevant Studio MCP tools, project tests, screenshots, block validation, or WP-CLI before summarizing completion.
+
+## Shared WordPress skills
+
+This Qodo output packages the same shared skill source as the other Build with WordPress outputs. The skills live in `skills/` and provide deeper task-specific guidance:
+
+- For auditing work, consult `skills/auditing/SKILL.md`.
+- For block-creator work, consult `skills/block-creator/SKILL.md`.
+- For design-previews-creator work, consult `skills/design-previews-creator/SKILL.md`.
+- For plugin-creator work, consult `skills/plugin-creator/SKILL.md`.
+- For site-creator work, consult `skills/site-creator/SKILL.md`.
+- For studio work, consult `skills/studio/SKILL.md`.
+- For theme-creator work, consult `skills/theme-creator/SKILL.md`.
+- For wordpress-creator work, consult `skills/wordpress-creator/SKILL.md`.
+
+When a task maps to one of those skills, use the relevant `skills/<name>/SKILL.md` file as the detailed playbook. Start with `skills/wordpress-creator/SKILL.md` for broad WordPress implementation requests.

plugins/roo-code/AGENTS.md

@@ -0,0 +1,8 @@
+# WordPress.com Roo Code Agent Rules
+
+This output packages the shared Build with WordPress skills for Roo Code.
+
+- Roo-specific files live in `.roo/`: workspace rules in `.roo/rules/` and MCP configuration in `.roo/mcp.json`.
+- Shared WordPress.com behavior lives in `skills/` and the existing WordPress Studio MCP flow.
+- Do not create a new WordPress backend service for Roo Code. Connect Roo to the existing `studio mcp` server and bundled `wordpress-telemetry` server.
+- Use the exact product name WordPress.com in user-facing text.

plugins/zed/AGENTS.md

@@ -0,0 +1,22 @@
+# WordPress.com Zed Instructions
+
+Use WordPress.com as the user-facing product name.
+
+## Role
+
+You help users build, customize, audit, and troubleshoot WordPress.com sites using the smallest suitable WordPress abstraction.
+
+## Workflow
+
+- Start by loading the `wordpress-creator` skill for WordPress.com build, theme, block, plugin, site-creation, or audit requests.
+- Prefer the WordPress Studio MCP server for site discovery, local site control, screenshots, block validation, and `wp_cli` access.
+- Use WordPress.com / Jetpack-connected MCP tools through the existing Studio MCP flow when the task targets a connected WordPress.com site.
+- Choose existing WordPress features and known plugins before creating custom code.
+- Use custom block plugins for reusable editor blocks that core blocks cannot cover.
+- Use custom plugins for reusable behavior that should survive theme changes.
+- Use theme work for templates, layout, styling, and visual presentation.
+- Verify changes with the relevant Studio MCP tools before calling the task complete.
+
+## Shared Substrate
+
+The WordPress.com MCP and agent substrate is shared across Zed, OpenCode, Codex, Claude Code, Cursor, Gemini, Copilot, and Roo Code. Zed-specific files only adapt discovery and MCP configuration to Zed's native `AGENTS.md`, `.agents/skills/`, and `.zed/settings.json` conventions.