/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.
One skill from claude-skills.
shell
$ npx -y skills add secondsky/claude-skills --skill woocommerce-backend-dev --agent claude-codeInstalls just this skill. Get the whole plugin for auto-invocation.
How it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/woocommerce-backend-dev
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
Stats
Stars194
Forks29
LanguageTypeScript
LicenseMIT
Ships with claude-skills
SKILL.md
woocommerce-backend-dev.SKILL.md
--- 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. license: MIT --- # 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
