woocommerce-backend-dev

Original：🇺🇸 English

Not Translated

Add or modify WooCommerce backend PHP code following project conventions. Use when creating new classes, methods, hooks, or modifying existing backend code in WooCommerce projects.

2installs

Sourcesecondsky/claude-skills

Added on2026-02-15

NPX Install

npx skill4agent add secondsky/claude-skills woocommerce-backend-dev

SKILL.md Content

WooCommerce Backend Development

This skill provides guidance for developing WooCommerce backend PHP code according to project standards and conventions.

Instructions

Follow WooCommerce project conventions when adding or modifying backend PHP code:

Creating new code structures: See file-entities.md for conventions on creating classes and organizing files (but for new unit test files see unit-tests.md).
Naming conventions: See code-entities.md for naming methods, variables, and parameters
Coding style: See coding-conventions.md for general coding standards and best practices
Working with hooks: See hooks.md for hook callback conventions and documentation
Dependency injection: See dependency-injection.md for DI container usage
Data integrity: See data-integrity.md for ensuring data integrity when performing CRUD operations
Writing tests: See unit-tests.md for unit testing conventions

Key Principles

Always follow WordPress Coding Standards
Use class methods instead of standalone functions
Place new internal classes in
```
src/Internal/
```
by default
Use PSR-4 autoloading with
```
Automattic\WooCommerce
```
namespace
Write comprehensive unit tests for new functionality
Run linting and tests before committing changes
Prefer bun over npm/bunx for Node.js package management when applicable

Version Information

To determine the next WooCommerce version number for

@since

annotations:

Read the
```
$version
```
property in
```
includes/class-woocommerce.php
```
on the trunk branch
Remove the
```
-dev
```
suffix if present
Example: If trunk shows
```
10.4.0-dev
```
, use
```
@since 10.4.0
```
Note: When reviewing PRs against trunk, the version in trunk is correct even if it seems "future" relative to released versions