poocommerce-local-env

name	poocommerce-local-env
description	Set up, start, stop, restart, verify, and troubleshoot the PooCommerce Core local development environment with wp-env and asset build watchers. Use when Codex is asked to run PooCommerce locally, prepare wp-env, watch PooCommerce builds, choose between full and targeted build/watch commands, diagnose localhost:8888, or explain local environment setup commands.

PooCommerce Local Environment

Overview

Use this skill to get PooCommerce Core running locally without re-reading plugins/poocommerce/README.md and .wp-env.json.

Prefer short root scripts when present. Fall back to filtered package commands if the aliases are not available.

Process Ownership

Use this ownership model when deciding whether to run a command or tell the user what to run:

• Run setup checks, dependency installs, one-shot builds, and wp-env start/stop commands from the agent when useful for the task. These commands should complete and return control.
• Treat watch:* commands as user-owned long-running processes. Tell the user to run the relevant watcher in a separate terminal unless a short, temporary watcher session is explicitly needed for active verification.
• Reuse an already-running environment when possible.
• Stop or clean up any agent-owned long-running session before finishing.

Quick Commands

Run these from the repository root:

# Start the wp-env development environment at http://localhost:8888/.
pnpm wc:env

# Stop or restart wp-env.
pnpm wc:env:stop
pnpm wc:env:restart


pnpm :watch


pnpm :watch:admin
pnpm :watch:blocks
pnpm :watch:classic-assets


pnpm :build
pnpm :build:admin
pnpm :build:blocks
pnpm :build:classic-assets