poocommerce

Add or modify PooCommerce backend PHP code following project conventions. Use when creating new classes, methods, hooks, or modifying existing backend code. **MUST be invoked before writing any PHP unit tests.**

Review PooCommerce code changes for coding standards compliance. Use when reviewing code locally, performing automated PR reviews, or checking code quality.

Guidelines for UI text and copy in PooCommerce. Use when writing user-facing text, labels, buttons, or messages.

Run tests, linting, and quality checks for PooCommerce development. Use when running tests, fixing code style, or following the development workflow.

Setup and develop the PooCommerce block email editor. Use when working on email templates, transactional emails, or the email editor feature.

Commit uncommitted changes with well-crafted messages following PooCommerce repo conventions. Use when the user says "commit", "commit changes", "commit this", "git commit", or "save my work".

Create a high-quality draft PR for the current branch. Use when the user says "create a PR", "draft PR", "open a PR", "make a PR", "push and create PR", or "submit PR".

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.

Guidelines for creating and modifying markdown files in PooCommerce. Use when writing documentation, README files, or any markdown content.

Identify performance issues in PooCommerce PHP code. Use when writing or reviewing code that loads collections of post-based objects (products, orders), renders product lists with images, reads multiple options in a loop or method, or writes SQL queries involving joins, aggregates, meta lookups, or range queries.

Add or modify routes in the PooCommerce Store API (`/wc/store/v1/*`). Use when creating new Store API endpoints, modifying existing ones, or designing the schemas blocks and external integrations consume. Covers authentication, REST URL design, schema/response alignment, variation handling, idempotency, and common pitfalls.