Skip to main content

wordpress-pro

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

Jump to install

Source facts

Repository
mediar-ai/skillhubz
Last source activity
March 1, 2026 at 22:57
Detected SKILL.md language
English
Stars
7
Forks
4

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
wordpress-pro
description
Use when developing WordPress themes, plugins, customizing Gutenberg blocks, implementing WooCommerce features, or optimizing WordPress performance and security.
license
MIT
metadata
{"author":"https://github.com/Jeffallan","version":"1.0.0","domain":"platform","triggers":"WordPress, WooCommerce, Gutenberg, WordPress theme, WordPress plugin, custom blocks, ACF, WordPress REST API, hooks, filters, WordPress performance, WordPress security","role":"expert","scope":"implementation","output-format":"code","related-skills":"php-pro, laravel-specialist, fullstack-guardian, security-reviewer"}
# 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: | 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 | ## 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
View on GitHub