# Build WordPress Playground Workflows

WordPress testing often needs fast, isolated sites without Docker or a database. This skill guides Playground CLI, blueprints, snapshots, versions, mounts, and debugging.

## Install

```bash
npx skillstore add automattic/wp-playground
```

## Metadata

- - Status: approved
- - Slug: automattic-wp-playground
- - Version: 1.0.0
- - Author: Automattic
- - GitHub username: Automattic
- - License: MIT
- - Repository: https://github.com/Automattic/agent-skills/tree/trunk/skills/wp-playground
- - Ref: trunk
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: medium
- - Risk factors: external\_commands, network, filesystem
- - Quality score: 50
- - Quality tier: warning
- - Public page: https://skillstore.pages.dev/skills/automattic-wp-playground
- - Manifest: https://skillstore.pages.dev/api/skills/automattic-wp-playground/manifest

## Capabilities

- Start local WordPress Playground servers with auto-mounted plugin or theme projects.
- Run Playground blueprints from local files or approved URLs.
- Build shareable Playground snapshots for bug reports or review workflows.
- Switch WordPress and PHP versions for compatibility testing.
- Set up Xdebug-oriented debugging steps for mounted plugin or theme code.
- Troubleshoot mounts, ports, blueprint assets, and slow Playground runs.

## Use Cases

- Test Plugin Changes Locally: Mount a plugin directory into a disposable Playground site and verify activation, UI paths, and version compatibility.
- Share Reproducible Bug Reports: Create a blueprint or snapshot that reproduces a site state for reviewers without a full local stack.
- Debug Theme Behavior: Run a mounted theme with Xdebug guidance and targeted troubleshooting for paths, ports, and slow runs.

## Prompt Templates

### Start A Local Playground

```
Help me start WordPress Playground for this plugin or theme. Check prerequisites, choose safe defaults, and explain each command before running it.
```

### Create A Test Blueprint

```
Design a WordPress Playground blueprint for my test scenario. Include required steps, local files, version choices, and safety notes for remote resources.
```

### Build A Shareable Snapshot

```
Guide me through building a Playground snapshot from my blueprint. Validate the setup, choose an output name, and list verification steps.
```

### Debug A Mounted Project

```
Troubleshoot my WordPress Playground run with Xdebug. Review mounts, port conflicts, version flags, blueprint access, and breakpoint path mappings.
```

## Limitations

- It does not replace a production WordPress stack or full database environment.
- It requires Node.js, npm or npx, and a compatible Playground CLI release.
- It cannot guarantee untrusted blueprints or remote ZIP files are safe.
- Some PHP extensions, native databases, and hosting-specific behavior may not match production.

## Best Practices

- Review every blueprint and remote ZIP URL before running it locally.
- Mount the smallest project directory needed, and remove secrets before testing.
- Pin WordPress, PHP, and CLI versions when reproducing bugs or sharing snapshots.

## Anti Patterns

- Do not run untrusted blueprints with PHP execution or file-writing steps.
- Do not mount production directories, secrets, uploads, or database exports into Playground.
- Do not rely on ephemeral Playground state as a permanent development environment.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T11:52:05.57\+00:00
- - Summary: Static command and weak-cryptography alerts were mostly markdown false positives, with no prompt injection or malicious intent found. The skill does provide legitimate instructions for npx CLI execution, remote blueprint resources, local file mounting, PHP execution, and file-writing blueprint steps, so publication should include a medium-risk warning.

## Stats

- - Views: 279
- - Downloads: 5
- - Favorites: 0
- - Popularity score: 0