skills.rest
MRiabov
MRiabovCOMMUNITY
Explore all skills by this author →
GitHub

electromechanics-syntax

Author motion contracts for electromechanical assemblies in YAML syntax.

2|Updated Jan 31, 2026
Search Tags:#handoffs#build123d#motor-control#assembly-definition#electromechanics#motion-syntax#cad-coding
One-click install
npx skills add https://github.com/MRiabov/Problemologist-AI --skill electromechanics-syntax
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: electromechanics-syntax
Source: https://github.com/MRiabov/Problemologist-AI/tree/main/.agents/skills/electromechanics-syntax
Command: npx skills add https://github.com/MRiabov/Problemologist-AI --skill electromechanics-syntax

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a formal, implementation-ready syntax for authoring electromechanical motion contracts, ensuring consistent communication between design and runtime controllers.

Core Features & Use Cases

  • Define moving-part contracts using stable identifiers and DOFs.
  • Map motion requirements to canonical control modes and performance parameters.
  • Use in handoffs where motorized parts, electronics, and CAD definitions intersect.

Quick Start

Identify moving parts in your handoff and bind each part's name, DOFs, and control mode to a single, stable label.

Frequently Asked Questions about electromechanics-syntax

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define motion contracts for electromechanical assemblies in CAD coding?▼

You define motion contracts by editing assembly_definition.yaml to bind moving_parts with stable identifiers, degrees of freedom, and canonical motor-control modes.

What control modes are supported for motor-control syntax in assembly definitions?▼

The canonical motor-control modes supported for motion syntax are CONSTANT, SINUSOIDAL, and ON_OFF, ensuring consistent communication between design and runtime controllers.

How do I maintain stable part identifiers across planner and solution handoffs?▼

Keep PartConfig.name stable across handoffs to preserve motor provenance in COTS and motion contracts, ensuring consistent tracking of moving parts and electronics.

When do I need to formalize electromechanical motion syntax in build123d projects?▼

You need formal motion syntax when authoring handoffs where motorized parts, electronics, and CAD definitions intersect, requiring structured AssemblyPartConfig.control parameters.

Can I use this motion syntax to coordinate final assembly with moving parts?▼

Yes, the syntax applies when editing final_assembly and moving_parts configurations, coordinating motion contracts for electromechanical assemblies with stable DOF mappings.

What's the best way to map motion requirements to performance parameters for motorized parts?▼

Map motion requirements by binding each part's name, DOFs, and control mode to a single stable label, ensuring implementation-ready syntax for runtime controllers.

Related Skills

Explore More Design & Creative Skills→
MRiabovMRiabov

engineer-plan-reviewer

Validate engineering plan artifacts against stage manifests and motion-trajectory contracts.

Community
Advanced
MRiabovMRiabov

benchmark-planner

Generate machine-readable benchmark definitions and narrative plans from briefs.

Community
Advanced
MRiabovMRiabov

cots-parts

Instantiate catalog-backed COTS parts and validate metadata, placement, and ownership in build123d workflows.

Community
Intermediate
zunyiqingfeng-codezunyiqingfeng-code
2

solidworks-automation

Automate SolidWorks CAD workflows via Python COM interface.

Community
Advanced