
Wordpress Plugin Development
Scaffold and extend WordPress plugins with hooks, admin UI, REST endpoints, and security patterns aligned to modern WordPress releases.
Overview
wordpress-plugin-development is an agent skill for the Build phase that guides WordPress plugin architecture, hooks, admin and REST interfaces, security, and WordPress 7.0 feature integration.
Install
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill wordpress-plugin-developmentWhat is this skill?
- End-to-end plugin workflow: architecture, hooks, admin UI, REST API, and security practices
- WordPress 7.0 focus: Real-Time Collaboration, AI Connectors, Abilities API, DataViews, PHP-only blocks
- RTC guidance: register post meta with show_in_rest => true and custom sync.providers transport
- AI integration via wp_ai_client_prompt() and Settings > Connectors for multiple providers
- Abilities API manifest at /wp-json/abilities/v1/manifest with MCP adapter considerations
- 5 WordPress 7.0 plugin development focus areas listed in the workflow overview
- Abilities REST manifest path /wp-json/abilities/v1/manifest
Adoption & trust: 1 installs on skills.sh; 40.1k GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You need a WordPress plugin but lack a consistent checklist for hooks, REST, admin UX, and newer platform APIs.
Who is it for?
Solo developers building custom WP plugins, agent connectors, or admin tools on self-hosted or managed WordPress.
Skip if: Static-site-only projects, non-PHP stacks, or teams that only need Gutenberg theme tweaks without plugin boundaries.
When should I use this skill?
When creating or extending a WordPress plugin with proper architecture, hooks, admin interfaces, REST API, and security aligned to WordPress 7.0 features.
What do I get? / Deliverables
You leave with plugin structure, integration points, and 7.0-ready patterns (RTC meta, AI connectors, Abilities manifest) to implement and test in your codebase.
- Plugin file structure and hook map
- REST routes and admin settings plan
- Security and meta-registration checklist for RTC and Abilities
Recommended Skills
Journey fit
Build is the primary phase because the skill guides implementing plugin code, admin surfaces, and APIs inside a WordPress site. Backend subphase matches server-side PHP, hooks, REST routes, and meta registration rather than theme-only frontend polish.
How it compares
Skill-shaped WordPress implementation playbook—not a one-click MCP server or generic PHP linter.
Common Questions / FAQ
Who is wordpress-plugin-development for?
It is for indie builders and small teams using agents to create or extend WordPress plugins with REST, admin UI, and current WordPress platform features.
When should I use wordpress-plugin-development?
Use it during Build while designing plugin files, registering hooks and REST routes, or adopting WordPress 7.0 Abilities, AI Connectors, and DataViews patterns.
Is wordpress-plugin-development safe to install?
Treat it as guidance that may suggest network and API usage; review the Security Audits panel on this page and audit generated plugin code before production deploy.
SKILL.md
READMESKILL.md - Wordpress Plugin Development
# WordPress Plugin Development Workflow ## Overview Specialized workflow for creating WordPress plugins with proper architecture, hooks system, admin interfaces, REST API endpoints, and security practices. Now includes WordPress 7.0 features for modern plugin development. ## WordPress 7.0 Plugin Development ### Key Features for Plugin Developers 1. **Real-Time Collaboration (RTC) Compatibility** - Yjs-based CRDT for simultaneous editing - Custom transport via `sync.providers` filter - **Requirement**: Register post meta with `show_in_rest => true` 2. **AI Connector Integration** - Provider-agnostic AI via `wp_ai_client_prompt()` - Settings > Connectors admin screen - Works with OpenAI, Claude, Gemini, Ollama 3. **Abilities API** - Declare plugin capabilities for AI agents - REST API: `/wp-json/abilities/v1/manifest` - MCP adapter support 4. **DataViews & DataForm** - Modern admin interfaces - Replaces WP_List_Table patterns - Built-in validation 5. **PHP-Only Blocks** - Register blocks without JavaScript - Auto-generated Inspector controls ## When to Use This Workflow Use this workflow when: - Creating custom WordPress plugins - Extending WordPress functionality - Building admin interfaces - Adding REST API endpoints - Integrating third-party services - Implementing WordPress 7.0 AI/Collaboration features ## Workflow Phases ### Phase 1: Plugin Setup #### Skills to Invoke - `app-builder` - Project scaffolding - `backend-dev-guidelines` - Backend patterns #### Actions 1. Create plugin directory structure 2. Set up main plugin file with header 3. Implement activation/deactivation hooks 4. Set up autoloading 5. Configure text domain #### WordPress 7.0 Plugin Header ```php /* Plugin Name: My Plugin Plugin URI: https://example.com/my-plugin Description: A WordPress 7.0 compatible plugin with AI and RTC support Version: 1.0.0 Requires at least: 6.0 Requires PHP: 7.4 Author: Developer Name License: GPL2+ */ ``` #### Copy-Paste Prompts ``` Use @app-builder to scaffold a new WordPress plugin ``` ### Phase 2: Plugin Architecture #### Skills to Invoke - `backend-dev-guidelines` - Architecture patterns #### Actions 1. Design plugin class structure 2. Implement singleton pattern 3. Create loader class 4. Set up dependency injection 5. Configure plugin lifecycle #### WordPress 7.0 Architecture Considerations - Prepare for iframed editor compatibility - Design for collaboration-aware data flows - Consider Abilities API for AI integration #### Copy-Paste Prompts ``` Use @backend-dev-guidelines to design plugin architecture ``` ### Phase 3: Hooks Implementation #### Skills to Invoke - `wordpress-penetration-testing` - WordPress patterns #### Actions 1. Register action hooks 2. Create filter hooks 3. Implement callback functions 4. Set up hook priorities 5. Add conditional hooks #### Copy-Paste Prompts ``` Use @wordpress-penetration-testing to understand WordPress hooks ``` ### Phase 4: Admin Interface #### Skills to Invoke - `frontend-developer` - Admin UI #### Actions 1. Create admin menu 2. Build settings pages 3. Implement options registration 4. Add settings sections/fields 5. Create admin notices #### WordPress 7.0 Admin Considerations - Test with new admin color scheme - Consider DataViews for data displays - Implement view transitions - Use new validation patterns #### DataViews Example ```javascript import { DataViews } from '@wordpress/dataviews'; const MyPluginDataView = () => { const data = [/* records */]; const fields = [ { id: 'title', label: 'Title', sortable