Japanized-for-WooCommerce

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.

Use when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing, multisite, and scripting/automation with wp-cli.yml.

Paygent銀行・コンビニ系決済スキル。仮想口座決済（ATM）・銀行ネット決済・口座振替・ コンビニ決済（番号方式・チケット発券）・電子マネー（WebMoney）をカバー。 「paygent_atm」「WC_Gateway_Paygent_ATM」「paygent_cs」「WC_Gateway_Paygent_CS」 「paygent_bn」「WC_Gateway_Paygent_BN」「仮想口座」「コンビニ」「銀行ネット」「口座振替」 などのキーワードで発動。

Paygentキャリア決済スキル。auかんたん決済・d払い・ソフトバンクまとめて支払い(B)・ ワイモバイルまとめて支払い の都度課金と継続課金をカバー。 「paygent_mb」「WC_Gateway_Paygent_MB」「キャリア決済」「auかんたん決済」「d払い」 「ソフトバンク」「携帯決済」「career_type」「addon-mb」などのキーワードで発動。

Paygentクレジットカード決済スキル。通常カード決済（トークン決済）、EMV 3Dセキュア 2.0、 継続課金（WooCommerce Subscriptions連携）、多通貨決済、デビット・プリペイド判定、 カード情報保存（トークナイゼーション）をカバー。 「paygent_cc」「WC_Gateway_Paygent_CC」「tds2」「3Dセキュア」「継続課金」「トークン決済」 「クレジットカード」「paygent_mccc」「多通貨」「addon-cc」などのキーワードで発動。

Paygent決済ゲートウェイの共通コア処理スキル。PaygentB2BModule経由のAPI通信、 認証情報管理、ハッシュチェック、エラーハンドリング、注文IDマッピング、Webhook受信、 デバッグログ、テスト環境設定など全決済手段で共有される基盤処理をカバー。 「paygent API」「telegram_kind」「PaygentB2BModule」「send_paygent_request」 「wc-paygent-mid」「ハッシュチェック」「WC_Gateway_Paygent_Request」などのキーワードで発動。

Paygentデジタル決済スキル。PayPay・Paidy・楽天ペイ・Apple Pay・Google Pay・Alipay国際決済・ 銀聯ネット決済をカバー。これらはすべてリダイレクト型決済（woocommerce_receipt_フック）。 「paygent_paypay」「WC_Gateway_Paygent_PayPay」「paygent_paidy」「paygent_rakuten」 「PayPay」「Paidy」「楽天ペイ」「Apple Pay」「Google Pay」「Alipay」「銀聯」 などのキーワードで発動。

Skill for creating sales content (product pages, documentation, FAQs, etc.) for the WooCommerce.com Marketplace. Generates product page content (name, short description, long description, media gallery, FAQ), user documentation (installation instructions, setup guide, configuration reference, troubleshooting), developer documentation (hooks/filters list, template overrides), and visual asset instructions aligned with screenshot guidelines. Use when keywords like "write product page", "create documentation", "write FAQ", "usage guide", "marketplace description", "plugin description", "installation instructions", "setup guide", "troubleshooting", "hook reference", or "screenshot guide" appear. Also reference proactively when consulted about preparing WooCommerce plugins for sale or content creation.

Use for security audits of WordPress plugins: nonce validation, capability checks, input sanitization, output escaping, SQL injection prevention, CSRF protection, PCI DSS compliance for payment plugins, and WooCommerce-specific security patterns.

Skill for recommending pricing for plugins sold on the WooCommerce.com Marketplace. Gathers information about the plugin's feature category, complexity, and target market, researches competitor pricing in the marketplace, and proposes an optimal annual subscription price factoring in the 70/30 revenue split. Also covers pricing tier design, Freemium model decisions, pricing for the Japanese market, and monthly plan design using the SaaS Billing API. Use when keywords like "pricing", "how much to charge", "how much to sell for", "annual subscription", "monthly pricing", "Freemium decision", "competitor research", "revenue simulation", or "price point" appear. Also reference proactively when consulting on business model or profitability for a WooCommerce plugin.