solidworks-ai-bridge

name

solidworks-ai-bridge

description

Bridge a local AI coding agent to SolidWorks through the Windows COM Automation API for automated CAD modeling, parametric part and assembly creation, macro-like API calls, template discovery, dependency setup, controlled document cleanup, preview image export, and neutral CAD export for downstream CAE/CFD workflows such as Ansys Fluent, Ansys Mechanical, COMSOL Multiphysics, or other simulation tools. Use when the user asks to connect an agent with SolidWorks, drive an open SolidWorks session, avoid accumulating many Part/零件 windows, troubleshoot SldWorks.Application COM access, create SolidWorks models automatically, export preview images, or export geometry for simulation.

SolidWorks AI Bridge

Use the Windows COM Automation entrypoint SldWorks.Application to control SolidWorks from the local machine. Prefer Python with pywin32 for agent-driven automation because it is scriptable, easy to inspect, and can be extended into downstream workflows such as STEP/Parasolid export, meshing, Ansys Fluent, Ansys Mechanical, COMSOL Multiphysics, or other CAE/CFD tools.

Operating Assumptions

• This skill only works on Windows with SolidWorks installed, licensed, and COM-registered.
• Tested on SolidWorks 2024 (RevisionNumber = 32.5.0). Expected to work with recent Windows desktop SolidWorks versions, roughly SolidWorks 2020-2025, when SldWorks.Application is available.
• The agent must be able to run local shell commands and Python in the same user session as SolidWorks.
• Opening SolidWorks first is recommended but not required.
• If SolidWorks is already open, attach with GetActiveObject("SldWorks.Application").
• If SolidWorks is closed, try Dispatch("SldWorks.Application"); this can launch SolidWorks only when installation and licensing are valid.
• Do not silently install SolidWorks. SolidWorks is commercial software; instruct the user to install it through their licensed Dassault/SOLIDWORKS installer, company software center, or administrator-managed package.
• It is acceptable to install Python dependencies such as pywin32 when the user permits dependency setup.
• Avoid leaving many generated Part1, Part2, or 零件1, 零件2 documents open. Generated test parts should be saved, exported if needed, then closed by default. Keep the document open only when the user explicitly asks to inspect or edit it interactively.

Compatibility

Use this compatibility language when users ask which SolidWorks versions are supported:

Tested on SolidWorks 2024. Expected to work with SolidWorks 2020-2025 Windows desktop versions that expose the SldWorks.Application COM Automation API.

Do not claim support for SolidWorks Online, browser-only workflows, macOS/Linux, remote agents without local COM access, or unlicensed/unregistered installations.

Quick Probe

From this skill directory, run:

python .\scripts\sw_probe.py

If pywin32 is missing and installing dependencies is appropriate:

python .\scripts\sw_probe.py --install-deps

Create a test part:

python .\scripts\sw_probe.py --create-test-part --output .\solidworks_com_test.SLDPRT

Create the focused meshing gear-pair example and export a preview image:

python .\scripts\create_gear_pair_test_part.py --output .\solidworks_gear_pair_test.SLDPRT --image-output .\docs\images\solidworks-exports\gear_pair_centered.png

The gear-pair script closes the generated SolidWorks document after saving and exporting. Add --keep-open only when the user wants the generated model left open for inspection.

If the agent cannot rely on the current working directory, resolve the skill directory first and call the script by absolute path.

Standard Workflow

1. Check Python and pywin32:

python --version
python -m pip show pywin32

2. Probe SolidWorks with scripts/sw_probe.py.

3. If the probe connects, write task-specific automation using the same connection pattern:

import pythoncom
import win32com.client

pythoncom.CoInitialize()
try:
    try:
        sw = win32com.client.GetActiveObject("SldWorks.Application")
    except Exception:
        sw = win32com.client.Dispatch("SldWorks.Application")
        sw.Visible = True
finally:
    pythoncom.CoUninitialize()

4. For model creation, discover or provide a .prtdot, .asmdot, or .drwdot template. Common locations include:

C:\ProgramData\SOLIDWORKS\SOLIDWORKS <year>\templates
C:\Users\Public\Documents\SOLIDWORKS\SOLIDWORKS <year>

5. Save generated files under the user's workspace unless another output path is requested.
6. Export preview images through SolidWorks only when useful for documentation or user verification. Keep one focused preview image in docs unless the user explicitly asks for a gallery.
7. Close generated SolidWorks documents after save/export by default to reduce memory usage and avoid cluttering the user's session. Preserve unrelated user-opened documents.

Modeling Rules

• Use SI units in SolidWorks API calls: meters, radians, kilograms.
• Convert user-facing millimeters to meters explicitly.
• Use win32com.client.VARIANT(pythoncom.VT_DISPATCH, None) for nullable COM dispatch arguments such as SelectByID2 callouts.
• Support localized default plane names where practical, including Front Plane and 前视基准面.
• Prefer parameterized functions for geometry creation so the same model can be regenerated for design sweeps.
• For CAE/CFD handoff, export neutral geometry such as STEP (.step/.stp) or Parasolid (.x_t) after model creation.
• For downstream simulation, describe the path broadly unless the user specifies a solver: SolidWorks automation -> neutral geometry export -> Ansys Fluent / Ansys Mechanical / COMSOL Multiphysics / other CAE tool -> meshing, solving, and post-processing.
• For repository documentation, prefer a single representative complex example image instead of many repetitive simple test images.

Troubleshooting

• ModuleNotFoundError: No module named 'win32com': install pywin32.
• Invalid class string: SolidWorks is not installed or the COM ProgID is not registered.
• GetActiveObject fails but Dispatch works: SolidWorks was not open; continue with the new instance.
• COM calls fail in PowerShell with type-library errors: use Python + pywin32.
• New document fails: locate a valid SolidWorks template and pass it to NewDocument.
• Plane or feature selection fails: check localized names and use an explicit COM null dispatch argument.
• Many Part or 零件 windows remain open: close only generated documents that the script created; do not close unrelated user work. For generated examples, use scripts that call CloseDoc after saving/exporting, and provide --keep-open as an explicit opt-in.