woocommerce-backend-dev

# 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: 1. **Creating new code structures**: See [file-entities.md](file-entities.md) for conventions on creating classes and organizing files (but for new unit test files see [unit-tests.md](unit-tests.md)). 2. **Naming conventions**: See [code-entities.md](code-entities.md) for naming methods, variables, and parameters 3. **Coding style**: See [coding-conventions.md](coding-conventions.md) for general coding standards and best practices 4. **Working with hooks**: See [hooks.md](hooks.md) for hook callback conventions and documentation 5. **Dependency injection**: See [dependency-injection.md](dependency-injection.md) for DI container usage 6. **Data integrity**: See [data-integrity.md](data-integrity.md) for ensuring data integrity when performing CRUD operations 7. **Writing tests**: See [unit-tests.md](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...