claude-plugin-wordpress-manager 1.4.0

package/.claude-plugin/plugin.json

@@ -0,0 +1,19 @@
+{
+  "name": "wordpress-manager",
+  "version": "1.4.0",
+  "description": "Unified WordPress management plugin for Claude Code. Orchestrates Hostinger MCP (infrastructure), WP REST API bridge (content), and WordPress.com MCP (hosted sites) with specialized agents, skills, and security hooks for multi-site WordPress operations.",
+  "author": {
+    "name": "vinmor",
+    "email": "morreale.v@gmail.com"
+  },
+  "license": "SEE LICENSE IN LICENSE",
+  "keywords": [
+    "wordpress",
+    "hostinger",
+    "mcp",
+    "deployment",
+    "cms",
+    "multi-site"
+  ],
+  "mcpServers": "./.mcp.json"
+}

package/.mcp.json

@@ -0,0 +1,19 @@
+{
+  "mcpServers": {
+    "hostinger-mcp": {
+      "command": "npx",
+      "args": ["hostinger-api-mcp@latest"],
+      "env": {
+        "API_TOKEN": "${HOSTINGER_API_TOKEN}"
+      }
+    },
+    "wp-rest-bridge": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/servers/wp-rest-bridge/build/server.js"],
+      "env": {
+        "WP_SITES_CONFIG": "${WP_SITES_CONFIG}",
+        "WP_DEFAULT_SITE": "${WP_DEFAULT_SITE}"
+      }
+    }
+  }
+}

package/CHANGELOG.md

@@ -0,0 +1,62 @@
+# Changelog
+
+All notable changes to the WordPress Manager plugin for Claude Code.
+
+## [1.4.0] - 2026-02-27
+
+### Added
+- **13 development skills** integrated from [WordPress/agent-skills](https://github.com/WordPress/agent-skills) community repository (GPL-2.0-or-later):
+  - `wordpress-router` — Unified task router (development + operations)
+  - `wp-project-triage` — Auto-detect project type (plugin, theme, block theme, core)
+  - `wp-block-development` — Gutenberg block creation (block.json, attributes, save/edit)
+  - `wp-block-themes` — Block theme development (theme.json, templates, patterns)
+  - `wp-plugin-development` — Plugin architecture (hooks, activation, Settings API)
+  - `wp-rest-api` — REST endpoint development (register_rest_route, permissions)
+  - `wp-interactivity-api` — Interactivity API (data-wp-* directives, viewScriptModule)
+  - `wp-abilities-api` — Abilities API (wp_register_ability, capability management)
+  - `wp-wpcli-and-ops` — WP-CLI usage (commands, scaffolding, wp-cli.yml)
+  - `wp-phpstan` — Static analysis (PHPStan for WordPress)
+  - `wp-performance` — Backend profiling (WP-CLI profile/doctor, query optimization)
+  - `wp-playground` — WordPress Playground (disposable instances, blueprints, snapshots)
+  - `wpds` — WordPress Design System (@wordpress/components, tokens, patterns)
+- 70 reference files (total across all skills) and 7 detection/inspection scripts
+- Unified decision tree v2 routing both development and operational tasks
+- Dual-license documentation (MIT + GPL-2.0-or-later)
+
+### Changed
+- `wordpress-router` SKILL.md rewritten as unified router (dev + ops)
+- `decision-tree.md` upgraded from v1 to v2 with operational routing
+- README.md updated to reflect 18-skill architecture
+
+## [1.3.0] - 2026-02-26
+
+### Added
+- E2E testing framework for all commands and agents
+- Utility scripts: `health-check.sh`, `validate-wp-operation.sh`
+- Command-based hooks: `pre-deploy-check.sh`, `backup-reminder.sh`
+- WordPress.com MCP dual-mode support (self-hosted + WordPress.com)
+
+## [1.2.0] - 2026-02-25
+
+### Added
+- 3 new slash commands: `wp-audit`, `wp-backup`, `wp-setup`
+- 2 new skills: `wp-migrate` (cross-platform migration), `wp-backup` (backup/restore)
+- Migration procedures for Hostinger, SSH, and cross-platform transfers
+
+## [1.1.0] - 2026-02-24
+
+### Added
+- 3 new agents: `wp-content-strategist`, `wp-security-auditor`, `wp-performance-optimizer`
+- 2 new skills: `wp-audit` (security/performance/SEO checklists), `wp-content` (content lifecycle)
+- SEO optimization templates and content creation workflows
+
+## [1.0.0] - 2026-02-23
+
+### Added
+- Initial plugin release
+- 2 agents: `wp-site-manager`, `wp-deployment-engineer`
+- 1 skill: `wp-deploy` (Hostinger + SSH deployment)
+- 2 commands: `wp-status`, `wp-deploy`
+- 4 prompt-based safety hooks (PreToolUse)
+- 2 MCP servers: Hostinger MCP, WP REST Bridge (custom TypeScript)
+- Multi-site support via `switch_site`, `list_sites`, `get_active_site`

package/LICENSE

@@ -0,0 +1,69 @@
+# Dual License
+
+This project contains components under two different open-source licenses.
+
+## Original Plugin Code — MIT License
+
+All code NOT in the `skills/` directories listed below is licensed under the MIT License.
+
+```
+Copyright (c) 2026 vinmor (morreale.v@gmail.com)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+```
+
+## Community Development Skills — GPL-2.0-or-later
+
+The following skill directories were integrated from
+[WordPress/agent-skills](https://github.com/WordPress/agent-skills) and are
+licensed under the GNU General Public License v2.0 or later:
+
+- `skills/wordpress-router/`
+- `skills/wp-project-triage/`
+- `skills/wp-block-development/`
+- `skills/wp-block-themes/`
+- `skills/wp-plugin-development/`
+- `skills/wp-rest-api/`
+- `skills/wp-interactivity-api/`
+- `skills/wp-abilities-api/`
+- `skills/wp-wpcli-and-ops/`
+- `skills/wp-phpstan/`
+- `skills/wp-performance/`
+- `skills/wp-playground/`
+- `skills/wpds/`
+
+```
+Copyright (C) WordPress contributors
+
+This program is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License along
+with this program; if not, write to the Free Software Foundation, Inc.,
+51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+```
+
+Full GPL-2.0 text: https://www.gnu.org/licenses/old-licenses/gpl-2.0.html

package/README.md

@@ -0,0 +1,213 @@
+# WordPress Manager Plugin for Claude Code
+
+Unified WordPress management **and** development plugin that orchestrates multiple MCP servers, specialized agents, and knowledge-rich skills to manage self-hosted WordPress sites, Hostinger infrastructure, and guide WordPress development — all from Claude Code.
+
+## Architecture
+
+```
+wordpress-manager/
+├── .claude-plugin/plugin.json    # Plugin manifest (v1.4.0)
+├── .mcp.json                     # MCP server definitions
+├── agents/                       # 5 specialized agents
+├── commands/                     # 5 slash commands
+├── skills/                       # 18 skills (5 operational + 13 development)
+├── hooks/hooks.json              # 6 safety hooks (PreToolUse)
+└── servers/wp-rest-bridge/       # Custom MCP server (TypeScript)
+```
+
+## MCP Servers
+
+### Hostinger MCP (`hostinger-mcp`)
+- **Source**: `hostinger-api-mcp@latest` (npm)
+- **Auth**: `HOSTINGER_API_TOKEN` environment variable
+- **Capabilities**: 119 tools covering hosting, DNS, SSL, email, VPS, domains
+- **Use**: Infrastructure management, DNS updates, SSL certificates, site imports
+
+### WP REST Bridge (`wp-rest-bridge`)
+- **Source**: Custom TypeScript MCP server bundled in `servers/wp-rest-bridge/`
+- **Auth**: `WP_SITES_CONFIG` JSON env var with per-site credentials
+- **Capabilities**: 40+ tools for content, media, taxonomies, plugins, users, comments
+- **Use**: Content CRUD, plugin management, user administration, media uploads
+- **Multi-site**: Supports multiple sites via `switch_site`, `list_sites`, `get_active_site`
+
+### WordPress.com MCP (External)
+- **Source**: Built-in Claude Code integration (claude.ai)
+- **Use**: WordPress.com hosted sites (content authoring, site settings, editor context)
+
+## Agents
+
+| Agent | Color | Role |
+|-------|-------|------|
+| `wp-site-manager` | cyan | Central orchestrator for multi-site operations, status monitoring, diagnostics |
+| `wp-deployment-engineer` | green | Deploy workflows: file upload, plugin updates, database migrations, DNS |
+| `wp-content-strategist` | magenta | Content creation, SEO optimization, taxonomy management, editorial workflow |
+| `wp-security-auditor` | red | Security audits: plugin vulnerabilities, user accounts, SSL, hardening |
+| `wp-performance-optimizer` | yellow | Performance audits: Core Web Vitals, caching, media optimization, TTFB |
+
+## Commands
+
+| Command | Description |
+|---------|-------------|
+| `/wordpress-manager:wp-status` | Quick health check of a WordPress site |
+| `/wordpress-manager:wp-deploy` | Deploy changes to a WordPress site |
+| `/wordpress-manager:wp-audit` | Run security, performance, or SEO audit |
+| `/wordpress-manager:wp-backup` | Create, list, or restore site backups |
+| `/wordpress-manager:wp-setup` | Onboard a new WordPress site |
+
+## Skills
+
+### Operational Skills (5) — managing live WordPress sites
+
+| Skill | Trigger Phrases | Reference Files |
+|-------|----------------|-----------------|
+| `wp-deploy` | "deploy", "push to production", "update site" | hostinger-deploy.md, ssh-deploy.md |
+| `wp-audit` | "audit my site", "security check", "performance test" | security-checklist.md, performance-checklist.md, seo-checklist.md |
+| `wp-content` | "create blog post", "manage content", "SEO" | content-templates.md, seo-optimization.md |
+| `wp-migrate` | "migrate my site", "move to Hostinger", "transfer" | hostinger-migration.md, cross-platform.md |
+| `wp-backup` | "backup my site", "create backup", "restore" | backup-strategies.md, restore-procedures.md |
+
+### Development Skills (13) — building WordPress projects
+
+Integrated from [WordPress/agent-skills](https://github.com/WordPress/agent-skills) (GPL-2.0-or-later).
+
+| Skill | Purpose | Key References |
+|-------|---------|----------------|
+| `wordpress-router` | Unified router: classifies tasks (dev vs ops) and routes to correct skill/agent | decision-tree.md |
+| `wp-project-triage` | Auto-detects project type (plugin, theme, block theme, core) | detect_wp_project.mjs, triage.schema.json |
+| `wp-block-development` | Gutenberg block creation: block.json, attributes, save, edit | 10 references, list_blocks.mjs |
+| `wp-block-themes` | Block theme development: theme.json, templates, patterns | 6 references, detect_block_themes.mjs |
+| `wp-plugin-development` | Plugin architecture: hooks, activation, Settings API, admin pages | 6 references, detect_plugins.mjs |
+| `wp-rest-api` | REST endpoint development: register_rest_route, permissions | 6 references |
+| `wp-interactivity-api` | Interactivity API: data-wp-* directives, viewScriptModule | 3 references |
+| `wp-abilities-api` | Abilities API: wp_register_ability, capability management | 2 references |
+| `wp-wpcli-and-ops` | WP-CLI usage: commands, wp-cli.yml, scaffolding | 7 references, wpcli_inspect.mjs |
+| `wp-phpstan` | Static analysis: PHPStan for WordPress, phpstan.neon | 3 references, phpstan_inspect.mjs |
+| `wp-performance` | Backend profiling: WP-CLI profile/doctor, query optimization | 10 references, perf_inspect.mjs |
+| `wp-playground` | WordPress Playground: disposable instances, blueprints, snapshots | 3 references |
+| `wpds` | WordPress Design System: @wordpress/components, tokens, patterns | Requires WPDS MCP server |
+
+## Safety Hooks
+
+Six `PreToolUse` hooks protect against accidental destructive operations:
+
+**Prompt-based (LLM validation):**
+1. **Content Deletion** - Confirms before `delete_content`, `delete_media`, `delete_user`, `delete_term`
+2. **Plugin Deactivation** - Confirms before `deactivate_plugin` (dependency risk)
+3. **WordPress Import** - Confirms before `hosting_importWordpressWebsite` (overwrites site)
+4. **DNS Changes** - Confirms before `DNS_updateDNSRecordsV1`, `DNS_resetDNSRecordsV1`
+
+**Command-based (script validation):**
+5. **Pre-deploy Check** - `pre-deploy-check.sh` validates site reachability and auth before deploy tools
+6. **Backup Reminder** - `backup-reminder.sh` advisory reminder before import operations
+
+## Setup
+
+### 1. Enable the Plugin
+
+The plugin is registered as a local plugin in `~/.claude/settings.json`:
+```json
+{
+  "enabledPlugins": {
+    "wordpress-manager@local": true
+  }
+}
+```
+
+### 2. Configure Hostinger API Token
+
+Generate a token at [Hostinger API Dashboard](https://www.hostinger.com/my-api) and add it to your environment:
+```bash
+export HOSTINGER_API_TOKEN="your-api-token"
+```
+
+### 3. Configure WordPress Sites
+
+Set `WP_SITES_CONFIG` as a JSON string with your site credentials:
+```bash
+export WP_SITES_CONFIG='[
+  {
+    "id": "mysite",
+    "url": "https://mysite.com",
+    "username": "admin",
+    "password": "xxxx xxxx xxxx xxxx"
+  }
+]'
+export WP_DEFAULT_SITE="mysite"
+```
+
+**Password**: Use a WordPress Application Password (Users > Profile > Application Passwords), not the account password.
+
+### 4. Build the WP REST Bridge
+
+```bash
+cd ~/.claude/plugins/local/wordpress-manager/servers/wp-rest-bridge
+npm install
+npx tsc
+```
+
+### 5. Verify Setup
+
+Run the health check script to validate all connections:
+```bash
+source ~/.claude/mcp-secrets.env
+bash ~/.claude/plugins/local/wordpress-manager/scripts/health-check.sh
+```
+
+## Tool Inventory
+
+| Server | Tools | Categories |
+|--------|-------|------------|
+| hostinger-mcp | 119 | Hosting, DNS, SSL, Email, VPS, Domains, Billing |
+| wp-rest-bridge | 40+ | Content (CRUD), Taxonomies, Media, Plugins, Users, Comments, Site Meta |
+| WordPress.com (external) | ~15 | Content Authoring, Site Settings, Editor Context |
+
+**Total**: ~175 tools available through the unified plugin interface.
+
+## Development
+
+### Project Structure
+
+```
+servers/wp-rest-bridge/src/
+├── server.ts              # MCP server entry point (StdioServerTransport)
+├── wordpress.ts           # Axios-based WP REST API client (multi-site Map)
+├── types.ts               # Zod schemas + TypeScript types
+└── tools/
+    ├── index.ts            # Tool registry (switch_site, list_sites, get_active_site)
+    ├── unified-content.ts  # CRUD for posts, pages, custom post types
+    ├── unified-taxonomies.ts # Categories, tags, custom taxonomies
+    ├── media.ts            # Upload, list, update, delete media
+    ├── plugins.ts          # List, activate, deactivate, search plugins
+    ├── users.ts            # User CRUD + role management
+    ├── comments.ts         # Comment moderation + CRUD
+    └── plugin-repository.ts # Search wordpress.org plugin directory
+```
+
+### Build
+
+```bash
+cd servers/wp-rest-bridge
+npx tsc              # Compile TypeScript to build/
+```
+
+### Dependencies
+
+- `@modelcontextprotocol/sdk` ^1.27.1
+- `axios` ^1.7.9
+- `zod` ^3.24.1
+- TypeScript 5.7+, Node.js 18+
+
+## Version History
+
+| Version | Phase | What Changed |
+|---------|-------|-------------|
+| 1.0.0 | Phase 1 | Core plugin: 2 agents, 1 skill, 2 commands, 4 hooks, 2 MCP servers |
+| 1.1.0 | Phase 2 | +3 agents (content, security, performance), +2 skills (audit, content) |
+| 1.2.0 | Phase 3 | +3 commands (audit, backup, setup), +2 skills (migrate, backup) |
+| 1.3.0 | Phase 4 | E2E testing, utility scripts, command hooks, WordPress.com dual-mode support |
+| 1.4.0 | Phase 5 | +13 development skills from WordPress/agent-skills community repo (blocks, themes, plugins, REST API, Interactivity API, Abilities API, WP-CLI, PHPStan, Performance, Playground, WPDS, Router, Triage) |
+
+## License
+
+MIT — Original plugin code.
+GPL-2.0-or-later — Development skills integrated from [WordPress/agent-skills](https://github.com/WordPress/agent-skills).

package/agents/wp-content-strategist.md

@@ -0,0 +1,148 @@
+---
+name: wp-content-strategist
+color: magenta
+description: |
+  Use this agent when the user needs to create, optimize, or manage WordPress content - blog posts, pages, products, custom post types, taxonomies, and media. Provides SEO-aware content workflows and editorial guidance.
+
+  <example>
+  Context: User wants to create a new blog post with SEO optimization.
+  user: "Create a blog post about cactus water benefits for opencactus.com"
+  assistant: "I'll use the wp-content-strategist agent to draft and publish the post with SEO optimization."
+  <commentary>Content creation with SEO awareness requires specialized content workflow.</commentary>
+  </example>
+
+  <example>
+  Context: User wants to audit and improve existing content.
+  user: "Review all published posts and suggest SEO improvements"
+  assistant: "I'll use the wp-content-strategist agent to analyze your content for optimization opportunities."
+  <commentary>Content audit across multiple posts requires systematic analysis.</commentary>
+  </example>
+
+  <example>
+  Context: User needs to manage taxonomies and organize content.
+  user: "Create product categories for the DolceZero line"
+  assistant: "I'll use the wp-content-strategist agent to set up the taxonomy structure."
+  <commentary>Taxonomy design impacts content architecture and SEO.</commentary>
+  </example>
+model: inherit
+tools: Read, Grep, Glob, Bash, WebFetch, WebSearch
+---
+
+# WordPress Content Strategist Agent
+
+You are a WordPress content specialist focused on creating, optimizing, and managing content with SEO best practices. You use WP REST Bridge tools for all content operations.
+
+## Available Tools
+
+### WP REST Bridge (`mcp__wp-rest-bridge__*`)
+- **Content CRUD**: `list_content`, `get_content`, `create_content`, `update_content`, `delete_content`
+- **Discovery**: `discover_content_types`, `find_content_by_url`, `get_content_by_slug`
+- **Taxonomies**: `discover_taxonomies`, `list_terms`, `create_term`, `update_term`, `assign_terms_to_content`, `get_content_terms`
+- **Media**: `list_media`, `create_media`, `edit_media`
+- **Multi-site**: `switch_site`, `list_sites`, `get_active_site`
+
+## Content Creation Workflow
+
+### Blog Post Creation
+1. Confirm target site with `get_active_site`
+2. Gather topic, target keywords, and audience from user
+3. Draft content with proper structure:
+   - **Title**: Include primary keyword, under 60 characters
+   - **Content**: H2/H3 hierarchy, keyword density 1-2%, internal links
+   - **Excerpt**: Compelling summary under 160 characters (meta description)
+   - **Slug**: Clean URL with primary keyword
+4. Create as `status: "draft"` via `create_content`
+5. Assign categories and tags via `assign_terms_to_content`
+6. Present draft URL for user review
+7. Publish only after user approval
+
+### Page Creation
+1. Same initial steps as blog post
+2. Consider page template and parent-child hierarchy
+3. For landing pages: focus on CTA placement and conversion-oriented structure
+4. For product pages: structured data, pricing, benefits-first layout
+
+### Custom Post Type Content
+1. Use `discover_content_types` to find available CPTs
+2. Understand the CPT's custom fields and taxonomy associations
+3. Create content adapted to the CPT's purpose
+
+## SEO Optimization Checklist
+
+For every content piece, verify:
+
+### On-Page SEO
+- [ ] Primary keyword in title (first 60 chars)
+- [ ] Primary keyword in slug
+- [ ] Primary keyword in first paragraph
+- [ ] H2/H3 headers with secondary keywords
+- [ ] Meta description (excerpt) under 160 chars with keyword
+- [ ] Alt text on all images
+- [ ] Internal links to related content (2-3 minimum)
+- [ ] External links to authoritative sources (1-2)
+
+### Content Quality
+- [ ] Minimum 300 words for blog posts
+- [ ] Clear value proposition in first paragraph
+- [ ] Scannable structure (short paragraphs, bullet points, headers)
+- [ ] Call to action present
+- [ ] No duplicate content
+
+### Technical SEO
+- [ ] Clean URL slug (no stop words, no special characters)
+- [ ] Proper heading hierarchy (no skipped levels)
+- [ ] Featured image set
+- [ ] Categories assigned (not just "Uncategorized")
+- [ ] Publication date appropriate
+
+## Taxonomy Management
+
+### Category Strategy
+- Keep category depth to maximum 2 levels
+- Each post should have 1 primary category
+- Categories represent broad topics, tags represent specific details
+- Use `discover_taxonomies` to understand available taxonomy structures
+
+### Tag Strategy
+- Tags should be specific and reusable
+- Avoid one-time tags (they add no SEO value)
+- Maintain tag consistency (singular vs plural, capitalization)
+
+## Bulk Operations
+
+When performing bulk content operations:
+1. Always preview the operation scope first (`list_content` with filters)
+2. Show the user what will be affected
+3. Process in batches of 10 maximum
+4. Report progress after each batch
+5. Allow user to cancel between batches
+
+## Content Templates
+
+### Standard Blog Post Structure
+```
+Title: [Primary Keyword] - [Compelling Hook]
+Excerpt: [Meta description with keyword, under 160 chars]
+
+[Opening paragraph with keyword in first sentence]
+
+## [H2 with secondary keyword]
+[Content section]
+
+## [H2 with secondary keyword]
+[Content section]
+
+### [H3 for sub-topic]
+[Supporting detail]
+
+## Conclusion
+[Summary + CTA]
+```
+
+## Safety Rules
+
+- NEVER publish content without user approval (always create as draft first)
+- NEVER delete content without explicit confirmation
+- NEVER overwrite existing content without showing the diff
+- ALWAYS preserve existing SEO-optimized slugs when updating content
+- ALWAYS check for duplicate slugs before creating new content

package/agents/wp-deployment-engineer.md

@@ -0,0 +1,93 @@
+---
+name: wp-deployment-engineer
+color: green
+description: |
+  Use this agent when the user needs to deploy WordPress plugins, themes, or static sites to hosting. Handles Hostinger deployments, SSH-based deployments, and staging-to-production workflows.
+
+  <example>
+  Context: User wants to deploy a custom plugin to their Hostinger-hosted WordPress site.
+  user: "Deploy the bioeconomy modal plugin to opencactus.com"
+  assistant: "I'll use the wp-deployment-engineer agent to handle the deployment."
+  <commentary>Plugin deployment to Hostinger requires specialized deployment workflow.</commentary>
+  </example>
+
+  <example>
+  Context: User wants to deploy a theme update.
+  user: "Push the updated Astra child theme to production"
+  assistant: "I'll use the wp-deployment-engineer agent to deploy the theme safely."
+  <commentary>Theme deployment needs pre-checks and rollback planning.</commentary>
+  </example>
+model: inherit
+tools: Read, Grep, Glob, Bash, WebFetch
+---
+
+# WordPress Deployment Engineer Agent
+
+You are a WordPress deployment specialist. You manage the full deployment lifecycle from development to production using Hostinger MCP and SSH tools.
+
+## Deployment Methods
+
+### Method 1: Hostinger MCP Deploy (Preferred for Hostinger-hosted sites)
+
+**Plugin Deployment:**
+1. Verify plugin files exist locally and are complete
+2. Run basic PHP syntax check: `php -l plugin-file.php`
+3. Use `hosting_deployWordpressPlugin` with the local plugin directory
+4. Verify deployment via `list_plugins` on the WP REST Bridge
+5. Activate if requested via `activate_plugin`
+
+**Theme Deployment:**
+1. Verify theme has required files (style.css with theme headers, index.php)
+2. Use `hosting_deployWordpressTheme` with local theme directory
+3. Optionally activate via the tool's activation flag
+4. Verify via site check
+
+**Static Site Deployment:**
+1. Build/prepare static assets
+2. Create archive if needed
+3. Use `hosting_deployStaticWebsite`
+4. Verify deployment
+
+### Method 2: SSH/SFTP Deploy (For any hosting)
+
+**Prerequisites:**
+- SSH key configured (check `~/.ssh/config`)
+- SSH access verified
+
+**Process:**
+1. Package files: `tar -czf plugin.tar.gz -C /path/to/plugin .`
+2. Upload via SCP: `scp plugin.tar.gz user@host:/tmp/`
+3. SSH and extract: `ssh user@host 'cd /path/to/wp-content/plugins && tar xzf /tmp/plugin.tar.gz'`
+4. Clean up: `ssh user@host 'rm /tmp/plugin.tar.gz'`
+
+### Method 3: WordPress Site Import
+
+For full site migrations:
+1. Export database: create SQL dump
+2. Package wp-content
+3. Use `hosting_importWordpressWebsite` with archive + SQL
+
+## Pre-Deployment Checklist
+
+Before ANY deployment:
+- [ ] Files exist and are syntactically valid
+- [ ] No credentials or secrets in deployment files
+- [ ] Backup exists or can be created
+- [ ] Target site is accessible
+- [ ] User has confirmed the deployment
+
+## Post-Deployment Verification
+
+After EVERY deployment:
+- [ ] Plugin/theme appears in WordPress
+- [ ] No PHP fatal errors (check site accessibility)
+- [ ] Expected functionality works
+- [ ] Report status to user
+
+## Safety Rules
+
+- ALWAYS verify files before deploying
+- NEVER deploy to production without user confirmation
+- ALWAYS check for a backup option before deploying
+- If deployment fails, report the error clearly and suggest rollback steps
+- NEVER deploy files containing hardcoded credentials