ワンクリックで
testing-wp-runtime
Guidelines for running wp-now to validate WordPress plugins and themes at runtime
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Guidelines for running wp-now to validate WordPress plugins and themes at runtime
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Import and rebuild a website from a closed platform (Wix, Squarespace, Webflow, Shopify, GoDaddy, Hostinger, HubSpot, Weebly) into a Studio WordPress site. Extracts pages/posts/products + media, then reconstructs the design as editable blocks + WooCommerce OR as a high-fidelity replica theme. Invoke when the user wants to migrate, import, liberate, or rebuild a site from one of these platforms.
Choose recommended plugins and plugin-provided blocks for features core WordPress blocks do not cover - ecommerce (WooCommerce), forms and newsletters (Jetpack), online courses and quizzes (Sensei LMS), polls, surveys and ratings (Crowdsignal), spam protection (Akismet) - while keeping generated content editable and avoiding raw HTML fallbacks. Any request to sell products or build a shop, store, or storefront requires WooCommerce with products.
Gather the site name and layout preference before building a WordPress site. Run this before creating any new site.
Use the Studio CLI to manage local WordPress sites, authentication, and preview sites. Invoke this skill when you need to run Studio CLI commands, manage sites, or troubleshoot site issues.
Write editable WordPress block markup for local Studio sites, including core/html limits, block-theme layout rules, full-width sections, validation, and skeleton-first page/CSS recipes.
Answer WordPress.com plan, pricing, upgrade, and feature-tier questions (plan names, what each tier unlocks — plugins, themes, custom code, SSH, hosting — and current prices) from authoritative live data. Load before answering ANY plan, pricing, or feature-gating question; never answer these from memory.
| name | testing-wp-runtime |
| description | Guidelines for running wp-now to validate WordPress plugins and themes at runtime |
| disable-model-invocation | true |
Use this skill when you need to verify that a WordPress plugin or theme loads correctly at runtime.
Do not use this skill for static linting — use testing-php or testing-js for that.
wp-now requires a --mode flag based on the project type:
Plugin Name: header): use --mode=pluginstyle.css with Theme Name: header): use --mode=themeCheck the project root to determine which mode to use:
head -20 *.php style.css 2>/dev/null
Start wp-now in the background on an available port:
wp-now start --mode=<plugin|theme> --port=8881 &
Wait a few seconds for the server to initialize, then verify it is running:
curl -s -o /dev/null -w "%{http_code}" http://localhost:8881/
After the server starts, check the WordPress debug log for errors:
find /tmp -name "debug.log" -path "*/wp-content/*" 2>/dev/null | head -1 | xargs tail -50 2>/dev/null
Look for:
Test key endpoints to verify the project works:
# Homepage
curl -s -o /dev/null -w "%{http_code}" http://localhost:8881/
# wp-admin (should redirect to login)
curl -s -o /dev/null -w "%{http_code}" http://localhost:8881/wp-admin/
For plugins, also check if the plugin is active:
curl -s http://localhost:8881/ | grep -c "<plugin-specific-identifier>"
Always stop wp-now when done testing:
kill $(lsof -t -i:8881) 2>/dev/null