メニュー
Use when working on Simulink or Simscape Electrical motor-drive power-electronics models, including PMSM, BLDC, induction motor drives, FOC, DTC, torque/speed/current loops, inverter-fed machines, and drive waveform validation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when working on Simulink or Simscape Electrical power-electronics models, including inverter, DC-DC converter, rectifier, motor-drive, battery/BMS, renewable-grid, HVDC/FACTS, converter layout, gate-routing, solver, waveform, control-algorithm, or simulation validation tasks.
Use when working on Simulink or Simscape Electrical DC-DC converter models, including buck, boost, buck-boost, flyback, forward, resonant, bidirectional converters, MPPT front ends, duty-cycle control, and regulation diagnostics.
Use when working on Simulink or Simscape Electrical three-phase grid-connected inverter models, including SPWM/SVPWM, T-type or NPC three-level bridges, grid-side voltage/current waveform balance, gate routing, sector tables, and switching-state validation.
Use when working on Simulink or Simscape Electrical battery, charger, and BMS-linked power-electronics models, including pack behavior, balancing, SOC/SOH, bidirectional charging, protection, and storage converter interfaces.
Use when working on Simulink or Simscape Electrical HVDC and FACTS models, including VSC-HVDC, LCC-HVDC, STATCOM, SVC, UPFC, transmission-system controls, power-flow regulation, and grid disturbance studies.
Use when working on Simulink or Simscape Electrical multilevel converter models beyond the populated three-phase inverter notes, including MMC, cascaded H-bridge, flying-capacitor converters, capacitor balancing, and arm-energy control.
| name | motor-drives |
| description | Use when working on Simulink or Simscape Electrical motor-drive power-electronics models, including PMSM, BLDC, induction motor drives, FOC, DTC, torque/speed/current loops, inverter-fed machines, and drive waveform validation. |
Developing subskill. Use this file to recognize motor-drive scope and choose evidence to collect. Apply the root simulink-power-electronics workflow; do not reuse grid-inverter assumptions unless the inspected model path is genuinely shared.
Read references/inspection.md for corpus-derived inspection notes before diagnosing motor-drive examples. Treat those notes as developing guidance, not a complete methodology.
Use the motor-drive subskill for inspection and debug planning when the goal is to trace machine control paths, not only to classify files. Current analyzed examples repeatedly show deep subsystem hierarchy, heavy From/Goto routing, fixed-step controller workflows, and existing scope/measurement surfaces. Before adding new logs or changing parameters, build a tag map and identify the top-level split between plant, inverter, controller, and measurements.
Treat these checks as required before tuning or editing:
Id/IqPromote only after adding motor-control references, a repeatable Simulink workflow, and checks for currents, torque/speed response, sensor alignment, and inverter gate legality.