What problem does it solve?
This Skill solves the challenge of extending JetEngine Dynamic Visibility with custom condition logic that works consistently across editor UI and rendering contexts.
Core Features & Use Cases
- JetEngine Dynamic Visibility extension contract: Registers a custom condition by hooking jet-engine/modules/dynamic-visibility/conditions/register and providing a class that extends \Jet_Engine\Modules\Dynamic_Visibility\Conditions\Base.
- Correct show/hide semantics: Ensures check() returns the proper boolean based on the user’s intent in $args['type'] ('show' vs 'hide') so the UI behaves as expected.
- Context-aware value resolution: Uses get_current_value($args) to read WP_Post/WP_User/WP_Term/WP_Comment and listing macros correctly instead of relying on raw meta reads.
- UI behavior controls: Guides proper configuration of get_id(), get_name(), get_group(), is_for_fields(), need_value_detect(), need_type_detect(), and get_custom_controls() so the condition appears in the right place in the dropdown and shows the right inputs.
Quick Start
Tell the AI: create a JetEngine Dynamic Visibility custom condition class extending \Jet_Engine\Modules\Dynamic_Visibility\Conditions\Base, implement get_id()/get_name()/check() with correct $args['type'] inversion and use get_current_value($args) for listing-aware meta, then register it on jet-engine/modules/dynamic-visibility/conditions/register from your companion plugin.