What problem does it solve?
This Skill solves the problem of WordPress hooks firing at the wrong time, with the wrong priority, or producing incorrect results because actions/filters and lifecycle placement are misunderstood in Sage/Acorn projects.
Core Features & Use Cases
- Choose the correct hook type and callback contract: distinguishes actions (side effects, no return required) from filters (data transformation, must return the filtered value) and maps them to
add_action vs add_filter.
- Place hooks in the right Sage/Acorn location: guides registrations primarily into
boot() methods in ServiceProviders (and clarifies why register() is for container bindings only), plus lifecycle timing choices like after_setup_theme, init, wp_loaded, wp_enqueue_scripts, and content filters like the_content.
- Prevent common production failures: covers priority/
accepted_args mismatches, removal issues, autosave/revision duplication for save_post, and Tailwind v4 filter conflicts (e.g., disabling wptexturize via run_wptexturize).
Quick Start
Ask your AI assistant to help you register your the_content filter and an init action in the correct Acorn ServiceProvider boot() method with the right priority and accepted argument count, then troubleshoot why the hook order is not matching expectations.
