wp-plugin-dev

Scaffold WordPress plugins with modular classes and compliance artifacts.

65|17|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/wpacademy/wordpress-dev-skills --skill wp-plugin-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wp-plugin-dev
Source: https://github.com/wpacademy/wordpress-dev-skills/tree/main/wp-plugin-dev
Command: npx skills add https://github.com/wpacademy/wordpress-dev-skills --skill wp-plugin-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Create production-ready WordPress plugins that adhere to official WordPress coding standards, the WordPress.org directory guidelines, and security best practices.

Core Features & Use Cases

  • Modular architecture: Scaffold plugin code with a bootstrap file and dedicated feature classes (admin, public, includes, blocks, API).
  • Compliance artifacts: Generates readme.txt, uninstall.php, license headers, and internationalization scaffolding suitable for WordPress.org submission.
  • Security and quality: Enforces input validation, escaping, nonce checks, and WordPress coding standards in generated code.
  • Use Case: Build a settings page plugin with a CPT and a Gutenberg block, ready for deployment.

Quick Start

Scaffold a new WordPress plugin by providing requirements to the skill and let it generate a modular plugin skeleton.

Frequently Asked Questions about wp-plugin-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a WordPress plugin that meets WordPress.org directory guidelines?

Scaffolding a WordPress plugin that meets WordPress.org guidelines involves generating a minimal bootstrap file, modular feature classes, readme.txt, and uninstall.php. This approach ensures compliance artifacts and internationalization readiness are built in from the start.

What's the best way to structure a modular WordPress plugin architecture for production?

A modular WordPress plugin architecture separates concerns using dedicated feature classes for admin, public, includes, blocks, and API. This structure maintains a minimal bootstrap file while enforcing WordPress coding standards and security practices across all components.

Does this WordPress plugin scaffolding approach support Gutenberg blocks and WooCommerce extensions?

Yes, the scaffolding supports Gutenberg blocks, REST endpoints, and WooCommerce extensions. It applies to plugins of all sizes, generating modular feature classes and necessary compliance artifacts for these specific WordPress components.

How do I ensure WordPress security best practices like nonce checks and escaping are included in generated plugin code?

Ensuring WordPress security best practices requires enforcing input validation, output escaping, and nonce checks directly within the generated code. The scaffolding automatically applies these security measures alongside official WordPress coding standards.

Can I generate a WordPress settings page plugin with a custom post type and a Gutenberg block together?

Yes, you can generate a settings page plugin with a custom post type and a Gutenberg block simultaneously. The scaffolding produces a modular plugin skeleton integrating admin pages, CPTs, and blocks ready for deployment.

What compliance artifacts do I need to submit a plugin to the WordPress.org repository?

Submitting a plugin to the WordPress.org repository requires compliance artifacts including readme.txt, uninstall.php, and proper license headers. The scaffolding generates these alongside internationalization structures suitable for directory submission.