Generates a modern Word (.docx) documentation for a TestStand sequence file — title + short file description, a real table of contents, one section per sequence (description, parameter table with By Value / By Reference, compact flow-indented step listing per Setup/Main/Cleanup group), and a rendered dependency…
Generates a modern, interactive HTML presentation of a TestStand sequence file — a dark glassmorphism single-page app with Setup/Main/Cleanup phase cards, clickable subsequences that open a detail overlay, and a "Code & Flowchart" compare view (flowchart next to a rendered TestStand step-listing). The flowchart nodes…
Converts a flowchart or test description into a well-structured TestStand sequence. For every step, interactively asks whether a SequenceCall should be linked in detail (target file + subsequence) or whether the step should be inserted as a plain placeholder (e.g. Statement) without any link. Applies whenever the user…
Writes and runs Caraya unit tests for LabVIEW code — settles what is worth asserting, builds one test VI per group of cases with the subject called as an ORDINARY STATIC SUBVI, runs the suite through a generated Caraya runner, and reads the JUnit report. It does NOT run a negative control unless the task asks for one…
Creates LabVIEW classes end to end — settles the data model, writes each .lvclass with its private data control through NI's own project provider VIs, links inheritance, binds .ctl typedef fields so they point at the file rather than carrying a de-linked copy, generates every accessor on dynamic dispatch, and verifies…
Generates a modern Word (.docx) documentation for a LabVIEW library, class or project — title + short description, a real table of contents, a rendered structure diagram of the library up front (folders with their access scope, VIs, nested classes), a UML class diagram when the target is object-oriented, and then one…
Writes and runs LUnit unit tests for LabVIEW code. Use ONLY when the user explicitly asked for LUnit, e.g. "schreib LUnit Tests", "teste das mit LUnit", "add LUnit test cases" — the default unit-test framework in this repository is Caraya, and labview-caraya-unit-test is the agent for it. SCAFFOLD, AND THE FRAMEWORK…
Changes an EXISTING LabVIEW VI — settles what must change, checks up front whether the VI can survive the round trip at all, searches the palette and then NI's shipping examples for the new functionality, backs up the icon, regenerates the VI from edited AIXML, updates its documentation, and puts the icon back. Use…
Creates a NEW LabVIEW VI end to end — clarifies the input/processing/output contract, searches the palette and then NI's shipping examples for something to reuse, builds the VI from that template (or from primitives when there is nothing to reuse), adds it to a project, writes its documentation into the AIXML…
Writes and runs JKI VI Tester unit tests for LabVIEW code. Use ONLY when the user explicitly asked for VI Tester, e.g. "schreib VI Tester Tests", "teste das mit VI Tester", "add VI Tester test cases" — the default unit-test framework in this repository is Caraya, and labview-caraya-unit-test is the agent for it.…
Instructions for Zuehlke/labview-mcp, covering working in this repository, generating labview code, which interface to reach for, when a tool call fails and when labview disappears.
Read, write and run LabVIEW 2026 code from an AI assistant — VIs as text via AIXML, palette and shipping-example search, and seven bundled LabVIEW agents. Windows x64 only.