wordpress-plugin-developmentlisted

Build WordPress plugins correctly and pass wp.org Plugin Directory review. Covers the full Plugin Developer Handbook (security, hooks, REST, shortcodes, blocks, CPTs/taxonomies, settings/meta, privacy/GDPR, users/roles, HTTP API, WP-Cron, JS/Ajax, i18n, readme/assets/SVN) and the 19 wp.org guidelines that cause closures (trialware, telemetry without opt-in, remote-loaded assets, missing source for minified files, wrong text-domain literal, missing REST permission_callback, vendored library collisions). Use when building a WordPress plugin or fixing a Plugins Team closure, preparing a submission, auditing compliance, responding to Plugin Check warnings, adding REST routes/shortcodes/blocks, registering CPTs/taxonomies/settings/meta, enqueuing scripts, wiring cron or activation hooks, translations, sanitizing/escaping, capability/nonce checks, or bundling PHP libs. Apply proactively on code under `wp-content/plugins/` or when you see `register_rest_route`, `add_shortcode`, `register_post_type`, `register_settin
atlasaidev/claude-wordpress-skill · ★ 0 · Data & Documents · score 72

Install: claude install-skill atlasaidev/claude-wordpress-skill

# WordPress Plugin Development & wp.org Guidelines A field guide for building WordPress plugins correctly and shipping plugins that pass — and stay on — the wp.org directory. It combines two bodies of knowledge: 1. **wp.org Directory survival** — the Plugins Team review cycle is slow and surprising; catch problems before submission, not after closure. 2. **The official Plugin Developer Handbook** — the canonical "how to build it right" reference (basics, security, hooks, data APIs, privacy, cron, i18n, etc.), distilled RULE-first. ## When to use this skill Any time you are reading or writing code under `wp-content/plugins/`. The triggers in the description are not exhaustive — anything touching WordPress plugin APIs from inside a plugin folder is fair game. Skip it for: WordPress theme code (different review track), standalone PHP outside a plugin, pure JS/front-end work that doesn't touch a plugin's PHP. ## How to use this skill The body below is a fast-loading triage layer. For the actual rules and code patterns, jump to the appropriate reference file. **wp.org directory & compliance (closure-survival):** | You are working on… | Open this reference | |---|---| | The closure email itself, or the master list of guidelines | `references/guidelines.md` | | Anything translatable, or any echoed/returned HTML | `references/i18n-and-escaping.md` | | Hooks, paths, settings, uploads, REST routes (compliance angle) | `references/hooks-paths-uploads-rest.md` | | Running