Add Factory Droid output (#41)

Author: chubes4

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, Roo Code, Windsurf/Cascade, and Aider as separate outputs:
+This repo currently packages shared skills and setup files for Codex, Claude Code, Cursor, Continue, Factory Droid, GitHub Copilot, Gemini, Roo Code, Windsurf/Cascade, and Aider 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
@@ -18,6 +18,7 @@ This repo currently packages shared skills and setup files for Codex, Claude Cod
 - 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
+- includes a Factory Droid marketplace output with a native Droid plugin, command, custom Droid, hook, and MCP configuration
 
 ## Testing
 
@@ -139,6 +140,26 @@ claude --plugin-dir ./plugins/claude-code
 5. Start Aider from the repo root that contains `.aider.conf.yml`.
 6. Try a representative WordPress.com coding task and confirm Aider loads the conventions as read-only context.
 
+### Test in Factory Droid
+
+1. Review the generated Factory marketplace output in `./plugins/factory`.
+2. Confirm the generated setup files exist:
+   - `plugins/factory/.factory-plugin/marketplace.json`
+   - `plugins/factory/plugins/wordpress-studio/.factory-plugin/plugin.json`
+   - `plugins/factory/plugins/wordpress-studio/mcp.json`
+   - `plugins/factory/plugins/wordpress-studio/commands/wordpress.md`
+   - `plugins/factory/plugins/wordpress-studio/droids/wordpress-builder.md`
+   - `plugins/factory/plugins/wordpress-studio/hooks/hooks.json`
+   - `plugins/factory/plugins/wordpress-studio/skills/`
+3. Install from the local marketplace with Factory Droid:
+
+```bash
+droid plugin marketplace add ./plugins/factory
+droid plugin install wordpress-studio@wordpress-studio --scope project
+```
+
+4. In Droid, confirm the `wordpress-studio` and `wordpress-telemetry` MCP servers are available, then try representative WordPress.com tasks.
+
 ## Current scope
 
 - Shared skills for:
@@ -156,6 +177,7 @@ claude --plugin-dir ./plugins/claude-code
 - Claude Code packaging output in `plugins/claude-code/`
 - Cursor packaging output in `plugins/cursor/`
 - Continue setup output in `plugins/continue/`
+- Factory Droid marketplace output in `plugins/factory/`
 - Roo Code workspace output in `plugins/roo-code/`
 - Gemini packaging output in `plugins/gemini/`
 - GitHub Copilot packaging output in `plugins/copilot/`
@@ -175,6 +197,7 @@ The build packages the shared skills into:
 - `plugins/claude-code/skills/`
 - `plugins/cursor/skills/`
 - `plugins/roo-code/skills/`
+- `plugins/factory/plugins/wordpress-studio/skills/`
 - `plugins/gemini/skills/`
 - `plugins/copilot/skills/`
 - `plugins/windsurf/skills/`
@@ -186,6 +209,7 @@ It also generates plugin-specific MCP configs for each surface:
 - Claude Code: `plugins/claude-code/.mcp.json`
 - Cursor: `plugins/cursor/mcp.json`
 - Continue: `plugins/continue/.continue/mcpServers/wordpress-com.yaml`
+- Factory Droid: `plugins/factory/plugins/wordpress-studio/mcp.json`
 - Roo Code: `plugins/roo-code/.roo/mcp.json`
 - Gemini: `plugins/gemini/.gemini/settings.json`
 - GitHub Copilot: `plugins/copilot/.vscode/mcp.json`
@@ -297,6 +321,35 @@ That folder currently contains:
 
 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 Factory Droid marketplace output is generated to:
+
+```text
+plugins/factory/
+```
+
+That folder currently contains:
+
+- `.factory-plugin/marketplace.json`
+- `plugins/wordpress-studio/.factory-plugin/plugin.json`
+- `plugins/wordpress-studio/mcp.json`
+- `plugins/wordpress-studio/scripts/wordpress-telemetry-mcp.mjs`
+- `plugins/wordpress-studio/commands/wordpress.md`
+- `plugins/wordpress-studio/droids/wordpress-builder.md`
+- `plugins/wordpress-studio/hooks/hooks.json`
+- `plugins/wordpress-studio/hooks/session-context.sh`
+- `plugins/wordpress-studio/skills/`
+- `plugins/wordpress-studio/README.md`
+
+The generated Factory Droid MCP config launches both `studio mcp` and the bundled `wordpress-telemetry` MCP server. The Factory output follows the official Factory plugin, skills, custom slash command, custom Droid, MCP, hooks, and marketplace docs:
+
+- https://docs.factory.ai/cli/configuration/plugins
+- https://docs.factory.ai/guides/building/building-plugins
+- https://docs.factory.ai/cli/configuration/skills
+- https://docs.factory.ai/cli/configuration/custom-slash-commands
+- https://docs.factory.ai/cli/configuration/custom-droids
+- https://docs.factory.ai/cli/configuration/mcp
+- https://docs.factory.ai/reference/hooks-reference
+
 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/factory/.factory-plugin/marketplace.json

@@ -0,0 +1,15 @@
+{
+  "name": "wordpress-studio",
+  "description": "WordPress Studio plugins for Factory Droid.",
+  "owner": {
+    "name": "Automattic"
+  },
+  "plugins": [
+    {
+      "name": "wordpress-studio",
+      "description": "Craft production-grade WordPress sites and applications with Droid, WordPress Studio MCP, shared skills, commands, hooks, and custom droids.",
+      "source": "./plugins/wordpress-studio",
+      "category": "Coding"
+    }
+  ]
+}

plugins/factory/plugins/wordpress-studio/.factory-plugin/plugin.json

@@ -0,0 +1,11 @@
+{
+  "name": "wordpress-studio",
+  "version": "0.3.0",
+  "description": "Craft production-grade WordPress sites and applications with Droid, WordPress Studio MCP, shared skills, commands, hooks, and custom droids.",
+  "author": {
+    "name": "Automattic"
+  },
+  "homepage": "https://developer.wordpress.com/",
+  "repository": "https://github.com/Automattic/build-with-wordpress",
+  "license": "GPL-2.0-or-later"
+}

plugins/factory/plugins/wordpress-studio/README.md

@@ -0,0 +1,60 @@
+# WordPress Studio for Factory Droid
+
+This Factory output packages the shared Build with WordPress skills as a native Droid plugin.
+
+## Factory-native pieces
+
+- `.factory-plugin/plugin.json` is the Factory plugin manifest.
+- `skills/` contains the shared WordPress skills. Droid can invoke these automatically, and users can invoke them as slash commands.
+- `commands/wordpress.md` adds a user-invoked `/wordpress` workflow shortcut.
+- `droids/wordpress-builder.md` adds a custom Droid subagent for focused WordPress.com work.
+- `mcp.json` configures the shared `wordpress-studio` MCP server and bundled `wordpress-telemetry` MCP server.
+- `hooks/hooks.json` adds lightweight session-start context using `${DROID_PLUGIN_ROOT}`.
+
+## Marketplace layout
+
+The parent `plugins/factory/` directory is a local Factory marketplace:
+
+- `.factory-plugin/marketplace.json` lists the `wordpress-studio` plugin.
+- `plugins/wordpress-studio/` contains this plugin.
+
+## Local install
+
+From this repository root after running `pnpm build`:
+
+```bash
+droid plugin marketplace add ./plugins/factory
+droid plugin install wordpress-studio@wordpress-studio --scope project
+```
+
+Factory's plugin documentation also supports adding marketplaces from GitHub repositories. If this output is published from a dedicated marketplace repository, add that repository URL with `droid plugin marketplace add <url>` and install `wordpress-studio@wordpress-studio`.
+
+## MCP servers
+
+`mcp.json` launches:
+
+- `wordpress-studio`: runs `studio mcp` for WordPress site management, screenshots, block validation, performance tooling, and WP-CLI access.
+- `wordpress-telemetry`: runs the bundled telemetry MCP server generated by this package.
+
+No secrets are stored in the project MCP config.
+
+## Included skills
+
+- `auditing`
+- `block-creator`
+- `design-previews-creator`
+- `plugin-creator`
+- `site-creator`
+- `studio`
+- `theme-creator`
+- `wordpress-creator`
+
+## Factory documentation used
+
+- Plugins: https://docs.factory.ai/cli/configuration/plugins
+- Building plugins: https://docs.factory.ai/guides/building/building-plugins
+- Skills: https://docs.factory.ai/cli/configuration/skills
+- Custom slash commands: https://docs.factory.ai/cli/configuration/custom-slash-commands
+- Custom Droids: https://docs.factory.ai/cli/configuration/custom-droids
+- MCP: https://docs.factory.ai/cli/configuration/mcp
+- Hooks reference: https://docs.factory.ai/reference/hooks-reference

plugins/factory/plugins/wordpress-studio/commands/wordpress.md

@@ -0,0 +1,12 @@
+---
+description: Route a WordPress.com task through the shared WordPress Creator skill.
+argument-hint: <wordpress task>
+---
+
+# Build with WordPress.com
+
+Handle this WordPress.com request using the shared WordPress Creator workflow:
+
+$ARGUMENTS
+
+Load the `wordpress-creator` skill first, choose the smallest suitable WordPress abstraction, and use the `wordpress-studio` MCP server for site operations and verification when available.

plugins/factory/plugins/wordpress-studio/droids/wordpress-builder.md

@@ -0,0 +1,15 @@
+---
+name: wordpress-builder
+description: Builds, customizes, audits, and troubleshoots WordPress.com sites using WordPress Studio MCP and the shared Build with WordPress skills.
+model: inherit
+tools: ["Read", "LS", "Grep", "Glob", "Create", "Edit", "ApplyPatch", "Execute"]
+mcpServers: ["wordpress-studio", "wordpress-telemetry"]
+---
+
+You are a WordPress.com specialist Droid.
+
+Use WordPress.com as the user-facing product name. For build, theme, block, plugin, site-creation, or audit requests, load `skills/wordpress-creator/SKILL.md` first and follow its routing to the smallest suitable implementation path.
+
+Prefer the `wordpress-studio` MCP server for site discovery, local site control, screenshots, block validation, `wp_cli`, and WordPress.com or Jetpack-connected workflows. Use the `wordpress-telemetry` MCP server for workflow telemetry when available.
+
+Verify changes with relevant Studio MCP tools, project tests, block validation, screenshots, or WP-CLI evidence before reporting completion.

plugins/factory/plugins/wordpress-studio/hooks/hooks.json

@@ -0,0 +1,16 @@
+{
+  "description": "Adds WordPress Studio plugin context at Droid session start.",
+  "hooks": {
+    "SessionStart": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "sh ${DROID_PLUGIN_ROOT}/hooks/session-context.sh",
+            "timeout": 10
+          }
+        ]
+      }
+    ]
+  }
+}

plugins/factory/plugins/wordpress-studio/hooks/session-context.sh

@@ -0,0 +1,5 @@
+#!/usr/bin/env sh
+set -eu
+
+printf '%s
+' 'WordPress Studio Droid plugin is active. Load skills/wordpress-creator/SKILL.md for WordPress.com build, theme, block, plugin, site creation, or audit tasks. Prefer the wordpress-studio MCP server for site operations and verification when available.'