SuperAPI AI Directory
Partner中文AI newsFavorites
Skillsdesigncraft-editor

designcraft-editor

Design & creation

View repository

Updated 11-02 02:06

About this skill

designcraft embedded editor
  1. From the tool list of currently loaded plugins, find the designcraft-editor service. 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://designcraft/panel.htmlwhen the host supports native MCP Apps. A text-only tool result does not mean the interface has been opened.
  3. When Codex does not automatically render the panel, call open_browser_editor, and hand the returned editorUrl to the host's embedded browser opening capability. Codex Desktop can call open_in_codex, with target set to browser and url set to the actual return value. Do not guess a fixed port for the local page path.
  4. Only one editing page per instance. Call editor_status, and 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.

Manage documents with open_document/new_document, verify content with inspect_document and get_story; execute commands with execute, save with save_document, and check page by page with render_page.

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

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

If the tool is not registered, once you have the plugin's actual directory, you can run the following in the project terminal: node ui/dist/adapter.mjs --serve, 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 must not start a separate backend claiming to share the session.

When done, save the project and reopen to verify; read the actual exported file. Browser storage, preview screenshots, and submitted render jobs do not count as workspace delivery.