Name: Cots Parts
Author: MRiabov

Use this skill when a design includes a catalog-backed component. It is a router: it keeps part identity, geometry, motion, and ownership aligned.

Read This

references/contract.md for the class-first COTS contract and motor-specific notes.

Core Rules

Treat the concrete COTS class instance as the part.
Preserve PartMetadata.cots_id, the part label, and COTS usage/provenance on the instance.
Place after construction; do not bake world-space placement into the COTS class.
Do not execute import_recipe; it is provenance, not runtime code.
Separate geometry from motion: the motor body defines fit and frame, while joint or control contracts define direction and actuation.
If benchmark or solution handoffs declare a COTS component, instantiate it in authored geometry. A declared-but-unused COTS part is a contract failure.
Keep benchmark-owned fixtures read-only and engineer-owned parts validated and priced according to ownership.

Use this skill when a design includes a catalog-backed component. It is a router: it keeps part identity, geometry, motion, and ownership aligned.

references/contract.md for the class-first COTS contract and motor-specific notes.

Treat the concrete COTS class instance as the part.
Preserve PartMetadata.cots_id, the part label, and COTS usage/provenance on the instance.
Place after construction; do not bake world-space placement into the COTS class.
Do not execute import_recipe; it is provenance, not runtime code.
Separate geometry from motion: the motor body defines fit and frame, while joint or control contracts define direction and actuation.
If benchmark or solution handoffs declare a COTS component, instantiate it in authored geometry. A declared-but-unused COTS part is a contract failure.
Keep benchmark-owned fixtures read-only and engineer-owned parts validated and priced according to ownership.