woo-marketplace-extension

Scaffold WooCommerce.com paid plugins with HPOS, Blocks, and Store API compliance.

3|2|Updated Jun 9, 2021
One-click install
npx skills add https://github.com/artisanworkshop/Japanized-for-WooCommerce --skill woo-marketplace-extension-artisanworkshop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: woo-marketplace-extension
Source: https://github.com/artisanworkshop/Japanized-for-WooCommerce/tree/main/.claude/skills/woo-marketplace-extension
Command: npx skills add https://github.com/artisanworkshop/Japanized-for-WooCommerce --skill woo-marketplace-extension-artisanworkshop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers build WooCommerce.com paid extension plugins that meet Marketplace expectations, reducing costly rejection cycles caused by missing requirements or incompatible technical choices.

Core Features & Use Cases

  • Marketplace-ready plugin scaffolding: Ensures the correct directory layout, required files, and consistent naming to support marketplace packaging and review.
  • Correct WooCommerce plugin initialization & lifecycle: Establishes safe initialization patterns plus activation, deactivation, and uninstall behaviors aligned with WordPress standards.
  • HPOS, Blocks, and Store API compliance: Declares High-Performance Order Storage compatibility and integrates with Cart/Checkout blocks and Store API data flows.
  • Security and internationalization guardrails: Enforces nonce/capability checks, sanitization/escaping practices, avoids unsafe storage of sensitive data, and standardizes i18n using a matching text domain.
  • UX guidelines for audit readiness: Prevents disallowed admin UI patterns and reduces review risk through compliant UX choices.

Quick Start

Use the woo-marketplace-extension skill to get a checklist for updating or creating your WooCommerce.com paid extension so it includes HPOS and Blocks compatibility, passes security expectations, and follows marketplace UX and i18n rules.

Frequently Asked Questions about woo-marketplace-extension

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make my WooCommerce extension pass the marketplace review?

WooCommerce marketplace submission requires HPOS compatibility declarations, Cart/Checkout blocks integration via IntegrationInterface, secure nonce validation, and matching text domains. Meeting these technical criteria ensures your extension passes marketplace review without rejection cycles.

What is HPOS compatibility and how does it affect WooCommerce plugin development?

HPOS compatibility in WooCommerce plugins requires declaring High-Performance Order Storage support to prevent order data conflicts and pass marketplace review. Your extension must safely handle custom order tables without falling back to legacy post storage.

How do I add Cart and Checkout Blocks integration to my WooCommerce plugin?

Cart and Checkout Blocks integration requires registering an IntegrationInterface implementation to connect your extension to Store API data flows. This ensures your WooCommerce plugin functions correctly within block-based checkout experiences.

Does WooCommerce marketplace require internationalization for paid extensions?

WooCommerce marketplace requires complete internationalization for paid extensions using a matching text domain across all user-facing strings. Standardizing i18n practices ensures your plugin passes marketplace review and supports global store installations.

What security checks does WooCommerce marketplace review enforce for plugins?

WooCommerce marketplace review enforces nonce verification, capability checks, data sanitization, output escaping, and prohibits unsafe storage of sensitive data. Your extension must follow these secure coding practices to pass audit requirements.

Can I use standard WordPress plugin scaffolding for a WooCommerce marketplace extension?

WooCommerce marketplace extensions require specific directory layouts, consistent naming, and correct plugin headers beyond standard WordPress scaffolding. Your plugin must also establish safe initialization patterns plus activation, deactivation, and uninstall behaviors aligned with WordPress standards.