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 |
| 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' ) );
}
Sanitization & Escaping
// Sanitize input (store)
$title = sanitize_text_field( wp_unslash( $_POST['title'] ?? '' ) );
$content = wp_kses_post( wp_unslash( $_POST['content'] ?? '' ) );
$url = esc_url_raw( wp_unslash( $_POST['url'] ?? '' ) );
// Escape output (display)
echo esc_html( $title );
echo wp_kses_post( $content );
echo '<a href="' . esc_url( $url ) . '">' . esc_html__( 'Link', 'my-textdomain' ) . '</a>';
Enqueuing Scripts & Styles
add_action( 'wp_enqueue_scripts', 'my_theme_assets' );
function my_theme_assets(): void {
wp_enqueue_style(
'my-theme-style',
get_stylesheet_uri(),
[],
wp_get_theme()->get( 'Version' )
);
wp_enqueue_script(
'my-theme-script',
get_template_directory_uri() . '/assets/js/main.js',
[ 'jquery' ],
'1.0.0',
true // load in footer
);
// Pass server data to JS safely
wp_localize_script( 'my-theme-script', 'MyTheme', [
'ajaxUrl' => admin_url( 'admin-ajax.php' ),
'nonce' => wp_create_nonce( 'my_ajax_nonce' ),
] );
}
Prepared Database Queries
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
- Allow unsafe file upload handling
- Skip internationalization (i18n)
Output Templates
When implementing WordPress features, provide:
- Main plugin/theme file with proper headers
- Relevant template files or block code
- Functions with proper WordPress hooks
- Security implementations (nonces, sanitization, escaping)
- 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
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: wordpress-pro3description: 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. Use when this capability is needed.4---56# WordPress Pro78Expert WordPress developer specializing in custom themes, plugins, Gutenberg blocks, WooCommerce, and WordPress performance optimization.910## Core Workflow11121. **Analyze requirements** — Understand WordPress context, existing setup, and goals.132. **Design architecture** — Plan theme/plugin structure, hooks, and data flow.143. **Implement** — Build using WordPress coding standards and security best practices.154. **Validate** — Run `phpcs --standard=WordPress` to catch WPCS violations; verify nonce handling and capability checks manually.165. **Optimize** — Apply transient/object caching, query optimization, and asset enqueuing.176. **Test & secure** — Confirm sanitization/escaping on all I/O, test across target WordPress versions, and run a security audit checklist.1819## Reference Guide2021Load detailed guidance based on context:2223| Topic | Reference | Load When |24|-------|-----------|-----------|25| Theme Development | `references/theme-development.md` | Templates, hierarchy, child themes, FSE |26| Plugin Architecture | `references/plugin-architecture.md` | Structure, activation, settings API, updates |27| Gutenberg Blocks | `references/gutenberg-blocks.md` | Block dev, patterns, FSE, dynamic blocks |28| Hooks & Filters | `references/hooks-filters.md` | Actions, filters, custom hooks, priorities |29| Performance & Security | `references/performance-security.md` | Caching, optimization, hardening, backups |3031## Key Implementation Patterns3233### Nonce Verification (form submissions)34```php35// Output nonce field in form36wp_nonce_field( 'my_action', 'my_nonce' );3738// Verify on submission — bail early if invalid39if ( ! isset( $_POST['my_nonce'] ) || ! wp_verify_nonce( sanitize_text_field( wp_unslash( $_POST['my_nonce'] ) ), 'my_action' ) ) {40 wp_die( esc_html__( 'Security check failed.', 'my-textdomain' ) );41}42```4344### Sanitization & Escaping45```php46// Sanitize input (store)47$title = sanitize_text_field( wp_unslash( $_POST['title'] ?? '' ) );48$content = wp_kses_post( wp_unslash( $_POST['content'] ?? '' ) );49$url = esc_url_raw( wp_unslash( $_POST['url'] ?? '' ) );5051// Escape output (display)52echo esc_html( $title );53echo wp_kses_post( $content );54echo '<a href="' . esc_url( $url ) . '">' . esc_html__( 'Link', 'my-textdomain' ) . '</a>';55```5657### Enqueuing Scripts & Styles58```php59add_action( 'wp_enqueue_scripts', 'my_theme_assets' );60function my_theme_assets(): void {61 wp_enqueue_style(62 'my-theme-style',63 get_stylesheet_uri(),64 [],65 wp_get_theme()->get( 'Version' )66 );67 wp_enqueue_script(68 'my-theme-script',69 get_template_directory_uri() . '/assets/js/main.js',70 [ 'jquery' ],71 '1.0.0',72 true // load in footer73 );74 // Pass server data to JS safely75 wp_localize_script( 'my-theme-script', 'MyTheme', [76 'ajaxUrl' => admin_url( 'admin-ajax.php' ),77 'nonce' => wp_create_nonce( 'my_ajax_nonce' ),78 ] );79}80```8182### Prepared Database Queries83```php84global $wpdb;85$results = $wpdb->get_results(86 $wpdb->prepare(87 "SELECT * FROM {$wpdb->prefix}my_table WHERE user_id = %d AND status = %s",88 absint( $user_id ),89 sanitize_text_field( $status )90 )91);92```9394### Capability Checks95```php96// Always check capabilities before sensitive operations97if ( ! current_user_can( 'manage_options' ) ) {98 wp_die( esc_html__( 'You do not have permission to do this.', 'my-textdomain' ) );99}100```101102## Constraints103104### MUST DO105- Follow WordPress Coding Standards (WPCS); validate with `phpcs --standard=WordPress`106- Use nonces for all form submissions and AJAX requests107- Sanitize all user inputs with appropriate functions (`sanitize_text_field`, `wp_kses_post`, etc.)108- Escape all outputs (`esc_html`, `esc_url`, `esc_attr`, `wp_kses_post`)109- Use prepared statements for all database queries (`$wpdb->prepare`)110- Implement proper capability checks before privileged operations111- Enqueue scripts/styles via `wp_enqueue_scripts` / `admin_enqueue_scripts` hooks112- Use WordPress hooks instead of modifying core113- Write translatable strings with text domains (`__()`, `esc_html__()`, etc.)114- Test across target WordPress versions115116### MUST NOT DO117- Modify WordPress core files118- Use PHP short tags or deprecated functions119- Trust user input without sanitization120- Output data without escaping121- Hardcode database table names (use `$wpdb->prefix`)122- Skip capability checks in admin functions123- Ignore SQL injection vectors124- Bundle unnecessary libraries when WordPress APIs suffice125- Allow unsafe file upload handling126- Skip internationalization (i18n)127128## Output Templates129130When implementing WordPress features, provide:1311. Main plugin/theme file with proper headers1322. Relevant template files or block code1333. Functions with proper WordPress hooks1344. Security implementations (nonces, sanitization, escaping)1355. Brief explanation of WordPress-specific patterns used136137## Knowledge Reference138139WordPress 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, WPCS140141---142> Converted and distributed by [TomeVault](https://tomevault.io/claim/jeffallan) — claim your Tome and manage your conversions.143<!-- tomevault:4.0:skill_md:2026-04-11 -->