agentsclimarketplace

Woocommerce backend dev

Skill secondsky/claude-skills/plugins/woocommerce-backend-dev/skills/woocommerce-backend-dev

Production-ready skills for Claude Code CLI - Cloudflare, React, Tailwind v4, and AI integrations

Install
npx -y skills add secondsky/claude-skills --skill woocommerce-backend-dev

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

What its author says it does

Copied from the file, not written here

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.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

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:

  1. 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).
  2. Naming conventions: See code-entities.md for naming methods, variables, and parameters
  3. Coding style: See coding-conventions.md for general coding standards and best practices
  4. Working with hooks: See hooks.md for hook callback conventions and documentation
  5. Dependency injection: See dependency-injection.md for DI container usage
  6. Data integrity: See data-integrity.md for ensuring data integrity when performing CRUD operations
  7. 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

Gives 0 of the 12 instructions most data backend skills give in 421 tokens

Counted across 229 of the 229 authors here whose files we hold, read 2026-08-07

  • separate business logic into service layersin 22 of 229, across 15 files
  • retry failures with exponential backoffin 21 of 229, across 14 files
  • select only needed database columnsin 20 of 229, across 13 files
  • abstract data access into repository classesin 19 of 229, across 12 files
  • use centralized error handlersin 17 of 229, across 10 files
  • Use AsNoTracking for read-only queriesin 16 of 229, across 4 files
  • Use async/await for all I/O operationsin 16 of 229, across 5 files
  • implement structured loggingin 15 of 229, across 4 files
  • Use dependency injection for all servicesin 14 of 229, across 2 files
  • use resource-based URLs for REST APIsin 13 of 229, across 7 files
  • invalidate cache after data changesin 13 of 229, across 9 files
  • Use a dependency injection containerin 12 of 229, across 4 files

Said here and by no other author read

  • follow WordPress Coding Standards
  • use class methods instead of standalone functions
  • place new internal classes in src/Internal/
  • use PSR-4 autoloading with Automattic namespace
  • write comprehensive unit tests for new functionality
  • run linting and tests before committing changes

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.