Skip to main content
skill CX Codex

wordpress — skill for WordPress and WooCommerce

The wordpress skill gives an agent a rulebook for WordPress and WooCommerce work in PHP. It keeps code inside WordPress standards and reminds the agent about hooks, nonces and prepared queries.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Mindrally/skills --skill wordpress -a claude-code
Open on GitHub

What wordpress does

Once installed, the skill acts as a set of rules: the agent writes code to WordPress standards, leaves core files alone and extends behaviour through hooks.

What is inside. A PHP and WordPress standards section: PHP 7.4+ typed properties and arrow functions, declare(strict_types=1);, prepare() for database queries, nonce verification on form submissions, dbDelta() for schema changes. A separate security block covers escaping, sanitization, capability checks and safe enqueueing of scripts and styles.

Practices: transients for caching, wp_cron() for background work, wp_enqueue_script() and wp_enqueue_style() for assets, custom post types and taxonomies, child themes so updates do not wipe customizations, i18n through WordPress localization functions.

WooCommerce gets its own section: wc_get_product() instead of get_post(), the Settings API for configuration pages, template overrides in the your-plugin/woocommerce/ directory, CRUD classes and data stores, WC()->session->set() for temporary data, wc_add_notice() for user-facing messages, plus activation and version checks.

Testing runs on WP_UnitTestCase, with hooks and filters covered. For errors the skill points to WordPress debug logging.

Who it is for. Anyone maintaining a plugin or theme who wants the agent to follow the ecosystem's conventions instead of inventing its own. On a plain PHP project with no WordPress, the rules just add noise.

What it helps with

  • The agent edits WordPress core files instead of using hooks — the skill forbids that.
  • Database queries are built by string concatenation, without prepare().
  • Forms are handled without nonce or capability checks.
  • WooCommerce products are fetched with get_post() instead of wc_get_product().
  • Edits in a parent theme are lost on update.

Example prompts for the agent

  • Write a plugin: a settings page through the Settings API and product output via wc_get_product().
  • Add a custom post type and taxonomy, register them on a hook, leave core untouched.
  • Review this form handler: it needs nonces, field sanitization and capability checks.

How to install wordpress

1Skills CLI (Vercel)

npx skills add Mindrally/skills --skill wordpress -a claude-code

2Manually: put the files in place

~/.claude/skills/wordpress/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/wordpress/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about wordpress

How to install wordpress in Claude?

Through the skills marketplace: run npx skills add Mindrally/skills --skill wordpress -a claude-code, then the same command again. The skill file lands at ~/.claude/skills/wordpress/SKILL.md.

What does the wordpress skill do?

It sets rules for WordPress and WooCommerce development in PHP: coding standards, hooks, query and form security, WooCommerce practices and tests on WP_UnitTestCase.

Why use the wordpress skill if the agent already knows PHP?

It pins down WordPress conventions: do not touch core, extend through hooks, use prepare() and nonces. Without it, an agent tends to propose its own patterns instead of the ecosystem's.

How to install wordpress in Codex?

Run npx skills add Mindrally/skills --skill wordpress -a codex. The skill appears at .agents/skills/wordpress/SKILL.md.

Source text

SKILL.md · Apache-2.0
---
name: wordpress
description: Expert in WordPress and WooCommerce development with PHP best practices
metadata:
  maintainer: Mindrally
  source: https://github.com/Mindrally/skills
---

# WordPress

You are an expert in WordPress and WooCommerce development with deep knowledge of PHP and WordPress ecosystem.

## Core Principles

- Write concise, technical responses with accurate PHP examples
- Follow WordPress coding standards and object-oriented programming practices
- Use lowercase with hyphens for directories (e.g., wp-content/themes/my-theme)
- Favor hooks (actions and filters) for extending functionality
- Never modify core WordPress files

## PHP/WordPress Standards

- Implement PHP 7.4+ features (typed properties, arrow functions)
- Enable strict typing with `declare(strict_types=1);`
- Use `prepare()` statements for secure database queries
- Implement proper nonce verification for form submissions
- Use `dbDelta()` function for database schema changes

## Security

- Apply proper security measures (nonces, escaping, sanitization)
- Use prepared statements to prevent SQL injection
- Validate and sanitize all user inputs
- Implement proper capability checks
- Use secure enqueue methods for scripts and styles

## Best Practices

- Leverage WordPress hooks instead of modifying core files
- Use transients API for caching
- Implement background processing via `wp_cron()`
- Use `wp_enqueue_script()` and `wp_enqueue_style()` for assets
- Implement custom post types and taxonomies appropriately
- Use child themes for customizations to preserve update compatibility
- Support internationalization (i18n) with WordPress localization functions

## WooCommerce

- Use `wc_get_product()` instead of `get_post()` for retrieving products
- Implement WooCommerce Settings API for configuration pages
- Override templates in `your-plugin/woocommerce/` directory
- Use CRUD classes and data stores for custom data management
- Apply `WC()->session->set()` for temporary data storage
- Use `wc_add_notice()` for user-facing messages
- Check WooCommerce activation and version compatibility

## Testing

- Write unit tests using WP_UnitTestCase framework
- Test hooks and filters thoroughly
- Use WordPress debug logging for error handling

© Mindrally · Apache-2.0 · Mindrally/skills

Similar skills

Everything for Backend and APIs →

From the same set168

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor