@wordpress/env (wp-env)

Zero-config, Docker-based local WordPress development environment for plugins, themes, and core.

When to use

• User asks to set up a local WordPress development environment
• Project contains a .wp-env.json file
• User mentions wp-env, @wordpress/env, or Docker-based WordPress development
• User wants to run WP-CLI commands, PHPUnit tests, or debug with Xdebug locally
• Triage detects a plugin or theme project that needs a local WordPress instance

wp-env or wp-playground? For a quick local WordPress, prefer the wp-playground skill by default — it's faster, disposable, and needs no Docker. Use wp-env when the task actually requires it:

• the repo already contains a .wp-env.json
• a real MySQL database is needed (PHPUnit against the DB, wp db commands, data that survives restarts)
• arbitrary commands must run inside the environment (shell access, Composer, full WP-CLI via wp-env run)
• this is a WordPress core or Gutenberg checkout
• the user explicitly asks for wp-env or Docker