Woocommerce Backend Dev

What it does

This skill provides guidance for developing WooCommerce backend PHP code, ensuring adherence to project standards and conventions. It focuses on helping developers create robust and maintainable WooCommerce extensions by outlining best practices for coding style, naming conventions, dependency injection, data integrity, and unit testing. The skill leverages SecondSky's expertise in WooCommerce development to streamline the process.

When to use it

• When creating new PHP classes or organizing files within a WooCommerce project.
• To ensure code adheres to WordPress Coding Standards and PSR-4 autoloading conventions.
• When implementing custom hooks within WooCommerce.
• For guidance on writing unit tests for new WooCommerce functionality.
• When determining the appropriate @since version annotation for new code.

Key capabilities

• Guidance on creating new code structures (classes, file organization).
• Enforcement of naming conventions for methods, variables, and parameters.
• Adherence to general coding standards and best practices.
• Documentation on hook callback conventions.
• Instructions on dependency injection container usage.
• Best practices for ensuring data integrity during CRUD operations.
• Guidance on unit testing conventions.
• Determining the next WooCommerce version number for @since annotations by inspecting includes/class-woocommerce.php.

Example prompts

• "How should I structure a new class in my WooCommerce plugin?"
• "What are the naming conventions for variables within a WooCommerce backend function?"
• "Show me an example of a hook callback implementation according to project standards."

Tips & gotchas

• Always refer to the linked documentation (file-entities.md, code-entities.md, etc.) for detailed guidance on specific aspects of development.
• The version information is based on the trunk branch, which may be ahead of released versions.
• Prefer using bun over npm/bunx when applicable for Node.js package management.