@vention/vention-skills 0.9.15 → 0.9.16

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "vention",
-  "version": "0.9.15",
+  "version": "0.9.16",
   "description": "Vention skills for coding agents: write MachineLogic applications, build machine designs, and diagnose deployed machines.",
   "author": {
     "name": "Vention"

package/README.md

@@ -1,6 +1,6 @@
 # Vention skills
 
-Version 0.9.15. Skills for coding agents that work with Vention machines, packaged as one plugin, `vention`, in the `vention-skills` marketplace.
+Version 0.9.16. Skills for coding agents that work with Vention machines, packaged as one plugin, `vention`, in the `vention-skills` marketplace.
 
 | Skill                       | What it does                                                                                                                         |
 | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vention/vention-skills",
-  "version": "0.9.15",
+  "version": "0.9.16",
   "description": "Vention skills for coding agents: write MachineLogic applications, build machine designs, and diagnose deployed machines.",
   "license": "MIT",
   "type": "module",

package/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "vention",
-  "version": "0.9.15",
+  "version": "0.9.16",
   "description": "Vention skills for coding agents: write MachineLogic applications, build machine designs, and diagnose deployed machines.",
   "author": {
     "name": "Vention"

package/skills/vention-design/SKILL.md

@@ -3,7 +3,7 @@ name: vention-design
 description: Create, build and edit Vention machine designs and design graphs for agentic layout. Use when the user wants to start a new design, lay out an automation cell, add or reposition components in a Vention design, generate a machine layout from a description, add or place a floor plan image under a design, list a design's versions, or inspect an existing design graph. Trigger on MachineBuilder designs, design graphs, assembly graphs, extrusions, actuators, robot mounting, cell footprints, floor plans, or a machine-builder URL.
 license: MIT
 metadata:
-  version: "0.9.15"
+  version: "0.9.16"
   author: Vention
 ---
 

package/skills/vention-machine-logic/SKILL.md

@@ -3,7 +3,7 @@ name: vention-machine-logic
 description: Write, edit, validate, and deploy MachineLogic Python applications for Vention machines with the machine-logic-sdk and the Vention CLI. Load it before writing or changing any Python that talks to a Vention machine, however short, since device names and version-specific SDK calls come from here. Use to program a Vention machine or MachineMotion controller, drive actuators, conveyors, robots, pneumatics, or digital I/O, change an existing application, build a state machine, debug from logs, or pull, push, or link with the Vention CLI (vention or vn). Trigger on MachineLogic, machine-logic-sdk, MachineMotion, MachineBuilder applications, the Vention CLI, or a directory holding .machine-code-app-directory-info.json. Printing what the machine or robot holds now (positions, taught targets, calibration, I/O) is a program: files on disk hold only as-designed values. Not for explaining an existing machine or its configuration in words when no program is asked for, nor for Python that never touches the machine.
 license: MIT
 metadata:
-  version: "0.9.15"
+  version: "0.9.16"
   machine-logic-sdk: ">=3.0,<4"
   author: Vention
 ---

package/skills/vention-machine-logic-hmi/SKILL.md

@@ -3,7 +3,7 @@ name: vention-machine-logic-hmi
 description: Build or edit the custom operator HMI of a MachineLogic application, the React touch screen in customui/ that runs in MachineBuilder and on the MachineMotion pendant, wired to the application's Python process through vention-communication. Use when the user asks for an operator screen, a custom HMI or UI, a touch panel, start and stop buttons, live machine state on screen, or recipes an operator picks, for a Vention machine or inside a directory holding .machine-code-app-directory-info.json. Uses @vention/machine-ui, @vention/machine-apps-components and @vention/machine-logic-ui-sdk. Do not use for the no-code HMI Builder, or for the Python motion logic alone (that is vention-machine-logic).
 license: MIT
 metadata:
-  version: "0.9.15"
+  version: "0.9.16"
   author: Vention
 ---
 
@@ -151,6 +151,8 @@ The machine-apps-components README is behind its code: `NavigationBar` takes `Na
 ## Design rules
 
 - Wrap the app in `machineUiHmiTheme`.
+- Give the app an Operate page at `/`, any setup pages it needs (such as Recipes), and a Logs page: a `LogsPanel` fed by the Events stream, as the example's `logs-page.tsx` does, where the operator finds out why a cycle faulted. Nav labels name the page and never echo a top-bar action, and their icons don't suggest one. Never "Run", "Start" or a play icon: beside the top bar's Start, the operator reads it as a second Start button.
+- The Operate page is what the operator watches during a run, so it reads from across the cell. Copy the example's `operate-page.tsx` and adapt it rather than starting from a blank page. Top to bottom: a heading saying what the station is doing or the recipe running, the run's segmented progress bar, the settings for the next run (disabled while one runs), and one short paragraph on what Start and Stop do. Lay it out with `Box` or `Stack` gaps, each readout a label above its value in theme text variants. Never set `fontSize` or `lineHeight`: a value sized by hand overlaps its label.
 - Show each piece of information in one place only. The `StatusTopBar` already shows the state, so a page never repeats it, not even as a status indicator or an alert titled with the same word. A page adds only what the bar cannot say: the cause of a fault, what happens next, what to do.
 - The screen fits the pendant without scrolling: keep `body { margin: 0 }` from the example's `index.html`, or the full-viewport root overflows it. Only the page area between the two bars scrolls.
 - Exactly one way back to Control Center: the `NavigationBar`'s own button, which confirms before leaving. Keep `ui.showDefaultBackToControlCenterButton` `false` in `project.json`, or the pendant lays a second one over the screen.
@@ -179,7 +181,7 @@ The HMI drives physical machinery that can injure someone.
 - Start never fires on page load, on reconnect, or from a stream message. Only an operator's tap, confirmed in a modal, starts motion.
 - Start and Stop live in the `StatusTopBar`, so they are on every page. Do not repeat them on a page. Raise the bar above `theme.zIndex.modal`, as the example's `app.tsx` does, or an open `VentionModal` covers Stop.
 - Stop stays enabled unless the station is known to be ready or already stopping. That includes while the stream is disconnected: a dropped stream may hide a moving machine. Every other command is disabled while disconnected.
-- A tap on Stop shows at once. While the station stops, the Stop button reads "Stopping…", the Run page's progress bar marks where the run now ends (the cycle in progress amber, the cancelled ones hatched and struck through), and a line by the heading says the emergency stop halts at once. Say it on the screen the operator already watches rather than in a separate alert.
+- A tap on Stop shows at once. While the station stops, the Stop button reads "Stopping…", the Operate page's progress bar marks where the run now ends (the cycle in progress amber, the cancelled ones hatched and struck through), and a line by the heading says the emergency stop halts at once. Say it on the screen the operator already watches rather than in a separate alert.
 - Send Start with a `timeoutMs` and an abort signal, and abort it when the stream drops. A Start the operator can no longer see must not land later; say it was not confirmed and to check the station.
 - The HMI never offers a way around an emergency stop, safety interlock, light curtain or guard, not even a hidden one for testing.
 - The confirmation for anything that starts motion says what will move. The button itself can just say Start.
@@ -196,7 +198,7 @@ The HMI drives physical machinery that can injure someone.
 - `customui/src/client.ts`, `customui/src/use-stream.ts`: the generated client and the stream hook.
 - `customui/src/station.ts`: state labels and colors, and when Start and Stop are enabled.
 - `customui/src/app.tsx`, `customui/src/main.tsx`: the shell with Start, Stop and the Start confirmation, the theme, the router and the keyboard.
-- `customui/src/pages/`: the Run, Recipes and Logs pages.
+- `customui/src/pages/`: the Operate, Recipes and Logs pages.
 
 ## Common mistakes
 

package/skills/vention-machine-logic-hmi/examples/indexing-station-hmi/customui/src/app.tsx

@@ -1,5 +1,5 @@
 import { Box } from "@mui/material"
-import { IconBook, IconHistory, IconPlayerPlay, IconPlayerPlayFilled, IconPlayerStopFilled } from "@tabler/icons-react"
+import { IconBook, IconHistory, IconLayoutDashboard, IconPlayerPlayFilled, IconPlayerStopFilled } from "@tabler/icons-react"
 import { NavigationBar, StatusTopBar } from "@vention/machine-apps-components"
 import type { LogEntry, LogType } from "@vention/machine-apps-components"
 import { COLORS, VentionAlert, VentionModal } from "@vention/machine-ui"
@@ -9,7 +9,7 @@ import { client, openEvents, openStatus, STATUS_STALL_MS } from "./client"
 import type { Event, Recipe } from "./gen/app_pb"
 import { LogsPage } from "./pages/logs-page"
 import { RecipesPage } from "./pages/recipes-page"
-import { RunPage } from "./pages/run-page"
+import { OperatePage } from "./pages/operate-page"
 import { canStart, canStop, describeState, errorText, isStopping } from "./station"
 import { useStream } from "./use-stream"
 
@@ -125,7 +125,9 @@ export function App() {
         <Routes>
           <Route
             path="/"
-            element={<RunPage status={status} connected={connected} recipe={recipe} onRecipeChange={setRecipe} onError={setCommandError} />}
+            element={
+              <OperatePage status={status} connected={connected} recipe={recipe} onRecipeChange={setRecipe} onError={setCommandError} />
+            }
           />
           <Route path="/recipes" element={<RecipesPage connected={connected} onError={setCommandError} />} />
           <Route path="/logs" element={<LogsPage entries={logEntries} />} />
@@ -133,7 +135,7 @@ export function App() {
         </Routes>
       </Box>
       <NavigationBar variant="flex">
-        <NavigationBar.Item id="run" label="Run" path="/" icon={<IconPlayerPlay size={NAV_ICON_SIZE} color="white" />} />
+        <NavigationBar.Item id="operate" label="Operate" path="/" icon={<IconLayoutDashboard size={NAV_ICON_SIZE} color="white" />} />
         <NavigationBar.Item id="recipes" label="Recipes" path="/recipes" icon={<IconBook size={NAV_ICON_SIZE} color="white" />} />
         <NavigationBar.Item id="logs" label="Logs" path="/logs" icon={<IconHistory size={NAV_ICON_SIZE} color="white" />} />
       </NavigationBar>

package/skills/vention-machine-logic-hmi/examples/indexing-station-hmi/customui/src/pages/{run-page.tsx → operate-page.tsx}

@@ -5,7 +5,7 @@ import { client } from "../client"
 import type { Recipe, StationStatus } from "../gen/app_pb"
 import { canStart, errorText, isStopping } from "../station"
 
-interface RunPageProps {
+interface OperatePageProps {
   status: StationStatus | undefined
   connected: boolean
   recipe: Recipe | undefined
@@ -34,7 +34,7 @@ function CycleProgress({ cycle, cycleCount, stopping }: { cycle: number; cycleCo
   )
 }
 
-export function RunPage({ status, connected, recipe, onRecipeChange, onError }: RunPageProps) {
+export function OperatePage({ status, connected, recipe, onRecipeChange, onError }: OperatePageProps) {
   const [recipes, setRecipes] = useState<Recipe[]>([])
   const stopping = isStopping(status, connected)
 
@@ -83,6 +83,10 @@ export function RunPage({ status, connected, recipe, onRecipeChange, onError }:
         onChange={event => onRecipeChange(recipes.find(candidate => candidate.id === Number(event.target.value)))}
         menuItems={recipes.map(candidate => ({ value: candidate.id, displayText: candidate.name }))}
       />
+      <Typography variant="paragraph18Medium">
+        Start indexes a part, clamps it, dwells and releases it, once for each cycle of the recipe. Stop finishes the move in progress, then
+        opens the clamp. The emergency stop halts everything at once.
+      </Typography>
     </Box>
   )
 }

package/skills/vention-machine-logic-hmi/examples/indexing-station-hmi/server.py

@@ -181,7 +181,7 @@ class IndexingStation(StateMachine):
         except Exception as error:
             await self.release_safely()
             self.fault_message = f"cycle {self.cycle}: {error}"
-            await publish_event("error", f"Cycle {self.cycle} faulted", f"{error}. Clear the cause, then press Reset on the Run page.")
+            await publish_event("error", f"Cycle {self.cycle} faulted", f"{error}. Clear the cause, then press Reset on the Operate page.")
             self.trigger(BaseTriggers.TO_FAULT.value)
 
 

package/skills/vention-monitoring/SKILL.md

@@ -3,7 +3,7 @@ name: vention-monitoring
 description: Diagnose deployed Vention machines from controller state, history, health, and activity data. Use when the user reports a machine that is down, faulted, offline, slow, or underperforming, asks why a cycle time regressed, wants to interpret MachineMotion event data or drive and brake status, asks about OEE or uptime, or wants to know which machine in a fleet needs attention. Trigger on a MachineMotion serial number plus any complaint.
 license: MIT
 metadata:
-  version: "0.9.15"
+  version: "0.9.16"
   author: Vention
 ---