wp-plugin-development

Use this skill for plugin work such as: If this is a full site repo, pick the specific plugin under wp-content/plugins/ or mu-plugins/ before changing code. Guidelines: See: Activation hooks are fragile; follow guardrails: See: Prefer Settings API for options: See: Before shipping: See: See: See: For canonical detail, consult the Plugin Handbook and security guidelines before inventing patterns. - creating or refactoring plugin structure (bootstrap, includes, namespaces/classes) - adding hooks/actions/filters - activation/deactivation/uninstall behavior and migrations - adding settings pages / options / admin UI (Settings API) - security fixes (nonces, capabilities, sanitization/escaping, SQL safety) - packaging a release (build artifacts, readme, assets) - Repo root + target plugin(s) (path to plugin main file if known). - Where this plugin runs: single site vs multisite; WP.com conventions if applicable. - Target WordPress + PHP versions (affects available APIs and placeholder support in $wpdb->prepare() ). - Run triage: - node skills/wp-project-triage/scripts/detect_wp_project.mjs - Detect plugin headers (deterministic scan): - node skills/wp-plugin-development/scripts/detect_plugins.mjs - Keep a single bootstrap (main plugin file with header). - Avoid heavy side effects at file load time; load on hooks. - Prefer a dedicated loader/class to register hooks.