Distinguish instances from source documents
One part document may appear multiple times in an assembly, with a distinct placement, referenced configuration and suppression state for each instance. Preserve hierarchy and complete instance identifiers rather than merging components by filename. Define how lightweight components, virtual components and subassemblies will be handled.
Make coordinates and positioning explicit
A component's local coordinates must be combined with parent transforms to determine its assembly-space position. Base placement on stable datums, interfaces and engineering constraints. Bounding boxes or visible screen positions alone generally cannot recover design intent.
Insert, mate, rebuild and read back
Identify component sources and target configurations before positioning or mating. After each operation, inspect rebuild results, constraint states and referenced configurations, with actionable records for failures. Batch operations should distinguish completed, unattempted and failed items.
Verify against real versions and models
Validate API automation using the project's SolidWorks version, component library and assembly templates. An operation possible by hand may not work programmatically in every document state. Cover unloaded components, missing references, configuration switches and repeated runs so failures are detectable and results recoverable.