Wp Plugin Development

WordPress plugin architecture review and WordPress.org submission standards. Use when reviewing WordPress plugin code, auditing plugin architecture, preparing WordPress.org plugin submission, checking plugin best practices, analyzing custom post types, taxonomies, Settings API, hooks system, internationalization, or when user mentions "plugin review", "plugin development", "plugin best practices", "WordPress.org submission", "Plugin Check", "plugin headers", "activation hook", "deactivation hook", "uninstall", "custom post type", "taxonomy", "Settings API", "hooks", "actions", "filters", "i18n

116 stars 13 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jorgerosal/wordpress-skills --skill wp-plugin-development
Manual install
git clone --depth 1 https://github.com/jorgerosal/wordpress-skills.git /tmp/wordpress-skills
mkdir -p ~/.claude/skills
cp -r /tmp/wordpress-skills/claude-skills/wp-plugin-development ~/.claude/skills/wp-plugin-development

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# WordPress Plugin Development Review Skill

## Overview

Systematic plugin architecture review for WordPress plugins targeting WordPress 6.x+. **Core principle:** WordPress plugins extend functionality through a standardized API ecosystem—lifecycle hooks (activation/deactivation/uninstall), Settings API, hooks system (actions/filters), custom post types/taxonomies, and internationalization. Review validates plugin architecture, naming conventions, WordPress.org compliance standards, and cross-references wp-security-review for security-specific patterns (nonces, capabilities, sanitization). Report findings grouped by file with line numbers, severity labels (CRITICAL/WARNING/INFO), and BAD/GOOD code pairs showing proper implementations.

## When to Use

**Use when:**
- Plugin code architecture review
- Pre-submission check for WordPress.org Plugin Directory
- Auditing plugin lifecycle hooks (activation/deactivation/uninstall)
- Reviewing custom post type or taxonomy registration
- Validating Settings API implementation
- Checking hooks system usage (actions/filters, priority, removal)
- Internationalization (i18n/l10n) audit
- WordPress Plugin Check (PCP) compliance verification
- Prefixing and namespace collision detection

**Don't use for:**
- Theme development (use wp-theme-development when available)
- Gutenberg block development (use wp-block-development when available)
- WooCommerce extension development (use wp-woocommerce-dev when available)
Read the full skill on GitHub

Details

Skill name
wp-plugin-development
Path
claude-skills/wp-plugin-development/SKILL.md
License
MIT
Repo updated
7 June 2026

FAQ

What does the Wp Plugin Development skill do?

WordPress plugin architecture review and WordPress.org submission standards. Use when reviewing WordPress plugin code, auditing plugin architecture, preparing WordPress.org plugin submission, checking plugin best practices, analyzing custom post types, taxonomies, Settings API, hooks system, internationalization, or when user mentions "plugin review", "plugin development", "plugin best practices", "WordPress.org submission", "Plugin Check", "plugin headers", "activation hook", "deactivation hook", "uninstall", "custom post type", "taxonomy", "Settings API", "hooks", "actions", "filters", "i18n

How do I install the Wp Plugin Development skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add jorgerosal/wordpress-skills --skill wp-plugin-development. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Wp Plugin Development popular?

It lives in jorgerosal/wordpress-skills, which has 116 GitHub stars and 13 forks.

Related skills

Wp Accessibility Review

116

jorgerosal/wordpress-skills

WordPress accessibility review for themes, blocks, plugins, and admin interfaces. Use when reviewing keyboard navigation, focus behavior, semantic HTML, ARIA usage, form labeling, screen-reader support, contrast-related implementation issues, or when user mentions "accessibility review", "a11y", "keyboard navigation", "focus management", "screen reader", "ARIA", "semantic HTML", "accessible form", or "accessible block". Detects implementation-level accessibility issues in frontend output, block markup, admin screens, and interactive UI behavior.

Frontend & Design13

Wp Accessibility Review

116

jorgerosal/wordpress-skills

WordPress accessibility review for Codex. Use when reviewing semantic HTML, keyboard access, focus behavior, form labels, ARIA usage, and accessible interaction patterns in themes, blocks, plugins, and admin screens.

Frontend & Design13

Wp Acf and Content Modeling

116

jorgerosal/wordpress-skills

WordPress ACF and content modeling review. Use when reviewing Advanced Custom Fields usage, field group architecture, CPT and taxonomy design, options pages, repeaters, flexible content, block-bound field groups, meta storage patterns, or when user mentions "ACF", "field groups", "flexible content", "repeater", "custom post type design", "taxonomy design", "content model", "relationship fields", "ACF JSON", "options page", or "meta query performance". Detects schema drift, weak content modeling, brittle field naming, and performance issues in meta-heavy WordPress builds.

AI, LLMs & Agents13

Wp Plugin Development

116

jorgerosal/wordpress-skills

WordPress plugin architecture review for Codex. Use when reviewing plugin structure, lifecycle hooks, Settings API usage, CPT and taxonomy registration, hook design, i18n, and WordPress.org readiness.

Software Development13

Wp Playground Development

116

jorgerosal/wordpress-skills

WordPress Playground review for Codex. Use when reviewing Blueprints, Playground CLI usage, embedded Playground demos, reproducible WordPress setups, or zero-setup bug repro environments.

Software Development13

Wp Rest API Development

116

jorgerosal/wordpress-skills

WordPress REST API review and development guidance. Use when reviewing custom REST routes, permission_callback logic, schema design, WP_REST_Request handling, response structure, versioning, controller classes, nonce or auth usage, or when user mentions "REST API review", "register_rest_route", "permission_callback", "WP_REST_Request", "REST endpoint", "custom API", "API schema", "REST controller", "headless WordPress", or "API auth". Detects route registration issues, authorization mistakes, schema drift, input validation gaps, and response design problems in WordPress REST API code.

Software Development13

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.