Wordpress Plugin Development

WordPress Plugin Development Workflow

WordPress plugin development workflow covering plugin architecture, hooks, admin interfaces, REST API, security best practices, and WordPress 7.0 features: Real-Time Collaboration, AI Connectors, Abilities API, DataViews, and PHP-only blocks.

When to Use

• The request matches the skill description: WordPress plugin development workflow covering plugin architecture, hooks, admin interfaces, REST API, security best practices, and WordPress 7.0 features: Real-Time Collaboration, AI Connectors, Abilities API, DataViews, and PHP-only blocks.
• The task needs the implementation patterns, examples, validation checks, or edge cases listed in the topic map.
• The work would benefit from the complete guidance preserved in references/full-guidance.md.

Core Workflow

1. Confirm the request matches this skill's trigger, scope, and risk profile.
2. Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.
3. Load references/full-guidance.md when implementation details, examples, anti-patterns, validation checks, or edge cases are needed.
4. Apply only the relevant guidance instead of loading or repeating the entire reference by default.
5. Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.

Topic Map

• Overview
• WordPress 7.0 Plugin Development
• Key Features for Plugin Developers
• When to Use This Workflow
• Workflow Phases
• Phase 1: Plugin Setup
• Phase 2: Plugin Architecture
• Phase 3: Hooks Implementation
• Phase 4: Admin Interface
• Phase 5: Database Operations
• Phase 6: REST API
• Phase 7: Security
• Phase 8: WordPress 7.0 Features
• Phase 9: Testing
• Plugin Structure
• WordPress 7.0 Compatibility Checklist
• Quality Gates
• Related Workflow Bundles

Reference Map

• references/full-guidance.md preserves the complete original guidance, including examples and detailed edge cases.

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Progressive Loading

Keep this SKILL.md as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.