wp-plugin-standardslisted

# WordPress Plugin Standards Companion to `wp-plugin-development`. Apply this skill when a plugin must pass WordPress.org Plugin Check (PCP), or when improving code quality, documentation, or submission readiness. ## When to use this skill - Writing or modifying WordPress plugin PHP files - Preparing a plugin for WordPress.org submission - Reviewing plugin code for security, quality, or standards compliance - Any task where plugin code reuse, documentation, or versioning is involved ## Mandatory workflow **Step 0 is always required and may never be skipped.** Do not modify any file until the user explicitly confirms they want to proceed after reviewing the report. ### Step 0 — Review report (always first) **Before scanning files, derive the expected WordPress.org slug:** Take the `Plugin Name:` header value, lowercase it, replace spaces with hyphens, and strip special characters. This is the expected `Text Domain:` value. If the plugin header `Text Domain:` does not match this derived slug, flag it as **Critical** immediately — this generates 70+ errors in PCP. Example: "CloudScale Free Backup and Restore" → `cloudscale-free-backup-and-restore`. **Then review against the 18 Detailed Plugin Guidelines** (`references/wordpress-org-guidelines.md`) — these are the human-reviewer policy rules that Plugin Check does **not** catch and that cause most repeat rejections of otherwise-clean code. Explicitly check: trialware / locked features (G5), tracking without explicit opt-i