SuperAPI AI Directory

cadcraft-editor

Coding & development

View repository

Updated 11-05 01:01

About this skill

cadcraft embedded editor
  1. Find the cadcraft-editor service from the tool list of the currently loaded plugin. Call open_editorwith the absolute path of this task's workspace, passing workspaceon the first call; relative file paths can be handed to the specific open tool once the editor is ready.
  2. Render ui://cadcraft/panel.htmlwhen the host supports native MCP Apps. A text-only tool result does not mean the interface has opened.
  3. When Codex does not automatically present the panel, call open_browser_editor, and hand the returned editorUrl to the host's built-in browser open capability. Codex Desktop can call open_in_codexwith target as browser and url as the actual return value. Do not guess a fixed port from the local page path.
  4. Open only one editor page per instance. Call editor_statusand wait until attached or ready is true before proceeding; if loading fails, handle the page error first.
  5. Use the same service for all edits in this round. The native CLI and the Web editor are not the same in-memory document; before switching, you must save and explicitly reopen.

Use open/new_drawing to open or create, query_entities to verify geometry; execute to run commands, save to save, render to preview.

If the host supports only MCP, tool-calling capability and embedded UI are two different things. The same editorUrl can be used in an external browser, but you must explicitly state that this is not in-host embedded acceptance.

When the development candidate is missing ui/dist/adapter.mjs , first build according to plugin ui/README.md . Do not guess paths from arbitrary caches and do not bypass validation. This skill installed independently does not include the editor service; you need to install the companion plugin or configure its MCP backend.

If the tools are not registered, once you have the plugin's actual directory, you can run node ui/dist/adapter.mjs --servein the project terminal, specifying this task's workspace via the environment variable CRAFT_WORKSPACE_ROOT . Keep that process alive; this mode can display the UI, but automation must still connect to the corresponding MCP instance and cannot start another backend and claim it shares the session.

When done, save the project and reopen to check; read the actual exported file. Browser storage, preview screenshots, and submitted render tasks do not equal workspace delivery.