菜单
Routes Elementor v4 / atomic-builder extension work to the correct domain skill. Use when extending atomic widgets, prop types, transformers, dynamic tags, editor packages, variables, CSS converter, or interactions without a named module — or when the user asks "how do I add X" in v4.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/elementor/elementor --skill atomic-builder-extend命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Extends Elementor Editor V2 — elementor/editor/v2/packages PHP filter, init() package contract, app bar / panel / elements-panel slots, v1 adapters, and getMCPByDomain in-editor MCP. Use for editor packages, React UI injection, or editor-mcp tools (not PHP modules/mcp).
Workflow for creating Elementor v4 atomic widgets and container elements — Atomic_Widget_Base, Atomic_Element_Base, define_props_schema, define_atomic_controls, Twig rendering, and registration hooks. Use for new v4 elements, e-my-widget types, or atomic-widgets module work.
Extends Elementor atomic CSS converter — Shorthand_Expander_Base, Property_Converter_Base, Converter_Registry_Factory, Expander_Registry_Factory, covered_properties CI. Use when migrating legacy CSS to Style_Schema PropValues; no public discovery filter exists.
基于 SOC 职业分类
正在显示 SKILL.md
| name | atomic-builder-extend |
| description | Routes Elementor v4 / atomic-builder extension work to the correct domain skill. Use when extending atomic widgets, prop types, transformers, dynamic tags, editor packages, variables, CSS converter, or interactions without a named module — or when the user asks "how do I add X" in v4. |
Source of truth: docs/atomic-builder/README.md. Skills are checklists that link there — do not duplicate the doc tree.
e_atomic_elements (and often e_opt_in_v4) — see getting-started/experiments.md..cursor/skills/ and follow its workflow.docs/atomic-builder/... pages before implementing.The marketplace skill elementor-widget-patterns is v3 only (Widget_Base, Controls_Manager, content_template). For atomic / v4 work, use the child skills below — not legacy widget patterns.
| Intent | Child skill | Primary docs |
|---|---|---|
| New widget or container element | author-atomic-widget | atomic-widgets/authoring-widgets.md |
$$type, prop schema, validation, transformers | extend-prop-types-transformers | fundamentals/prop-types.md, transformers.md |
| WordPress data source / dynamic binding | extend-dynamic-tags | dynamic-tags/extending.md |
| Editor UI, package, slots, in-editor MCP | extend-editor-v2 | editor-packages/extending-editor.md |
| Design tokens / kit variables | extend-variables | variables/types.md |
| Legacy CSS → atomic style props | extend-css-converter | css-converter/extension.md |
| Motion / interactions tab | extend-interactions | interactions/editor.md |
Public path — third-party plugin in its own repo: subclass + WordPress hooks/filters documented in child skills; own npm package for editor JS.
Internal path — Elementor Core / Pro: change modules/atomic-widgets/, packages/packages/core/, or packages/packages/pro/; follow module ownership in linked docs.
Pick one child skill from the table, open its SKILL.md, and execute that checklist end-to-end.