Skip to content
cccskills
FreePublished on GitHub

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

100+ animated React components (Aceternity UI) for Next.js with Tailwind. Use for hero sections, parallax, 3D effects, or encountering animation, shadcn CLI integration errors.

The English summary is being prepared. Showing the original description.

secondsky/claude-skills231Updated Sep 28, 2026

Secure API authentication with JWT, OAuth 2.0, API keys. Use for authentication systems, third-party integrations, service-to-service communication, or encountering token management, security headers, auth flow errors.

The English summary is being prepared. Showing the original description.

secondsky/claude-skills231Updated Sep 28, 2026

Creates comprehensive API changelogs documenting breaking changes, deprecations, and migration strategies for API consumers. Use when managing API versions, communicating breaking changes, or creating upgrade guides.

The English summary is being prepared. Showing the original description.

secondsky/claude-skills231Updated Sep 28, 2026

Verifies API contracts between services using consumer-driven contracts, schema validation, and tools like Pact. Use when testing microservices communication, preventing breaking changes, or validating OpenAPI specifications.

The English summary is being prepared. Showing the original description.

secondsky/claude-skills231Updated Sep 28, 2026

Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.

The English summary is being prepared. Showing the original description.

secondsky/claude-skills231Updated Sep 28, 2026

Implements standardized API error responses with proper status codes, logging, and user-friendly messages. Use when building production APIs, implementing error recovery patterns, or integrating error monitoring services.

The English summary is being prepared. Showing the original description.

secondsky/claude-skills231Updated Sep 28, 2026

See all skills by secondsky

Report a problem with this skill