twincat-stlisted
Install: claude install-skill SionVerhoef/twincat-st
# Structured Text that survives contact with a machine
> **Reference material only. Not for safety functions.** All code you generate must be reviewed and validated by a qualified engineer against the drive and platform documentation before it runs on a machine. Every hand-over ends with the fixed line in step 5.
**Target: the CODESYS V3 dialect family.** TwinCAT 3 (build 4024.x) is the verified platform. Its PLC layer is CODESYS-V3-derived, so the vendor-neutral core applies to CODESYS too; CODESYS library names, the `.project` container and its tooling are **not covered** and were never checked on a CODESYS install. On a CODESYS question, answer from the core and say the vendor specifics are unverified rather than guess.
**Out of scope:** Siemens SCL, Rockwell Studio 5000 ST, OpenPLC/matiec. Those are different dialects — matiec implements IEC 61131-3 **2nd Edition** and has no `METHOD`, `PROPERTY`, `EXTENDS` or `INTERFACE` at all. Guidance from here would be fluent and wrong. Say so and stop.
**Scope traces and recordings** — reading a `.svdx`, sizing a recording, diagnosing an axis from measured data — belong to the companion skill `twincat-scope`. Load it if it is installed.
**TwinCAT NC axes** — axis configuration and parameters, NC error codes (0x4xxx), homing in the NC, coupling and cam tables, `.xti` axis files, and why an axis won't enable or move — belong to the companion skill `twincat-motion`. Load it if it is installed. This skill still owns how the PLC cod