wp-playground

Provision disposable WordPress instances for plugin and theme testing.

1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/javiercasares/cloudfest-wporgdownload --skill wp-playground-javiercasares
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wp-playground
Source: https://github.com/javiercasares/cloudfest-wporgdownload/tree/main/.claude/skills/wp-playground
Command: npx skills add https://github.com/javiercasares/cloudfest-wporgdownload --skill wp-playground-javiercasares

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables developers to rapidly prototype WordPress plugins/themes by providing disposable WordPress instances (in-browser or local) for testing, debugging, and iteration without a full stack setup.

Core Features & Use Cases

  • Disposable environments: Spin up isolated WP instances quickly for testing plugins, themes, or blueprint-driven workflows.
  • Blueprints & snapshots: Build repeatable environments via blueprints and export/import snapshots for CI or sharing.
  • Version switching & debugging: Switch WordPress/PHP versions on demand and debug with integrated tooling (Xdebug) in a contained Playground.

Quick Start

Install Node.js 20.18+, install the WP Playground CLI, then start a server with automatic mounting:

  • npx @wp-playground/cli@latest server --auto-mount
  • Open http://localhost:9400 to interact with the WP instance.

Frequently Asked Questions about wp-playground

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

FAQPage Schema
How do I create disposable WordPress instances for testing plugins locally?

Disposable WordPress instances for testing plugins are provisioned via the WP Playground CLI running on Node.js 20.18+, which auto-mounts local assets and provides isolated browser-backed or WASM environments without requiring a full stack setup.

What is a WordPress playground blueprint and how does it work?

A WordPress playground blueprint is a configuration file that defines repeatable environment setups, allowing you to automate plugin/theme installation and configuration. Blueprints enable consistent testing workflows across local development and CI pipelines by standardizing the environment state.

Can I switch WordPress and PHP versions on demand for debugging?

Yes, you can switch WordPress and PHP versions on demand within the playground environment. This allows you to test plugin compatibility across different versions and debug with integrated tooling like Xdebug in a contained instance.

Do I need a full WordPress installation to prototype themes in a CI pipeline?

No, you do not need a full WordPress installation to prototype themes in a CI pipeline. The WP Playground CLI provisions isolated WASM or browser-backed instances with auto-mounting, enabling automated testing and snapshot exports without traditional server infrastructure.

What's the best way to share a WordPress testing environment with my team?

The best way to share a WordPress testing environment is by using blueprint-driven setups and exporting build-snapshots. This allows team members to import the exact environment state into their own local WP Playground CLI instances for consistent testing.

Why does my WP Playground CLI server fail to start?

Your WP Playground CLI server fails to start if your environment does not meet the Node.js 20.18+ requirement. Ensure you have the correct Node.js version installed and run the server command with automatic mounting enabled on port 9400.