poocommerce-backend-dev

PooCommerce backend code uses PSR-4 autoloading with classes organized in `src/Internal/` by default, following WordPress Coding Standards. Use `snake_case` for file and method names, include PHPDoc type annotations, and apply dependency injection for external dependencies to maintain consistency and testability.

Follow WordPress Coding Standards, PSR-4 autoloading conventions, and PooCommerce naming rules. Apply dependency injection patterns, use PHPDoc annotations with `@since` tags, enforce method visibility, and validate all operations for data integrity. Unit tests must be written before committing changes.

Write unit tests before committing backend changes using the project's testing framework. Use `@testdox` annotations for test documentation, follow the established testing patterns in the codebase, and ensure tests cover data integrity, race conditions, and validation logic to maintain code quality.

Yes. Dependency injection is a core PooCommerce convention for managing class dependencies. It improves testability, reduces tight coupling, and ensures cleaner code structure. All new classes and methods should apply this pattern consistently with project standards.

Review PooCommerce naming conventions, file organization rules, and namespace structure (typically `src/Internal/` for internal utilities). Plan your class design around dependency injection, ensure PHPDoc annotations are complete, and prepare unit tests before implementing code.