woocommerce-backend-dev
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.
When & Why to Use This Skill
This Claude skill streamlines WooCommerce backend development by providing expert guidance on creating and modifying PHP code. It ensures all contributions adhere to WordPress Coding Standards, PSR-4 namespacing, and WooCommerce-specific conventions for hooks, dependency injection, and data integrity, significantly reducing technical debt in e-commerce projects.
Use Cases
- Developing new WooCommerce features by generating classes and methods that follow strict internal project structures and naming conventions.
- Refactoring existing backend code to implement dependency injection and improve modularity within the WooCommerce ecosystem.
- Implementing custom hooks and filters with standardized documentation to ensure seamless integration with the WooCommerce core.
- Writing comprehensive unit tests for backend logic to maintain data integrity and prevent regressions in complex e-commerce workflows.
- Ensuring accurate versioning for new features by automatically determining the correct @since annotations based on the current trunk branch.
| name | woocommerce-backend-dev |
|---|---|
| description | 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. |
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\WooCommercenamespace - 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
$versionproperty inincludes/class-woocommerce.phpon the trunk branch - Remove the
-devsuffix 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