Guardrail·E-commerce

WooCommerce Backend Dev

Add or modify WooCommerce backend PHP code following project conventions. Use when creating new classes, methods, hooks, or modifying…

You say
Install this skill Read the source first Free Written by woocommerce · unverified publisher
Context cost
10.8k tokensestimated from the bundle, loaded when it triggers
Bundle
9 files · 43.0 kBtext throughout, nothing executable
Licence
GPL-2.0-or-laterfree to use
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

Add or modify WooCommerce backend PHP code following project conventions. Use when creating new classes, methods, hooks, or modifying existing backend code. **MUST be invoked before writing any PHP unit tests.**

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Guardrail

Constrains what the agent is allowed to do.

woocommercephpwordpressconventions
Filed under

E-commerce

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md2.5 kB · 49 lines
--- 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. **MUST be invoked before writing any PHP unit tests.** ---
6# WooCommerce Backend Development
7
8This skill provides guidance for developing WooCommerce backend PHP code according to project standards and conventions.
9
10## When to Use This Skill
11
12**ALWAYS invoke this skill before:**
13
14- Writing new PHP unit tests (*Test.php files)
15- Creating new PHP classes
16- Modifying existing backend PHP code
17- Adding hooks or filters
18
19## Instructions
20
21Follow WooCommerce project conventions when adding or modifying backend PHP code:
22
231. **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)).
242. **Naming conventions**: See [code-entities.md](code-entities.md) for naming methods, variables, and parameters
253. **Coding style**: See [coding-conventions.md](coding-conventions.md) for general coding standards and best practices
264. **Type annotations**: See [type-annotations.md](type-annotations.md) for PHPStan-aware PHPDoc annotations
275. **Working with hooks**: See [hooks.md](hooks.md) for hook callback conventions and documentation
286. **Dependency injection**: See [dependency-injection.md](dependency-injection.md) for DI container usage
297. **Data integrity**: See [data-integrity.md](data-integrity.md) for ensuring data integrity when performing CRUD operations
308. **Writing tests**: See [unit-tests.md](unit-tests.md) for unit testing conventions
31
32## Key Principles
33
34- Always follow WordPress Coding Standards
35- Use class methods instead of standalone functions
36- Place new internal classes in src/Internal/ by default
37- Use PSR-4 autoloading with Automattic\WooCommerce namespace
38- Write comprehensive unit tests for new functionality
39- Run linting and tests before committing changes
40
41## Version Information
42
43To determine the next WooCommerce version number for @since annotations:
44
45- Read the $version property in includes/class-woocommerce.php **on the trunk branch**
46- Remove the -dev suffix if present
47- Example: If trunk shows 10.4.0-dev, use @since 10.4.0
48- Note: When reviewing PRs against trunk, the version in trunk is correct even if it seems "future" relative to released versions
49
In the file
SKILL.md313 words
Files9
LicenceGPL-2.0-or-later
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈70
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
10,680
on trigger
The instruction body and 8 supporting files, read only when the skill fires.
5.4%
of a 200k window
Ten skills this size would take about 54% of the window before you open a file.
050k100k150k200k context window

10.8k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

9 files, 43.0 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md2.5 kB
  • code-entities.md4.6 kB
  • coding-conventions.md5.1 kB
  • data-integrity.md4.4 kB
  • dependency-injection.md3.0 kB
  • file-entities.md2.0 kB
  • hooks.md2.0 kB
  • type-annotations.md8.6 kB
  • unit-tests.md10.8 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 9 files you can review in full before installing. The GPL-2.0-or-later licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# WooCommerce Backend Dev · 10.8k tokens when loaded npx mcprush@latest skill add woocommerce/woocommerce-backend-dev

Writes to .claude/skills/woocommerce-backend-dev/ in the current project. Add --global to put it in your home directory instead, for every project.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referencewoocommerce/woocommerce-backend-dev

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Who wrote it

WO
woocommerce

Publishes on mcprush.

0 servers listed3 skills listednot claimed
Profile
Publisher
Servers0
Claim this skill