agentleFS
MindrallyMindrally/skills/wordpress/SKILL.md

wordpress

Skill275 starsChanged 34 days agoApache-2.0View on GitHub

Expert in WordPress and WooCommerce development with PHP best practices

11 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. 0 are common, 12 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 12

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write concise, technical responses with accurate PHP examples

    line 15
  2. Distinctive:

    Follow WordPress coding standards and object-oriented programming practices

    line 16
  3. Very specific:

    Use lowercase with hyphens for directories (e.g., wp-content/themes/my-theme)

    line 17
  4. Distinctive:

    Never modify core WordPress files

    line 19
  5. Very specific:

    Use prepare() statements for secure database queries

    line 25
  6. Very specific:

    Use dbDelta() function for database schema changes

    line 27
  7. Distinctive:

    Use prepared statements to prevent SQL injection

    line 32
  8. Distinctive:

    Use secure enqueue methods for scripts and styles

    line 35
  9. Distinctive:

    Use transients API for caching

    line 40
  10. Very specific:

    Use wp_enqueue_script() and wp_enqueue_style() for assets

    line 42
  11. Distinctive:

    Use child themes for customizations to preserve update compatibility

    line 44
  12. Very specific:

    Use wc_get_product() instead of get_post() for retrieving products

    line 49
  13. Distinctive:

    Use CRUD classes and data stores for custom data management

    line 52
  14. Very specific:

    Use wc_add_notice() for user-facing messages

    line 54
  15. Distinctive:

    Check WooCommerce activation and version compatibility

    line 55
  16. Distinctive:

    Write unit tests using WP_UnitTestCase framework

    line 59
  17. Distinctive:

    Test hooks and filters thoroughly

    line 60
  18. Distinctive:

    Use WordPress debug logging for error handling

    line 61

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.