solidworks-automation

SolidWorks Automation

Use this skill when the task requires executable SolidWorks automation code or a live COM session for parts, assemblies, drawings, Simulation, Flow Simulation, sheet metal, weldments, molds, or tooling. For design-only decisions or parameterization methodology without implementation, use sw-designer instead.

Operating rules

• Reuse an active SolidWorks instance with GetActiveObject("SldWorks.Application"); only fall back to Dispatch when no usable instance exists.
• Reuse sw.ActiveDoc when it matches the task. Create a new document only when explicitly required or no suitable document exists.
• Wrap temporary documents in try...finally and close them by title; do not leave orphan windows or COM references.
• Treat units as meters inside the API. Keep user-facing dimensions in millimeters and convert explicitly.
• Before any mutation, capture a geometry fingerprint: feature count, body count, bbox, volume, and relevant dimensions.
• After each mutation, force a rebuild, re-read the fingerprint, and assert the expected change. Do not report success from a return value alone.
• If an assertion fails, stop the current strategy, print the traceback and current feature-tree state, and propose a concrete fallback. Do not silently catch the failure.
• Do not guess API names, argument counts, or COM null handling. Probe the live object with dir(), get_com_member, or a tiny subprocess before using an uncertain API.
• Keep real project files and generated models under F:\codexspace\...; do not copy full projects to the Desktop or C drive.

Recommended workflow

1. Preflight capability. State whether the current runtime can inspect images/PDFs and whether SolidWorks is available. For drawing-driven work, identify the drawing source and who or what performed visual verification.
2. Build a dimension ledger. Separate exact, inferred, designer-choice, and unsupported dimensions. Bounding-box matching is not sufficient; account for recesses, lands, grooves, PCD holes, chamfers, and secondary features.
3. Choose an execution channel.
   • Prefer Python COM for connection, sketching, additive extrudes, measurements, and file I/O.
   • Prefer one sketch with outer and inner closed loops plus FeatureExtrusion2 for through holes and rings.
   • Use C# or a generated VBA macro for methods that Python COM cannot call reliably, especially complex cut features with more than 12 parameters.
4. Implement in the project workspace. Keep builder code modular, parameter-driven, and testable without loading the full manual.
5. Execute and validate. Compile the script first. If SolidWorks is available, run it, force a rebuild, then assert feature/body counts, bbox, volume, and output-file existence. Use screenshots or rendered views when geometry intent matters.
6. Report truthfully. Distinguish completed geometry, markers-only holes, approximations, and unsupported features. Never describe an uncut marker as a through hole.