Woocommerce backend dev

Skill VRIL-LABS/skill-jam/skills/ai-ml/claude-skills-main/claude-skills-main/plugins/woocommerce-backend-dev/skills/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.From its SKILL.md

Install

npx -y skills add VRIL-LABS/skill-jam --skill woocommerce-backend-dev

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 421 tokens by cl100k_base, as published. Nobody here has run it

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.