Develops custom WordPress themes and plugins, creates and registers Gutenberg blocks and block patterns, configures WooCommerce stores, implements WordPress REST API endpoints, applies security hardening (nonces, sanitization, escaping, capability checks), and optimizes performance through caching and query tuning. Use when building WordPress themes, writing plugins, customizing Gutenberg blocks, extending WooCommerce, working with ACF, using the WordPress REST API, applying hooks and filters, or improving WordPress performance and security.
SKILL.md
WordPress Pro
Expert WordPress developer specializing in custom themes, plugins, Gutenberg blocks, WooCommerce, and WordPress performance optimization.
Core Workflow
Analyze requirements — Understand WordPress context, existing setup, and goals.
Design architecture — Plan theme/plugin structure, hooks, and data flow.
Implement — Build using WordPress coding standards and security best practices.
Validate — Run phpcs --standard=WordPress to catch WPCS violations; verify nonce handling and capability checks manually.
Optimize — Apply transient/object caching, query optimization, and asset enqueuing.
Test & secure — Confirm sanitization/escaping on all I/O, test across target WordPress versions, and run a security audit checklist.
Reference Guide
Load detailed guidance based on context:
Topic
Reference
Load When
Theme Development
references/theme-development.md
Templates, hierarchy, child themes, FSE
Plugin Architecture
references/plugin-architecture.md
Structure, activation, settings API, updates
Gutenberg Blocks
references/gutenberg-blocks.md
Block dev, patterns, FSE, dynamic blocks
0
Hooks & Filters
references/hooks-filters.md
Actions, filters, custom hooks, priorities
Performance & Security
references/performance-security.md
Caching, optimization, hardening, backups
Key Implementation Patterns
Nonce Verification (form submissions)
// Output nonce field in form
wp_nonce_field( 'my_action', 'my_nonce' );
// Verify on submission — bail early if invalid
if ( ! isset( $_POST['my_nonce'] ) || ! wp_verify_nonce( sanitize_text_field( wp_unslash( $_POST['my_nonce'] ) ), 'my_action' ) ) {
wp_die( esc_html__( 'Security check failed.', 'my-textdomain' ) );
}
global $wpdb;
$results = $wpdb->get_results(
$wpdb->prepare(
"SELECT * FROM {$wpdb->prefix}my_table WHERE user_id = %d AND status = %s",
absint( $user_id ),
sanitize_text_field( $status )
)
);
Capability Checks
// Always check capabilities before sensitive operations
if ( ! current_user_can( 'manage_options' ) ) {
wp_die( esc_html__( 'You do not have permission to do this.', 'my-textdomain' ) );
}
Constraints
MUST DO
Follow WordPress Coding Standards (WPCS); validate with phpcs --standard=WordPress
Use nonces for all form submissions and AJAX requests
Sanitize all user inputs with appropriate functions (sanitize_text_field, wp_kses_post, etc.)
Escape all outputs (esc_html, esc_url, esc_attr, wp_kses_post)
Use prepared statements for all database queries ($wpdb->prepare)
Implement proper capability checks before privileged operations
Enqueue scripts/styles via wp_enqueue_scripts / admin_enqueue_scripts hooks
Use WordPress hooks instead of modifying core
Write translatable strings with text domains (__(), esc_html__(), etc.)
Test across target 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 vectors
Bundle unnecessary libraries when WordPress APIs suffice