From8 scenario workflowsselect the current task;recipes.jsonprovide ordered methods and parameters,command evidencesave native command descriptions,sourcefixed GitHub documentation commit.
First runcadcraft-cli --versionandcadcraft-cli commandsto confirm the CLI is ready; the skill does not bundle a CLI. If missing, follow theofficial release notesto choose the system version; installation must comply with host authorization. First confirm units, actual dimensions, and output purpose. Each entry defaults to an independent drawing; when combining multiple scenarios, first arrange positions and offsets to avoid everything stacking at the origin. All examples are millimeter model space; the title frame does not equal print settings. For hole parameters, radius is the radius; dimensions are calculated from geometry, and expected values must not be written into text to pose as measurements. The room example sets DIMSCALE=100 only in a new drawing so text and arrows fit the 5000 mm space; for existing drawings, first check the existing dimension style and do not override globally. Use dark dimensions and labels for white-background review images to avoid low contrast caused by on-screen layer colors. Separate layers for outlines, holes, centerlines, and dimensions.
MCP and CLI
When the embedded editor already has a task, use the same MCP session. First read the current tool schema and command catalog, then call step by step; use native CAD tools withexecute {"command":"circle","params":{"center":[10,10],"radius":3}}; the plugin forwards enhanced runtime tools to the host; rely on the names and schemas returned by the current tools/list, and do not infer from other Craft tool names. The returned handle is used for subsequent actual object selection and cannot be guessed.
Standalone CLI:cadcraft-cli run --metric --cmd 'circle {"center":[10,10],"radius":3}' --save part.dxf. Each方法ID 空格 JSONis a single argv; put the steps for the same drawing in one run. On Windows, prefer process argument arrays to avoid the shell interpreting JSON. For existing drawings userun input.dxf, skipping allnewDocumentOnlysteps, including INSUNITS setup. First usegetvar {"name":"INSUNITS"}to read the existing units; only confirmed millimeter drawings may directly adopt these examples; inch or meter drawings must first explicitly convert the actual coordinates and dimensions in a copy, and must not merely change the unit variable. Do not use this example's new on an existing session and clear the drawing.
After saving under a new name,cadcraft-cli run part.dxf --cmd 'drawing.inspect {"entities":true}'query the actual entities; usetextsto query readable text, and useconvert part.dxf part.svgto output a review image. Check dimensions, hole centers, outline closure, and units; do not just check that the file exists. Editing another file with the native CLI cannot prove that the embedded editor changed synchronously; work in the same view must use methods supported by the current bridge session.
Delivery
Keep an editable DXF and a review image. Examples do not replace engineering design, tolerances, or manufacturing requirements; unspecified hole spacing, materials, and tolerances must not be claimed as satisfied. Assertions apply only to technical regression of the accompanying examples; real drawings should be checked against actual data and the rendered drawing viewed.
Skill store scenario experience
When encountering rebuilding parts from explicit dimensions, geometric relationships of plan drawings, or reviewable title frame handoff, readstore workflow adaptation, and use the corresponding Craft methods and actual result checks. Upstream skills are not runtime dependencies.