genie-editor-client

Genie Editor host-side client integration workflow

Focus on the Genie Editor host-side client integration workflow, with the goal of implementing property editing, multi-option design comparisons, card option switching, and page environment information declaration capabilities in the current project.

This skill does not depend on the Genie online closed loop. When the Genie backend is online, the online context can be reused; when it is not online, the implementation can also be completed directly based on the current code, page structure, host state, and user requirements.

Applicable scenarios

When these signals are hit, prioritize using this skill:

• The user wants to "expose editable items" or "make it editable in the adjustment panel"
• The user wants to uniformly organize editable items by page
• The user wants to first produce multiple directions, then compare and decide which one to proceed with
• The user wants to turn multiple directions into switchable options within the page
• The user wants to supplement page locating information so that the current page and corresponding implementation can be quickly found during debugging
• The Genie backend is not online, but property editing, design comparison, or option switching implementation still needs to be completed

Quick triage

• Property editing, page-level property aggregation → read references/property-editing.md
• Multi-option design comparison, card option switching → read references/design-bid.md
• Page environment information, debugging locating, host resource context → read references/environment-context.md

Implementation principles

• tweak / schema / values / adapter / update / card option switching prioritize reuse @axhub/genie-editor-client
• Page resource context / filePath / targetPath / projectPath prioritize going through createGenieEditor(...).host.getResourceContext() or window.__GENIE_EDITOR_HOST__
• Terminology alignment schema、values、adapter、update
• Page environment information should prioritize providing the minimum necessary resource context, without piling up temporary debugging noise
• The host is responsible for business fields, default values, and write-back semantics
• Page-level property aggregation is not creating another global static configuration, but performing aggregated display based on element-level tweak registration results
• If the current environment supports sub-agents, independent implementations can be split out; the main agent retains overall constraints and final review

Delivery requirements

The final reply must contain at least:

• The sub-processes that were hit
• Which files were modified
• Which properties or option fields were exposed
• Which verifications were performed

Reference

• references/property-editing.md
• references/design-bid.md
• references/environment-context.md