Woocommerce Backend Dev

This one's for when you're writing or modifying WooCommerce backend PHP code and need to follow the project's actual conventions. It covers the essentials: where to put new classes (src/Internal/ by default), how to name things, hook callback patterns, dependency injection usage, and unit testing requirements. The instructions link out to detailed docs on file organization, coding standards, and data integrity practices. One nice touch is the clear guidance on version numbers for @since annotations, which saves you from guessing. It assumes you're working in a WooCommerce core or plugin codebase where these conventions matter, not just throwing together a quick integration.

skills.sh installs: 379
GitHub stars: 248
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add secondsky/claude-skills --skill woocommerce-backend-dev --agent claude-code

Installs into .claude/skills of the current project.

Files

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