@wordpress

wp-playground spins up ephemeral wordpress instances for plugin/theme testing, blueprint validation, and cross-version compatibility checks without full infrastructure setup.

wp-rest-api covers registration and debugging of custom REST endpoints, schema validation, authentication modes, and response field management across WordPress plugins and themes.

wp-phpstan guides setup and error resolution for phpstan in wordpress projects, covering config generation, stub management, baseline migrations, and wordpress-specific type annotations for hooks and rest endpoints.

wp-performance provides a structured backend-only profiling workflow for wordpress diagnostics using wp-cli, query monitor headless mode, and targeted fixes by bottleneck category (db queries, autoload, caching, http calls, cron).

wp-project-triage runs a Node.js detector to classify WordPress repository structure, identify tooling/tests/versions, and surface project metadata needed before making changes.

wordpress-router classifies wordpress repository types (plugin, theme, block theme, gutenberg blocks, core) and delegates to domain-specific workflows. classification runs automated triage with repo type detection and downstream routing.

wp-plugin-directory-guidelines maps the 18 wordpress.org plugin submission rules, focusing on gpl compliance, licensing headers, and freemium/trialware restrictions. lacks procedural depth for practical plugin audits.

Use when developing WordPress (Gutenberg) blocks: block.json metadata, register_block_type(_from_metadata), attributes/serialization, supports, dynamic…

Use when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor…

Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security…

Use when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing,…

Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.

Use when building or debugging WordPress Interactivity API features (data-wp-* directives, @wordpress/interactivity store/state/actions, block viewScriptModule…

Use when working with the WordPress Abilities API (wp_register_ability, wp_register_ability_category, /wp-json/wp-abilities/v1/*, @wordpress/abilities)…

Use when creating, editing, or reviewing WordPress Playground blueprint JSON files. Triggers on mentions of blueprints, playground configuration, or requests…