WordPress Playground

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.

Procedure

Identify the user intent: Blueprint authoring/review, local CLI execution, browser-only website/share link workflow, Xdebug/stuck CLI run, or a mixed Playground request.
Route to the focused source below, loading more than one only when the request has multiple distinct parts.
For mixed requests, delegate Blueprint JSON work to blueprint, then return here for runtime, CLI, debugging, or sharing guidance.

Blueprint JSON, schema, steps, resources, bundles, or Blueprint review: use the blueprint skill directly. Do not duplicate Blueprint schema details here.
Local CLI execution: read references/cli.md for @wp-playground/cli server, run-blueprint, build-snapshot, mounts, version switching, and local validation.
Xdebug or stuck CLI runs: read references/debugging.md for Xdebug, runtime logs, worker flags, and stuck CLI runs.
Browser-only Playground website workflows: read 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.