wp-plugin-hooks

What problem does it solve?

Managing a plugin's public extension surface with custom actions and filters can become inconsistent and brittle. This skill outlines conventions to design stable hook APIs, enforce safe deprecation, and ensure downstream developers have a clear contract.

Core Features & Use Cases

• Prefix all custom hooks with the plugin slug to avoid collisions and improve discoverability.
• Document every hook with docblocks, including @since tags and parameter descriptions to enable IDEs and tools to surface useful information.
• Provide a safe deprecation path using apply_filters_deprecated and do_action_deprecated, maintaining backward compatibility during migrations.
• Use when designing a new API surface, reviewing PRs that add or modify hooks, or migrating legacy hooks to a managed surface.

Quick Start

Define a plugin's public hooks with a consistent prefix and document them thoroughly in SKILL.md.