From8 specific workflowschoose a task,recipes.jsonprovide ordered parameters,command evidenceandGitHub sourcesrecord actual methods and workflow references separately. Copy, pages, and sample data are original demonstrations; InDesign JSX is not executed.
Confirm units and scope first
First rundesigncraft-cli --versionandcommands; the CLI is not installed with this skill. If missing, follow theofficial release notesto choose a system version and comply with the installation license. The native 0.8 commands in this document may differ from the plugin Web bridge; for an actual host, read the schema first. Use font.list to check the fonts used this time; this example uses the runtime-bundled Source Serif 4 / Source Sans 3 and does not require commercial fonts to be installed on the system by default.
Coordinates, font sizes, and bleed are all in points; 1 mm = 72/25.4 points. rect=[left,top,right,bottom], not [x,y,width,height]. frame.create.spread starts from 0, and positions in the figure are spread coordinates; file.exportPdf.pages uses 1-based page positions, and the two must not be mixed. text.select.anchor/focus are UTF-8 bytes, so the number of Chinese characters cannot be used directly as an offset.
Same-session MCP and standalone CLI
After the editor is ready, call execute step by step on the same MCP service; the exact wrapper is defined by tools/list. First create the text frame, save the actual returned id/story, then pass it to subsequent methods; inspect_document, get_story, and render_page verify structure and pages. Standalone CLI file operations cannot prove that the embedded editor is synchronized.
The manual's capture names return values,{"$ref":"title.story"}which must be bound to actual values and cannot be sent verbatim to the CLI/MCP. The CLI natively supports$N.storyreferences such ascompile scriptsto generate:python write_script.py --recipes recipes.json --scene event-poster --output steps.json, replacing the two input paths with the actual paths for this skill. Thendesigncraft-cli script steps.json --save new.designcraft --export review.pdf --export exchange.idml. The compile script only rewrites references and does not perform layout; all business operations are still completed by the native CLI.
For an existing document, compile with--existingand then usescript steps.json --in input.designcraft --save new.designcraft. This mode skips newDocumentOnly and rewrites references, but you must still adjust the current positions, page counts, stories, and style conflicts first; do not insert a complete new-document example verbatim into an existing layout. Do not manually delete only file.new while keeping the old $N numbering. MCP uses actual return values directly; only the CLI script's reference resolver interprets $N.
Results and delivery
Each output uses a new, unused path; the native CLI will not prevent overwriting for you. Keep the editable .designcraft and any needed IDML and PDF. Reopen and query document.inspect, story.get, and table.get; check preflight issues, and do not claim complete delivery based on exit codes or file headers. For overflow fixes, first prove that overset actually exists, then check that it disappears after the fix and that content was not deleted; recheck after changes to fonts, leading, images, or pagination.
The assertions in the template apply only to the sample input. Review the actual PDF page by page, and verify reading order, data, line breaks, and object overlaps. Successful bleed and PDF export do not mean CMYK, PDF/X, printer, or accessibility acceptance. An interactive PDF with annotations does not mean the target website is usable; sample URLs must be replaced.
Skill store scenario experience
When planning reading order before page layout, laying out long text as story flow, or turning prepress findings into to-do items, readstore workflow adaptation, check using the corresponding Craft method and actual results. Upstream skills are not a runtime dependency.
main development candidate
When importing SVG into native layouts, delivering editable PPTX, using Flex modules for layout, or loading styles across documents, first readmain new workflows and version boundaries. Complete new and changed parameters are recorded separately; do not treat the number of directories as actual acceptance.