Стандарты WordPress для плагинов

★ 6.9 · regulation-compliance

WordPress Compliance is a Claude Code skill that enforces WordPress.org requirements and repository PHPCS rules when editing templates, admin UI, hooks, plugin metadata, sanitization, escaping, or any code that must pass Plugin Check. Reach for it when a plugin gets rejected by the WordPress.org review team for unsafe output, when a code reviewer flags missing escaping or wrong capability checks, when you need to drop jQuery in favor of native DOM APIs, or when WP Rocket–specific capabilities must replace the forbidden `manage_options`. The skill embeds context-aware escaping rules — `esc_html()`, `esc_attr()`, `esc_url()`, `wp_kses_post()` — the full set of WP Rocket custom capabilities (`rocket_manage_options`, `rocket_purge_cache`, and others), the `rocket` text domain for i18n, and links to in-repo specs under `.claude/specs/phpcs/`. A key anti-pattern it catches: storing API keys or tokens as static files under `wp-content/` without real access control — `.htaccess deny` does not protect against Nginx, and an `index.php` stub does not block sibling files served directly from disk; secrets must live outside the web tree or be delivered through a `current_user_can()`-gated PHP handler. The skill checks and corrects code for compliance rather than generating arbitrary WordPress business logic.