Before executing specific methods, read Craft scenario commands and parameters, and execute according to the object selection, session, input replacement, and result checking described therein.
Connection and execution
First check the current MCP tool list and editor_status. When there is create_node、run_command、inspect_document , use the actual tool JSON schema; do not guess parameters. Use list_commands to find the commands and parameters required for this scenario, then execute.
Enhanced Web MCP operations must occur on the same page that is already open and ready. The official original Web 0.6.0 only has an interactive view; file services are not yet implemented; when these MCP tools are absent, do not pretend that edits or saves have occurred. Standalone native figcraft-cli mcp is a separate session, and switching must be explicitly communicated. When the CLI is available, use figcraft-cli commands --json to check commands; do not install missing tools yourself.
Reference:FigCraft v0.6.0 MCP、CLI. Commands are subject to the currently loaded version.
Work steps
- Inspect existing frames, container hierarchy, and main content widths, and confirm which modules should wrap, collapse, or be hidden.
- Use list_commands to query actual commands such as layout.add, and convert relevant containers to horizontal, vertical, or grid; use gap, padding, sizingH, and sizingV to express layout intent, and avoid simultaneously fixing in-flow children with absolute x/y.
- Create three frames: 390×884, 768×1024, and 1280×1024; keep the same content and semantic order for important components.
- Check parent-child constraints of Hug and Fill, long titles, empty content, and larger numbers of list items; capture screenshots and read absoluteBounds for each size separately to identify out-of-bounds nodes.
- Save the editable project and reopen it; export images for the three sizes, and explain breakpoint behavior and interactions that still require real frontend validation.