AutomationView sequences are plain Python files. Any AI assistant with access to your project folder — Claude Code, GitHub Copilot, Cursor, or a local LLM — can write .seq and .machine files directly.
Before asking an AI to write a sequence, add a CLAUDE.md file to your project root. This file gives the AI the API reference and project rules it needs to produce correct code. See What is a CLAUDE.md file? for the template.
.seq file.Example prompt:
"Write a sequence for a pneumatic cylinder. Sensors: cyl_fwd (forward), cyl_bwd (backward). Output: cyl_extend. The cycle starts on start_cmd, extends, confirms position with a 300ms timer, then retracts."
The AI will produce a complete .seq file following the rules in your CLAUDE.md.
Before loading the file in AutomationView, ask the AI to self-review:
"Check this sequence against the rules in CLAUDE.md — look for missing timer confirmations, dual-sensor checks, and any physical output using S/R qualifier."
The Diagnostics panel in AutomationView will also catch structural issues (deadlocks, unreachable steps, address conflicts) once the file is loaded.
Share the existing file content and describe the change:
"Add an emergency stop step to this sequence. When emergency_stop is active, freeze the sequence in a dedicated step and wait for reset_btn before returning to the initial step."
For machines with repeated equipment (multiple axes, conveyors, or press units):
"Create a dynamic Verin sequence parameterized for forward/backward motion, then create a machine file that instantiates it 4 times: verin_1, verin_2, verin_3, verin_4."
Tip: The more specific you are about variable names and timing constraints, the less you will need to edit the output. If your project already has sequences, point the AI to them as style references.