figcraft

Installation
SKILL.md

FigCraft

Operate FigCraft through its structured automation interface. Preserve the user's requested design workflow and target file.

Protocol reference

Read the relevant sections of references/control-protocol.md before constructing calls. This is the downloaded upstream protocol, captured on 2026-11-15.

Source: FigCraft control protocol. The documentation is distributed under the bundled MIT license. Relative links inside the snapshot (e.g. mcp.md) refer to upstream documentation; resolve those against https://github.com/storytold/figcraft/blob/main/docs/ when needed. If installed behavior differs, inspect the installed command registry through engine.commands rather than inventing parameters.

Select the session

  • The desktop app serves the control channel on 127.0.0.1 only: figcraft --control 7979 [file.figcraft|file.svg|image]. For the user's open file, drive that live window, directly or through the attached MCP server (figcraft-cli mcp --attach 7979, see upstream docs/mcp.md).
  • The app can show files in several windows. Every method takes an optional window id from window.list (0 is the main window); without it, requests go to the window last in front. engine.execute, document.inspect, node.get, and ui.render also take an optional document (open file id from doc.list, or a path) to act on a background tab.
  • The web build exposes the same methods as promises on window.figcraft when the page URL carries a control query entry.
  • Discover available executables and sessions first. If the required connection or executable is missing, report the concrete prerequisite; this skill does not install FigCraft or register an MCP server.

Transport and limits

Installs
60
GitHub Stars
14
First Seen
Nov 2, 2026