woo-setup
Install WooCommerce, configure the development stack, and set up a local dev environment with WP-CLI, Docker, or wp-env. Use when setting up a new WooCommerce project or development environment.
Best use case
woo-setup is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Install WooCommerce, configure the development stack, and set up a local dev environment with WP-CLI, Docker, or wp-env. Use when setting up a new WooCommerce project or development environment.
Teams using woo-setup should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/woo-setup/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How woo-setup Compares
| Feature / Agent | woo-setup | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Install WooCommerce, configure the development stack, and set up a local dev environment with WP-CLI, Docker, or wp-env. Use when setting up a new WooCommerce project or development environment.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# WooCommerce Installation & Environment Setup
## Before writing code
**Fetch live docs**:
1. Fetch `https://developer.woocommerce.com/docs/` for the getting started guide
2. Web-search `site:developer.wordpress.org cli commands` for WP-CLI reference
3. Web-search `woocommerce system requirements latest version` for current requirements
## System Requirements
### Minimum Stack
| Component | Requirement |
|-----------|-------------|
| PHP | 7.4+ (8.0–8.3 recommended) |
| MySQL | 8.0+ |
| MariaDB | 10.4+ |
| WordPress | 6.4+ |
| WooCommerce | 9.x (latest) |
| HTTPS | Required for payment gateways |
| max_execution_time | 120+ seconds |
| memory_limit | 256M+ |
### Recommended PHP Extensions
`curl`, `gd`, `intl`, `mbstring`, `openssl`, `xml`, `zip`, `sodium`, `imagick`
## Local Development Options
### wp-env (Official WordPress)
WordPress's official Docker-based local environment:
- `npm -g i @wordpress/env` then `wp-env start`
- Configured via `.wp-env.json` in project root
- Supports specifying WordPress version, plugins, themes, PHP version
- Includes WP-CLI access: `wp-env run cli wp <command>`
### Docker Compose
Custom Docker setup with `wordpress`, `mysql`/`mariadb`, optional `phpmyadmin`, `mailhog` containers. Mount plugin/theme directories into the WordPress container.
### Local by Flywheel / DDEV / Lando
GUI or CLI tools that provision WordPress-ready environments with configurable PHP, MySQL, and web server versions.
## WP-CLI Setup
### Essential WooCommerce Commands
- `wp plugin install woocommerce --activate` — install and activate
- `wp wc update` — run WooCommerce database migrations
- `wp wc setting list general` — view store settings
- `wp wc product list` — list products
- `wp wc order list` — list orders
- `wp wc tool run install_pages` — create default WooCommerce pages (shop, cart, checkout)
### Scaffold a WooCommerce Extension
- `wp scaffold plugin my-woo-extension` — generate boilerplate plugin
- Add WooCommerce headers: `WC requires at least`, `WC tested up to`
## Project Bootstrapping
### Recommended Plugin Structure
```
my-woo-extension/
├── my-woo-extension.php # Main plugin file with headers
├── includes/ # PHP classes
├── src/ # Namespaced source (PSR-4 autoloaded)
├── assets/
│ ├── css/
│ └── js/
├── templates/ # Overridable templates
├── languages/ # i18n .pot/.po/.mo files
├── tests/ # PHPUnit tests
├── composer.json # Dependencies + autoloading
├── package.json # JS build tooling (if blocks)
└── readme.txt # WordPress.org plugin header
```
### Main Plugin File Headers
Required headers for WooCommerce extensions:
- `Plugin Name`, `Plugin URI`, `Description`, `Version`, `Author`, `License`
- `WC requires at least: 8.0` — minimum WooCommerce version
- `WC tested up to: 9.5` — tested WooCommerce version
- `Requires Plugins: woocommerce` — WordPress 6.5+ dependency declaration
### HPOS Compatibility Declaration
Every new extension must declare HPOS compatibility:
```php
add_action( 'before_woocommerce_init', function() {
if ( class_exists( \Automattic\WooCommerce\Utilities\FeaturesUtil::class ) ) {
\Automattic\WooCommerce\Utilities\FeaturesUtil::declare_compatibility(
'custom_order_tables', __FILE__, true
);
}
});
```
## Best Practices
- Always declare HPOS (`custom_order_tables`) compatibility in new extensions
- Use Composer autoloading (PSR-4) for namespaced classes
- Set `WC requires at least` and `WC tested up to` headers
- Use `wp-env` or Docker for reproducible development environments
- Run `wp wc tool run install_pages` after fresh WooCommerce install
Fetch the WooCommerce getting started guide and WP-CLI docs for exact commands and configuration options before setting up.Related Skills
webmcp-setup
Set up a WebMCP project — enable Chrome flags, install MCP-B polyfill, scaffold tool registration, and configure development environment. Use when starting a new WebMCP-enabled website from scratch.
ucp-setup
Set up a UCP project — scaffold a merchant server or platform client with discovery profile, SDK installation, and project structure. Use when starting a new UCP implementation.
mpp-setup
Scaffold an MPP project — install mppx SDK, configure payment methods, set up server middleware, and create a basic paid API endpoint. Use when starting a new MPP machine payments project from scratch.
spree-setup
Bootstrap a new Spree project — `create-spree-app` CLI (v5.2+), `spree-starter` Rails backend, the Next.js storefront repo, `bin/rails g spree:install`, sample data, Docker Compose, and the PostgreSQL + Redis + Sidekiq prerequisites. Use when starting a new Spree project from scratch or onboarding an existing repo.
shopify-setup
Set up a Shopify development environment — Shopify CLI installation, Partner account, development stores, environment variables, project structures for themes, apps, and Hydrogen. Use when starting a new Shopify project.
sf-setup
Set up a Salesforce Commerce development environment — sfcc-ci CLI for B2C, sf CLI for B2B, Business Manager access, sandbox management, dw.json configuration, .sfdx project setup, and project structures for SFRA, PWA Kit, and Lightning. Use when starting a new Salesforce Commerce project.
saleor-setup
Set up a Saleor development environment — saleor-platform Docker Compose, CLI, PostgreSQL/Redis prerequisites, manage.py commands, environment variables, project structure. Use when starting a new Saleor project.
nlweb-setup
Bootstrap a local NLWeb development environment from scratch — clone the repo, configure .env, install Python deps via `nlweb init-python`, run `nlweb init` for interactive LLM/retrieval selection, load sample Schema.org data, and verify with `nlweb check`. Use when starting a new NLWeb deployment from zero.
medusa-setup
Set up a Medusa v2 development environment — CLI, PostgreSQL/Redis prerequisites, project creation, medusa-config.ts, directory structure, environment variables. Use when starting a new Medusa project.
magento-setup
Set up a Magento 2 Open Source project — installation, Composer setup, system requirements verification, and initial configuration. Use when starting a new Magento project or setting up a development environment.
bc-setup
Set up a BigCommerce development environment — Stencil CLI, API credentials, sandbox stores, Catalyst, and developer tools. Use when starting a new BigCommerce project or configuring development tools.
ap2-setup
Scaffold a new AP2 project — install the SDK, set up agent roles, configure credentials, and create a basic multi-agent payment system. Use when starting a new AP2 agentic payments project from scratch.