Creative workflows

SolidCraft: Check Your First CAD Part Before Using AI Product Images

SolidCraft is an independent parametric CAD tool. Build a small measurable fixture, check the saved design and export, then separate engineering geometry from generated presentation images.

SJolt Editorial7 min readUpdated
Diagram separating a measured CAD part, an exported reference view and a reviewed presentation image.
Original SJolt editorial diagram. An illustrative workflow, not a product screenshot or a reproduced experiment.

SolidCraft is an open-source parametric 3D CAD application, with a desktop app, browser app, command-line tools and an MCP server for agents. Its editable geometry and feature timeline make it useful for defining a part. It is not an image model, and SJolt does not expose a SolidCraft CAD endpoint.

Start with one simple part whose dimensions you can verify independently. Once the CAD result passes, a rendered view can become a reference for a separate presentation-image workflow. Keep the measured design as the authority for shape, dimensions and fit.

Find the official project and preserve the old design

The official project links solidcraft.io, docs.solidcraft.io and the tangency-labs/solidcraft repository. Older links may use bherbruck/solidcraft or the former SolveCraft name. Use the project’s release page to identify the exact package instead of treating a similarly named download site as authoritative.

At this October 25 check, the latest release is v0.22.0, published at 23:53 UTC on October 24 (07:53 in Beijing on October 25). Saved designs now use format 35, compared with format 34 in v0.21.0. The new version opens earlier designs, but v0.21.0 and older cannot open a design saved by v0.22.0. Keep an untouched copy before upgrading an existing project.

Choose the package for your operating system and architecture, and retain the version with your project notes. The release includes a separate macOS CLI package; having the desktop app does not by itself put solidcraft-cli on your shell path. This guide reviewed documentation and example syntax without installing or executing the application.

The project describes itself as early and usable for simple parts. Its public reference checks cover a specific set of models, not every geometry or downstream workflow. A small acceptance fixture is more useful than assuming that a familiar CAD operation implies complete compatibility with another editor.

Check imported orientation before making the reference image

The v0.21.0 release changes import-orientation handling. STEP and IGES imports ask before turning a file; a SolidWorks import can offer standing it up as the default. The Turn Up Axis command can switch Y-up and Z-up after import in one undo step. Preserve the source file and record the orientation choice before exporting a presentation view.

For an original acceptance fixture, import a deliberately asymmetric test part with a recognizable top face. Capture its starting view, apply the intended axis change, and check dimensions and volume before and after. Orientation can change the bounding-box axes, but a pure rotation should preserve the solid’s volume. Undo once and confirm the starting orientation returns.

When the CAD view becomes an image reference, retain that orientation in the generation brief. A plausible product image with a rotated mounting face is still the wrong deliverable. These are proposed acceptance checks, not measurements from a SolidCraft execution.

Build a rectangular fixture with an analytic answer

The tagged scripting guide uses a commands array containing the same command IDs used by the UI. The following fixture retains its sketch and extrusion steps while omitting the fillet, so the expected volume stays easy to calculate. Save it as block.json in a dedicated test folder.

json
{
  "commands": [
    {
      "command": "sketch.create",
      "params": {
        "plane": "XY"
      }
    },
    {
      "command": "sketch.rectangle.two_point",
      "params": {
        "p0": [
          0,
          0
        ],
        "p1": [
          40,
          30
        ]
      }
    },
    {
      "command": "solid.extrude",
      "params": {
        "distance": 20
      }
    }
  ]
}
bash
solidcraft-cli run block.json --out block.step

With millimetres as the working units, a 40 × 30 × 20 solid rectangular prism has volume 24,000 mm³ and surface area 5,200 mm². These are calculated expectations, not measurements from a SolidCraft run. Confirm the unit setting and measure the result before declaring the fixture passed.

CheckExpected for this fixtureWhat a mismatch suggests
Dimensions40 × 30 × 20 mmWrong units, extrusion distance or selected profile.
Volume24,000 mm³Missing material, multiple bodies or an unintended operation.
Surface area5,200 mm²Unexpected geometry even if the silhouette looks plausible.
Round tripSame dimensions after reopening the exportAn export/import or unit interpretation problem.

Next, change only the extrusion distance to 25 in a copy of the script and generate a separate export. The expected volume becomes 30,000 mm³ and area 5,900 mm². Keep both files and their measurement records. Add holes or fillets only after this baseline works; every extra feature introduces another reason for a mismatch.

Make the agent inspect its own edits

In v0.22.0, the desktop control channel is on by default and solidcraft-cli mcp discovers a running app; without one it starts headless. Use --headless to force an independent design session, or --connect for an explicit app address. Pick the session deliberately so an agent edits the design you are reviewing. Preferences can disable the desktop listener on the next start.

Use list_commands and describe_command to discover the available operation and its arguments. inspect_design reports the timeline and bodies, while measure reports geometric quantities. Ask for the measurement result after each meaningful change. A screenshot helps inspect appearance, but cannot replace a volume or dimension check.

The updated MCP guide adds skill_reference for reading bundled modeling, mechanism, editing and checking instructions without arbitrary file access. For example, {"skill":"solidcraft-modeling"} selects its default reference document. Use that version-matched guidance alongside describe_command; it does not replace measuring the resulting design.

For a short multi-step change, batch defaults to rollback on failure, but inspect the returned rolled_back, applied and not_run fields. A still-running step can prevent rollback and later apply. Keep file export outside the geometry-edit batch and verify it separately; a restored design checkpoint does not establish that every external artifact was restored.

When a bridged call reports still running, use pending to retrieve its eventual result before sending the mutation again. If the bridge connection drops, that result can be lost: inspect the design before retrying. Retain the intended edit and observed result together instead of treating a missing reply as proof that nothing changed.

Keep test designs and exports in a dedicated project directory. The MCP guide documents scoped file access and explicit allow-path directories. Limit the working area to the files required for the part, then save a new revision before exploring a risky feature combination.

Export the exact render job you reviewed

Version 0.22.0 introduces the Render workspace. Its tagged automation guide describes render.preflight, render.start, render.status and render.export through the ordinary execute tool. Keep the complete job identity: session, serial and generation. A one-shot process that starts a job is not a durable background renderer; the CLI or persistent MCP session must remain alive.

For a small acceptance check, capture the part, start a render and record scene_generation. Change the design afterward and confirm that the completed image still belongs to the captured revision. Export only the retained completed job you reviewed. The documented export fails if that image has been evicted instead of silently substituting a newer one. Cancellation can leave an earlier successful image available, so an image on screen alone does not prove that the latest request succeeded.

The Render workspace has several execution paths with different capabilities. The bounded CPU preview path does not promise glass refraction, and native GPU preview can differ from CPU export. Use preflight for the requested setup and review the exported PNG itself. These are documentation-based acceptance steps; no CAD render was executed for this guide.

Use CAD views as references, and keep geometry authoritative

After the fixture passes, produce a clean view of the real part and retain its CAD revision, camera and dimensions. Decide whether the deliverable is an engineering file or a marketing image. A generated studio scene can support the latter, but it does not provide a new editable CAD model or certify a manufacturing tolerance.

SJolt’s Nano Banana 2.1 image-edit route accepts a prompt and one to fourteen public PNG, JPEG or WebP reference image URLs. Its documented controls include aspect_ratio and resolution. Export an image first: a STEP file or a .solidcraft design is not a valid image reference for that route.

An original presentation brief could request a neutral studio background while preserving the enclosure’s silhouette, openings and visible fasteners. Review those details against the CAD view at matching scale. Reject a beautiful result if it invents a port, fills a vent or changes the wall outline. Generated pixels remain a presentation asset even after that visual review.

Store the measured CAD revision, reference raster, generation task ID and accepted image together. Let geometry changes start a new CAD revision, then regenerate the reference deliberately. No SolidCraft connector, CAD conversion service, engineering certification or paid image result is claimed by this workflow.

Sources & further reading

Take the next idea into production.

Explore the models, test a workflow in the playground, and use the same request in your application.

Keep exploring

← All stories