Use as the WordPress Playground routing wrapper for ambiguous Playground work, local CLI runs with @wp-playground/cli, playground.wordpress.net share links, browser previews, WebMCP site tools, snapshots, mounts, version switching, and Xdebug. For Blueprint JSON authoring or review, use the blueprint skill directly.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
This is a thin routing wrapper. Use it to pick the right Playground workflow, then load only the focused reference or skill needed for the task.
blueprint, then return here for runtime, CLI, debugging, or sharing guidance.blueprint skill directly. Do not duplicate Blueprint schema details here.references/cli.md for @wp-playground/cli server, run-blueprint, build-snapshot, mounts, version switching, and local validation.references/debugging.md for Xdebug, runtime logs, worker flags, and stuck CLI runs.references/website.md for Query API and Blueprint URL setup, share links, and browser limitations. It routes existing-site operations to separate WebMCP, Playground MCP, and Sites API references; load only the selected method. Unless the user requests a specific connection method, prefer available WebMCP tools for supported browser operations.blueprint so the schema and examples have one source of truth.npm/npx before running commands.blueprint skill verification.blueprint skill for schema keys, steps, resources, bundles, validation, or Blueprint review.references/cli.md; playground.wordpress.net cannot read local filesystem paths.references/website.md; local server URLs are not portable share links.references/debugging.md directly for Xdebug, logs, worker flags, and stuck CLI runs.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when the deliverable is WordPress Playground Blueprint JSON or a Blueprint bundle, including creating, editing, reviewing, validating schema keys, choosing steps/resources, and debugging Blueprint files. For only running or sharing a Playground environment, use wp-playground.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks about WordPress codebases (plugins, themes, block themes, Gutenberg blocks, WP core checkouts) and you need to quickly classify the repo and route to the correct workflow/skill (blocks, theme.json, REST API, WP-CLI, performance, security, testing, release packaging).
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with the WordPress Abilities API (wp_register_ability, wp_register_ability_category, /wp-json/wp-abilities/v1/*, @wordpress/abilities) including defining abilities, categories, meta, REST exposure, and permissions checks for clients.
日本語の概要は準備中です。原文の説明を表示しています。
Audit a WordPress plugin's REST surface and produce a standardized audit document proposing Abilities API registrations. Produces a markdown doc with a YAML schema and prose sections that humans and agents can both consume when planning a registration rollout. Works on any WP plugin.
日本語の概要は準備中です。原文の説明を表示しています。
Verify a WordPress plugin's Abilities API registrations: enumerate abilities, check that callback behavior matches each annotation's claim (the adversarial readonly-but-writes detection), validate permissions and schemas, and validate audit documents produced by wp-abilities-audit.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。