WordPress Plugin Developer - Claude Code Plugin
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.
What It Does
This plugin adds four things to your Claude Code sessions:
1. WordPress Plugin Developer Skill
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
2. /plugin-plan Command
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.
3. /plugin-tasks Command
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.
4. /plugin-build Command
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.
Installation
1. Clone the plugin
Clone this repo into a directory where you keep your Claude Code plugins:
mkdir -p ~/.claude/plugins
git clone <repo-url> ~/.claude/plugins/wordpress-plugin
You can clone it anywhere you like — ~/.claude/plugins/ is just a convention.
2. Use it in a session
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-plugin
This loads the WordPress plugin developer skill and commands for that session only, keeping your other Claude sessions clean.
Verify it's loaded
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.
Usage
Starting a new plugin from scratch
- 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
