Skill for quality testing of plugins for the WooCommerce.com Marketplace. Covers all QIT (Quality Insights Toolkit) test suites (Activation, Security, PHPStan, PHP Compatibility, Malware, Woo E2E, Woo API), how to run them locally, GitHub Actions CI integration, writing custom E2E tests, and coding standards compliance via PHPCS/ESLint. Use when keywords like "QIT", "marketplace testing", "quality testing", "security scan", "PHPStan", "Woo E2E", "plugin testing", "pre-submission", "pre-submission check", "PHPCS", or "coding standards" appear. Also reference proactively when designing CI/CD pipelines or test strategies for WooCommerce plugins.
Skill covering the full process from plugin submission to the WooCommerce.com Marketplace through review approval and post-release ongoing operations. Covers all fields of the Vendor Dashboard's Submit Product form (Name, Short description, Best features, Benefits, Rationale, Monthly sales, Competitive comparison, Testing instructions, Notes for reviewers, etc.) with appropriate English text generation, submission package preparation (ZIP naming, changelog format, version consistency), response strategies for the 4-stage review process (Business/Code/UX/Launch preparations, with automated QIT testing as a submission prerequisite), pricing rules (70/30 revenue split, SaaS Billing API), Freemium model configuration, post-release update obligations (minimum every 6 months, quarterly major recommended), and documentation requirements. Use when keywords like "marketplace submission", "Woo submission", "review handling", "Vendor Dashboard", "submission form", "Submit Product", "pricing", "revenue sharing", "Freemiu
WooCommerce extension development skill covering HPOS, payment gateways, Blocks/StoreAPI integration, order management, product data, shipping methods, REST API, and security. Use this skill whenever building, modifying, debugging, or reviewing a WooCommerce extension plugin. Trigger on keywords like "WooCommerce plugin", "WC extension", "payment gateway", "HPOS", "order meta", "wc_get_orders", "checkout block", "Store API", "WC_Payment_Gateway", "shipping method", "product type", "WooCommerce REST API", or any WooCommerce-specific development task. Also trigger when the user references WooCommerce hooks, filters, or classes. This skill targets WooCommerce 9.0+ (current stable: 10.9; 11.0 scheduled 2026-07-28) on WordPress 6.7+ (current stable: 7.0).
Skill for developing paid plugins for the WooCommerce.com Marketplace. Covers plugin scaffolding, file structure, required headers, HPOS compatibility, Blocks/StoreAPI integration, UX guideline compliance, security, and internationalization — everything needed to pass marketplace review. Use when creating a new WooCommerce extension plugin, updating an existing plugin for marketplace compliance, or when keywords like "Woo Marketplace", "sell on WooCommerce.com", "paid plugin", or "extension development" appear. Also reference proactively when asked about WooCommerce plugin structure, HPOS compatibility, or Blocks compatibility.
Use when developing WordPress (Gutenberg) blocks: block.json metadata, register_block_type(_from_metadata), attributes/serialization, supports, dynamic rendering (render.php/render_callback), deprecations/migrations, viewScript vs viewScriptModule, and @wordpress/scripts/@wordpress/create-block build and test workflows.
Use when configuring, running, or fixing PHPStan static analysis in WordPress projects (plugins/themes/sites): phpstan.neon setup, baselines, WordPress-specific typing, and handling third-party plugin classes.
Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.
Use when building, extending, or debugging WordPress REST API endpoints/routes: register_rest_route, WP_REST_Controller/controller classes, schema/argument validation, permission_callback/authentication, response shaping, register_rest_field/register_meta, or exposing CPTs/taxonomies via show_in_rest.