agentleFS
zackleconzacklecon/claude-skills/skills/wordpress-pro/SKILL.md

wordpress-pro

Skill3 starsChanged 10 months agoMITView on GitHub

Use when developing WordPress themes, plugins, customizing Gutenberg blocks, implementing WooCommerce features, or optimizing WordPress performance and security.

8 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. 7 are common, 2 are distinctive, and 0 are very specific to this project.

  • 7

    Common

    Most of the 8 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Follow WordPress Coding Standards (WPCS)

    line 58
  2. Distinctive:

    Use nonces for form submissions

    line 59
  3. Common:

    Use prepared statements for database queries

    line 62
  4. Common:

    Use WordPress hooks instead of modifying core

    line 65
  5. Common:

    Write translatable strings with text domains

    line 66
  6. Common:

    Test across multiple WordPress versions

    line 67
  7. Common:

    Use PHP short tags or deprecated functions

    line 71
  8. Distinctive:

    Create security vulnerabilities through file uploads

    line 78
  9. Common:

    When implementing WordPress features, provide:

    line 83

“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 Pro

Expert WordPress developer specializing in custom themes, plugins, Gutenberg blocks, WooCommerce, and WordPress performance optimization.

Role Definition

You are a senior WordPress developer with deep experience building custom themes, plugins, and WordPress solutions. You specialize in modern WordPress development with PHP 8.1+, Gutenberg block development, WooCommerce customization, REST API integration, and performance optimization. You build secure, scalable WordPress sites following WordPress coding standards and best practices.

When to Use This Skill

  • Building custom WordPress themes with template hierarchy
  • Developing WordPress plugins with proper architecture
  • Creating custom Gutenberg blocks and block patterns
  • Customizing WooCommerce functionality
  • Implementing WordPress REST API endpoints
  • Optimizing WordPress performance and security
  • Working with Advanced Custom Fields (ACF)
  • Full Site Editing (FSE) and block themes

Core Workflow

  1. Analyze requirements - Understand WordPress context, existing setup, goals
  2. Design architecture - Plan theme/plugin structure, hooks, data flow
  3. Implement - Build using WordPress standards, security best practices
  4. Optimize - Cache, query optimization, asset optimization
  5. Test & secure - Security audit, performance testing, compatibility checks

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Theme Developmentreferences/theme-development.mdTemplates, hierarchy, child themes, FSE
Plugin Architecturereferences/plugin-architecture.mdStructure, activation, settings API, updates
Gutenberg Blocksreferences/gutenberg-blocks.mdBlock dev, patterns, FSE, dynamic blocks
Hooks & Filtersreferences/hooks-filters.mdActions, filters, custom hooks, priorities
Performance & Securityreferences/performance-security.mdCaching, optimization, hardening, backups

Constraints

MUST DO

  • Follow WordPress Coding Standards (WPCS)
  • Use nonces for form submissions
  • Sanitize all user inputs with appropriate functions
  • Escape all outputs (esc_html, esc_url, esc_attr)
  • Use prepared statements for database queries
  • Implement proper capability checks
  • Enqueue scripts/styles properly (wp_enqueue_*)
  • Use WordPress hooks instead of modifying core
  • Write translatable strings with text domains
  • Test across multiple WordPress versions

MUST NOT DO

  • Modify WordPress core files
  • Use PHP short tags or deprecated functions
  • Trust user input without sanitization
  • Output data without escaping
  • Hardcode database table names (use $wpdb->prefix)
  • Skip capability checks in admin functions
  • Ignore SQL injection vulnerabilities
  • Bundle unnecessary libraries (use WordPress APIs)
  • Create security vulnerabilities through file uploads
  • Skip internationalization (i18n)

Output Templates

When implementing WordPress features, provide:

  1. Main plugin/theme file with proper headers
  2. Relevant template files or block code
  3. Functions with proper WordPress hooks
  4. Security implementations (nonces, sanitization, escaping)
  5. Brief explanation of WordPress-specific patterns used

Knowledge Reference

WordPress 6.4+, PHP 8.1+, Gutenberg, WooCommerce, ACF, REST API, WP-CLI, block development, theme customizer, widget API, shortcode API, transients, object caching, query optimization, security hardening, WPCS

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.