A Claude Code plugin that gives Claude deep knowledge of WordPress plugin development. When installed, Claude writes WordPress plugins that follow modern PHP practices, WordPress Coding Standards, and established security patterns - without you having to repeat the same instructions every session.
This plugin adds four things to your Claude Code sessions:
Automatically activates when you're working on WordPress plugin code. Claude will:
- Write PHP 8.2+ with strict types, typed properties, union types, enums, and readonly properties
- Follow WordPress Coding Standards (WPCS) - tabs, Yoda conditions, spaces inside parentheses, proper naming
- Apply security best practices - input sanitisation, output escaping, nonce verification, capability checks, prepared database queries
- Use the correct WordPress APIs - hooks, custom post types,
register_post_meta(), block editor, REST API, WP-CLI - Structure plugins with PSR-4 autoloading, Composer, and
@wordpress/scripts - Add DocBlocks to every function, favour early returns, keep functions small and single-purpose
Runs a structured discovery conversation before any code — or any task list — is written. Claude asks questions in rounds (core purpose, scope and data, user interface, integrations and APIs, edge cases and constraints), follows up adaptively based on your answers, and checks the current project directory for an existing plugin structure, CLAUDE.md, or composer.json so the result fits what's already there.
/plugin-plan A WooCommerce extension that adds gift wrapping options to products
The output is a PRD.md file in the project root (or PRD-<slug>.md if one already exists). The PRD captures the plugin's purpose, goals, non-goals, data model, features, admin UI, frontend output, REST API, integrations, scheduled tasks, CLI commands, lifecycle, and testing strategy.
Run this before /plugin-tasks — the PRD it produces is the input to the task generator.
Reads a PRD file produced by /plugin-plan and turns it into a structured, sequential task list before any code is written.
/plugin-tasks PRD.md
If you don't pass an argument, it looks for PRD.md in the project root. If you pass a free-form description instead of a file path it will still proceed, but you'll get better results by running /plugin-plan first.
The output is a TASKS.md file (or TASKS-<slug>.md if one already exists) with numbered, grouped tasks where each task has a clear description and a verification step. Tasks are ordered so each one builds on the last and can be tested independently.
Works through a task list one step at a time - implementing, verifying, and marking each task complete before moving on.
/plugin-build
By default it reads TASKS.md. You can pass a specific file if you have multiple task lists:
/plugin-build TASKS-gift-wrapping.md
After each task, Claude pauses to check in before continuing. This gives you a chance to review the code, suggest changes, or adjust direction.
Clone this repo into a directory where you keep your Claude Code plugins:
mkdir -p ~/.claude/plugins
git clone <repo-url> ~/.claude/plugins/wordpress-pluginYou can clone it anywhere you like — ~/.claude/plugins/ is just a convention.
This plugin is designed to be loaded on demand, not globally. When you start a Claude Code session for WordPress plugin work, pass the plugin directory:
claude --plugin-dir ~/.claude/plugins/wordpress-pluginThis loads the WordPress plugin developer skill and commands for that session only, keeping your other Claude sessions clean.
Once in the session, you can confirm the plugin is active by running /plugin-plan, /plugin-tasks, or /plugin-build. Claude should also automatically apply WordPress coding standards and security practices when you ask it to write plugin code.
- Navigate to your plugin directory (or create an empty one):
mkdir ~/projects/my-plugin && cd ~/projects/my-plugin- Start Claude Code and run a discovery session to produce a PRD:
/plugin-plan A WordPress plugin that adds a custom "Projects" post type with
portfolio fields, a filterable archive page, and a Gutenberg block for
displaying featured projects
Claude will ask questions in rounds. Answer them, and a PRD.md will be written to the project root.
-
Review
PRD.md. Edit anything that's wrong, fill in any open questions, and tighten the scope. -
Generate the task list from the PRD:
/plugin-tasks PRD.md
-
Review the generated
TASKS.md. Edit it if you want to add, remove, or reorder tasks. -
Start building:
/plugin-build
Claude implements one task at a time, verifies it, marks it complete, and asks if you're ready to continue.
The same workflow applies. Navigate to your existing plugin directory and run /plugin-plan to scope the new feature — Claude will detect the existing plugin structure and treat the PRD as a feature spec rather than a new plugin. Then run /plugin-tasks against the resulting PRD.
/plugin-plan Add a REST API endpoint for the Projects post type with full CRUD,
filtering by taxonomy, and batch operations
/plugin-tasks PRD-projects-rest-api.md
You don't have to use the commands. The skill activates automatically whenever you're working on WordPress plugin code. Just describe what you need:
Add a settings page under the Settings menu with fields for API key, sync interval,
and debug mode. Use the Settings API.
Claude will write the code following all the same standards - strict types, WPCS, security, DocBlocks, small functions - whether you use the structured task workflow or not.
| File | Purpose |
|---|---|
skills/wordpress-plugin-developer/SKILL.md |
Core skill definition - coding standards, security rules, plugin structure, patterns for hooks, CPTs, blocks, REST API, assets, i18n, testing, and performance |
| Command | File | Purpose |
|---|---|---|
/plugin-plan |
commands/plugin-plan/SKILL.md |
Run a discovery conversation and produce a PRD |
/plugin-tasks |
commands/plugin-tasks/SKILL.md |
Generate a sequential task list from a PRD file |
/plugin-build |
commands/plugin-build/SKILL.md |
Execute a task list step-by-step with verification |
/plugin-status |
commands/plugin-status/SKILL.md |
(Planned) |
The skill uses progressive disclosure - core patterns are in the main skill file, and detailed templates and examples are in reference files that Claude loads only when needed:
| File | Contents |
|---|---|
references/bootstrap.md |
Full main plugin file template, composer.json, phpcs.xml.dist, package.json |
references/security.md |
Input sanitisation, output escaping, nonce verification, capability checks, $wpdb->prepare() |
references/blocks.md |
block.json template, edit.js/save.js patterns, render.php for dynamic blocks, Interactivity API |
references/rest-api.md |
Full WP_REST_Controller example with CRUD routes, permission callbacks, schema |
references/testing.md |
PHPUnit config, .wp-env.json, WP_UnitTestCase examples, Playwright e2e setup |
references/lifecycle.md |
Activator/Deactivator classes, dbDelta(), cron scheduling, uninstall.php, WP-CLI commands |
Plugins built with this tool target:
- PHP 8.2+ - strict types, typed properties, enums, readonly, match expressions, named arguments
- WordPress 6.7+ - current APIs only, no deprecated functions
- Composer - PSR-4 autoloading, PHPCS, PHPUnit, PHPStan as dev dependencies
- Node/npm -
@wordpress/scriptsfor block compilation and asset bundling - wp-env - local development and test environment
Plugins are scaffolded with this structure:
plugin-name/
├── plugin-name.php # Thin bootstrap: header, constants, autoloader, boot
├── composer.json # PSR-4 autoloading, dev deps (PHPCS, PHPUnit, PHPStan)
├── package.json # @wordpress/scripts
├── uninstall.php # Clean data removal
├── .wp-env.json # Local dev environment
├── phpunit.xml.dist # Test config
├── phpcs.xml.dist # WPCS ruleset
├── src/ # PHP source (PSR-4 root)
│ ├── Plugin.php # Main plugin class (singleton)
│ ├── Admin/ # Admin screens, settings pages
│ ├── Frontend/ # Public-facing output
│ ├── PostTypes/ # Custom post type registrations
│ ├── Taxonomies/ # Custom taxonomies
│ ├── Blocks/ # Server-side block logic
│ ├── REST/ # REST API controllers
│ ├── CLI/ # WP-CLI commands
│ └── Services/ # Business logic
├── src-blocks/ # Block source (JS/CSS per block)
│ └── example-block/
│ ├── block.json
│ ├── edit.js, save.js, index.js
│ ├── editor.scss, style.scss
│ └── view.js # Interactivity API store
├── build/ # Compiled assets (gitignored)
├── assets/ # Static CSS/JS/images
├── languages/ # Translation files
├── templates/ # PHP template partials
├── tests/
│ ├── php/
│ │ ├── Unit/ # Pure PHP tests, no WordPress
│ │ ├── Integration/ # Tests using WP test framework
│ │ └── bootstrap.php
│ └── e2e/ # Playwright tests
└── vendor/ # Composer deps (gitignored)
To modify the plugin's behaviour:
- Coding standards and patterns: Edit
skills/wordpress-plugin-developer/SKILL.md - Detailed examples and templates: Edit the relevant file in
references/ - Task generation workflow: Edit
commands/plugin-tasks/SKILL.md - Build execution workflow: Edit
commands/plugin-build/SKILL.md - Plugin metadata: Edit
.claude-plugin/plugin.json
Skill and command files use YAML frontmatter for metadata (name, description, allowed-tools, etc.) followed by markdown instructions that Claude follows at runtime.
GPL-2.0-or-later