How do I install the Woocommerce Backend Dev skill?

Run npx skillmds@latest add tomevault-io/woocommerce-backend-dev in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Woocommerce Backend Dev safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Woocommerce Backend Dev?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Woocommerce Backend Dev free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Woocommerce Backend Dev?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Woocommerce Backend Dev by tomevault-io

Name: Woocommerce Backend Dev
Author: tomevault-io

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. Use when this capability is needed.

tomevault-io a3a0bb1 2 files · 3.0 KB Updated Sep 17, 2026

File contents

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\WooCommerce namespace
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 $version property in includes/class-woocommerce.php on the trunk branch
Remove the -dev suffix 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

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: woocommerce-backend-devdescription: 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. Use when this capability is needed.---# WooCommerce Backend DevelopmentThis skill provides guidance for developing WooCommerce backend PHP code according to project standards and conventions.## InstructionsFollow 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 parameters3. **Coding style**: See [coding-conventions.md](coding-conventions.md) for general coding standards and best practices4. **Working with hooks**: See [hooks.md](hooks.md) for hook callback conventions and documentation5. **Dependency injection**: See [dependency-injection.md](dependency-injection.md) for DI container usage6. **Data integrity**: See [data-integrity.md](data-integrity.md) for ensuring data integrity when performing CRUD operations7. **Writing tests**: See [unit-tests.md](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\WooCommerce` namespace- 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 InformationTo determine the next WooCommerce version number for `@since` annotations:- Read the `$version` property in `includes/class-woocommerce.php` **on the trunk branch**- Remove the `-dev` suffix 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---> Converted and distributed by [TomeVault](https://tomevault.io/claim/secondsky) — claim your Tome and manage your conversions.

Frequently asked questions