wp-playground
by WordPressThe wp-playground skill helps you create disposable, reproducible WordPress Playground environments for plugin and theme testing, version switching, blueprints, snapshots, and isolated debugging. It supports browser or CLI workflows via @wp-playground/cli and is especially useful for backend development, QA, and controlled issue reproduction.
This skill scores 84/100, which means it is a solid listing candidate for directory users who want a focused WordPress Playground workflow rather than a generic prompt. The repository gives enough operational detail to trigger the skill correctly, choose the right command, and understand when it fits—especially for disposable test sites, blueprints, snapshots, and debugging. Users should still expect some experimentation caveats, but the install decision is well-supported.
- Strong triggerability: the frontmatter description explicitly names core workflows, required inputs, and compatibility for WordPress Playground, CLI, blueprints, snapshots, and Xdebug.
- Good operational clarity: SKILL.md and references provide concrete commands for server, run-blueprint, build-snapshot, mounts, WP/PHP version selection, and debugging.
- Useful agent leverage: the repo documents repeatable workflows that reduce guesswork for disposable testing, reproducible setup, and isolated debugging.
- Experimental naming and Playground scope mean this is best for ephemeral test workflows, not production environments or broad WordPress administration.
- No install command in SKILL.md and no scripts/resources, so users will rely on CLI guidance in the docs rather than automated setup.
Overview of wp-playground skill
wp-playground is the skill for setting up and working with WordPress Playground instances when you need a disposable, reproducible environment instead of a full local WordPress stack. The wp-playground skill is best for plugin and theme developers, QA testers, and backend developers who want to reproduce issues, test versions, or share a setup that can be run in the browser or through @wp-playground/cli.
What matters most is the job it solves: get a WordPress site running fast, with the right code mounted, the right WP/PHP version selected, and enough control to debug or package the result. It is not a generic “write me a WordPress prompt” skill; it is a practical wp-playground guide for controlled setups, blueprints, snapshots, and isolated testing.
Best fit for disposable WP workflows
Use wp-playground when you need to:
- spin up a temporary WordPress site to validate a plugin or theme change,
- test against a specific WordPress or PHP version,
- run a blueprint or generate a snapshot for sharing,
- debug behavior in isolation without affecting production or a local database.
What makes it different
The strongest differentiators are the CLI workflow, blueprint support, and predictable ephemeral runtime. wp-playground works well when you need repeatability more than a polished UI. It also matters that the environment is SQLite-backed and WebAssembly-based, which changes both performance and constraints compared with a traditional server install.
Important constraints to know first
This is a fit only if you can work within a disposable environment. It is not for production data, long-lived local state, or workflows that require a conventional MySQL-based WordPress stack. For best results, treat it as a controlled test bed and not as a replacement for your main dev environment.
How to Use wp-playground skill
Install and open the source files
Start with the standard wp-playground install path for your directory tooling, then read the skill’s source files before prompting it for work. The key files in this repo are SKILL.md, references/blueprints.md, references/cli-commands.md, and references/debugging.md. Those files tell you what inputs the skill expects and which CLI flags matter.
Turn a rough goal into a usable prompt
A weak prompt says: “Set up WordPress Playground for my plugin.”
A stronger prompt says: “Use wp-playground to create a disposable local instance for the plugin in packages/my-plugin, auto-mount the project, test against WP 6.9 and PHP 8.3, and tell me the exact CLI command plus any mount or blueprint adjustments.”
For wp-playground usage, include:
- the project path,
- whether you want
server,run-blueprint, orbuild-snapshot, - the WordPress and PHP versions,
- whether the code should auto-mount,
- whether you need Xdebug or a blueprint file.
Choose the right workflow first
Use server --auto-mount when you want an interactive instance for live testing. Use run-blueprint when you need a scripted setup that starts and exits. Use build-snapshot when you want a reusable artifact you can hand off or rerun later. If your goal is backend debugging, mention the exact failure mode and ask for Xdebug-friendly steps instead of only asking for a launch command.
Read the repo in this order
A good wp-playground guide starts with SKILL.md, then references/cli-commands.md for command shape, then references/blueprints.md if you need setup automation, and finally references/debugging.md if the task involves breakpoints, mounts, or stuck runs. This order reduces guesswork and keeps you from missing flags like --mount-before-install or --blueprint-may-read-adjacent-files.
wp-playground skill FAQ
Is wp-playground only for frontend demos?
No. The wp-playground skill is especially useful for plugin, theme, and backend development when you need isolated WordPress behavior, reproducible versions, or debug sessions. It is less about visual demos and more about controlled execution.
Do I need a full local WordPress setup first?
Usually no. The point of wp-playground install is to give you a fast environment without provisioning a traditional stack. If you already have a local stack, wp-playground is still useful when you need a clean comparison target or a specific WP/PHP combination.
When should I not use it?
Do not use it for production data, persistent content work, or workflows that depend on MySQL-specific behavior. If your plugin relies on external services, filesystem persistence, or long-running state, wp-playground may be the wrong default unless you can explicitly model those dependencies in a blueprint.
Is it beginner-friendly?
Yes, if the task is simple and you follow the CLI examples closely. The main failure point is vague input: if you do not specify the project path, version targets, or whether you need a blueprint, the result will be less useful. Beginners get the best results when they ask for one clear workflow at a time.
How to Improve wp-playground skill
Give the skill the exact setup variables
The biggest quality gain comes from specifying the project root, desired WP/PHP versions, and whether the code should auto-mount or be explicitly mounted. For example, “Use wp-playground to test plugins/contact-form against WP 6.9 and PHP 8.3 with --auto-mount” is much better than “make it work.”
Mention the failure mode, not just the goal
If you are debugging, say what is broken: installation fails, a plugin hook does not fire, a REST response is wrong, or a version-specific regression only appears on PHP 8.3. That lets the skill choose between server, run-blueprint, and build-snapshot, and it improves the usefulness of any wp-playground for Backend Development workflow.
Watch for mount and blueprint mistakes
Common issues are relative mount paths, files that must exist before install, and blueprints that need local adjacent files. If your first run fails, improve the prompt by adding absolute paths, confirming whether --mount-before-install is needed, and stating whether the blueprint reads local assets. For debugging, ask for Xdebug setup details and the expected IDE mapping.
Iterate with one variable at a time
If the first output is close but not right, change only one thing: WP version, PHP version, mount mode, or blueprint source. That makes it easier to identify whether the issue is with the environment choice, the command flags, or the setup recipe itself.