wp-builder-prolisted

This skill should be used when the user asks to "build a WordPress theme", "add a feature to an existing plugin", "add a settings page to a plugin", "extend an existing WordPress plugin", "create or register a single Gutenberg block or pattern", "extend WooCommerce", "add a WordPress REST API endpoint", "work with ACF fields", "add a nonce to an admin form", "harden a WordPress plugin", "speed up a slow WordPress site", or invokes /wp-builder-pro. Also triggers on symptom-driven requests - "my WordPress site is slow", "a plugin throws a fatal error", "a block won't render", "fix my WordPress site". Operates as an expert WordPress developer building custom themes, plugins, Gutenberg blocks, WooCommerce extensions, and REST endpoints, applying security hardening (nonces, sanitization, escaping, capability checks, prepared statements) and performance tuning (transients, object cache, query optimization, conditional asset enqueueing) to WordPress Coding Standards. Routes each request to the matching reference (th
chrismccoy/skills · ★ 2 · Web & Frontend · score 66

Install: claude install-skill chrismccoy/skills

# WP Builder Pro Operate as an expert WordPress developer specializing in custom themes, plugins, Gutenberg blocks, WooCommerce, and WordPress performance optimization. Build and implement WordPress code to WordPress Coding Standards (WPCS) with security and performance baked in. ## When to Use Use this skill when the task is to **build or implement** WordPress code: - Building or modifying a custom theme (templates, hierarchy, child theme, FSE) - Writing or extending a plugin (activation, settings, hooks, updates) - Creating or registering Gutenberg blocks, block patterns, or dynamic blocks - Extending WooCommerce (products, checkout, hooks, custom flows) - Adding REST API endpoints or working with ACF fields - Hardening security (nonces, sanitization, escaping, capability checks) - Diagnosing and fixing performance (caching, slow queries, asset loading) - Symptom-driven requests: "my site is slow", "plugin throws a fatal error", "block won't render", "fix my WordPress site" Do **not** use to audit/review existing code (→ wordpress-architect-review, wordpress-consultant). Do **not** use to scaffold a complete plugin from scratch as a full WordPress.org-ready directory tree (modular OOP classes, `uninstall.php`, `readme.txt`, `.pot`) - that is the `wordpress-plugin` skill's one-shot job. Use wp-builder-pro for targeted/iterative plugin work (add a feature, settings page, endpoint, hook, fix) and for all non-plugin building (themes, blocks, WooCommerce, performance, se