elementor-development

Route ambiguous Elementor requests to the correct owning surface.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/korflux/skills --skill elementor-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: elementor-development
Source: https://github.com/korflux/skills/tree/main/skills/elementor-development
Command: npx skills add https://github.com/korflux/skills --skill elementor-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ambiguity in routing Elementor-related requests to the correct owning surface (Free, Pro, Hello parent theme, or Hello child theme) to ensure correct implementation and ownership.

Core Features & Use Cases

  • Routing decision: determines the appropriate specialized Elementor or Hello theme skill based on the request.
  • Anchor identification: identifies the first concrete anchor (hook, class, file) to inspect.
  • Escalation guidance: provides validation pathways to confirm routing decisions.

Quick Start

Route an ambiguous Elementor request to the correct specialized surface (Free, Pro, Hello parent, or Hello child).

Frequently Asked Questions about elementor-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I determine if an Elementor feature belongs to Elementor Free, Elementor Pro, or the Hello theme?

To determine the correct owner for an Elementor feature, route the request by identifying the primary surface (Free, Pro, or Hello parent/child) and pinpointing the first concrete hook, class, or file to inspect.

What is the best way to resolve ambiguity when routing Elementor requests to the correct owning surface?

The best way to resolve Elementor routing ambiguity is to identify the primary owner between Free, Pro, and Hello theme surfaces, then follow the provided validation pathways to confirm the routing decision.

How do I find the first hook, class, or file to inspect for an unclear Elementor implementation?

To find the first anchor for an unclear Elementor implementation, the routing workflow pinpoints the specific hook, class, or file that governs the requested feature on its correct owning surface.

Do I need different workflows for customizing the Hello Elementor parent theme versus its child theme?

You need different workflows for the Hello Elementor parent and child themes because routing distinguishes between them to ensure correct implementation ownership and directs you to the appropriate specialized surface.