Electromechanical planning and runtime guidance for the current Problemologist electronics stack. Use only when a plan or implementation explicitly includes an `electronics` section, benchmark `electronics_requirements`, circuit validation, electronics review, or simulation evidence for an electromechanical system.
Use this skill for current repo behavior, not legacy prompt lore.
It is for electromechanical reasoning and handoff alignment, not for importing runtime internals into authored solution_script.py.
references/api_reference.md
Use when you need the current schema or helper surface.references/circuit_patterns.md
Use when composing an ElectronicsSection or reviewing a simple circuit topology.references/routing_best_practices.md
Use when routing 3D wires or reviewing clearance/tension risks.../cots-parts/SKILL.md
Use when the electronics plan includes catalog-backed motors, relays, connectors, wires, or other off-the-shelf components that need part identity and provenance preserved.../render-evidence/SKILL.md
Use when the task needs visual inspection of routed wiring, moving electromechanical evidence, or repeated blocker diagnosis through renders.assembly_definition.yaml as the source of truth for planner-authored electronics.electronics section and no explicit circuit-validation task, do not load this skill just because the design has motors or wires. Do not invent electronics unless the task requires it.objects.parquet pose-history sidecar together; frames.jsonl is sparse timing metadata only.electronics section or explicit circuit-validation intent.utils.* import surface unless the task is specifically editing repo internals.worker_heavy/utils/electronics.py, shared/circuit_builder.py, shared/pyspice_utils.py, shared/wire_utils.py, and shared/models/schemas.py.solution_script.py should stay on the canonical utils.submission / utils.metadata surface and use direct build123d geometry for any physical implementation details.