cimatron-api

Add a new ApiCommand to a Cimatron API plugin project. In practice this means scaffolding a sibling plugin DLL, since Cimatron 2026 is one-command-per-plugin.

Build a Cimatron 2026 API plugin in the current working directory. The csproj sets `OutputPath=$(CimatronRootPath)`, so a successful build writes the DLL directly into `C:\Program Files\Cimatron\Cimatron\2026.0\Program` (or wherever `CimatronRootPath` resolves). **The build is the deploy.** There is no separate publish step.

Scaffold a new Cimatron 2026 API plugin in the current folder with VSCode F5 wired up to build, deploy, launch Cimatron, and attach the managed debugger.

Package the Cimatron API plugin in the current working directory into a single self-contained `.exe` installer that an end-user can run on their own machine. The installer bundles the plugin DLL (and the per-plugin `<ApiName>.ico`, with a legacy-`icon.ico` fallback for older projects) as embedded resources, self-elevates via UAC, detects the user's installed Cimatron, copies the DLL into `<CimatronRoot>\Program\`, and writes the `[Plugin Ext Commands]` entry into `ExternalCommands.ini`. Running it again with `/uninstall` reverses both steps.

Register a Cimatron 2026 plugin by adding (or updating) an entry in `ExternalCommands.ini`. The INI is what makes the plugin DLL visible to Cimatron — without it, the DLL sits in the Program folder but never loads.

Use when the user asks to audit, sanity-check, or conformance-check an existing Cimatron API plugin against the standard — e.g. "review my plugin", "is this command name OK?", "does my MenuPath follow the standard?", "audit this folder". Read-only — reports findings, never edits files. For broad code review (security, correctness, reuse), use the general agent instead. For applying fixes, use api-scaffold or the appropriate `/add-command` / `/new-cimatron-api` flow.

Use proactively when the user asks to create, scaffold, set up, or "start a new" Cimatron API plugin / command / hook project, AND when the canonical `/new-cimatron-api` and `/add-command` slash commands don't fit (e.g. the user wants a hook in addition to a command, multiple toolbar commands in one DLL, or a COM-pattern command for legacy reasons). For the standard "new plugin" and "add a command" flows, point the user at `/new-cimatron-api` and `/add-command` first — this agent fills the gaps those commands don't cover.

Use to smoke-test a Cimatron API plugin headlessly — opens a fixture part, invokes the plugin's command via CadCimAiShell, captures log output and document state deltas, and reports pass/fail. Use after building a plugin and before declaring a feature done. Hands off to `cimatron-modeler` for the actual modeling RPC.

Subagent that runs the cimatron-api MCP doc-search workflow on the main agent's behalf — useful for parallelizing lookups or protecting the main context. Drives `mcp__cimatron-api__search` / `read_file` / `list_index` (or the discovered `mcp__api-docs__*` / `mcp__cimatron-deploy__*` variants when the user's MCP config registers the same server under a different name) and answers from official Cimatron docs. Falls back to disassembling shipped `interop.*.dll`s with `ildasm` when no MCP variant is reachable. For the inline reference-card form, see the cimatron-api SKILL. Do NOT use for editing source code.

Use when the user asks to create, scaffold, or "start a new" Cimatron Feature Guide command — e.g. "add a feature guide to this plugin", "scaffold a 2-stage feature guide", "set up the FG events plumbing". Produces the ICimCommand (or ICimWpfCommand) entry point, the 4-interface events class, one or more stage classes, the per-project data classes (MyFeatureData / MySpFigureData / CaptureImageData / ToolServicesData), and the three-way IConnectionPointContainer.Advise wiring. For just adding SP figures to an existing stage, use sp-figure-builder instead.

Reference card for the cimatron-api MCP doc-search workflow — loaded into the main thread when Claude answers a Cimatron API question directly. Documents the search/read_file/list_index tools, ranking weights, and index schema. To DELEGATE a lookup to a subagent, use the cimatron-api-docs agent instead.

Offer to put a freshly-scaffolded Cimatron API plugin under git, with one initial commit so the user has a clean rollback point before they start changing things.

You are a specialized assistant for surfacing the user-visible log entries a

Package a built Cimatron API plugin into a single self-elevating `.exe` installer end-users can double-click to deploy the DLL into their Cimatron Program folder and register it in `ExternalCommands.ini`. Same EXE supports `/uninstall` to reverse both steps. Invoked by the `/package-installer` slash command; also runnable standalone when a caller needs the recipe without the orchestration layer.

Run the same build → deploy → launch → attach sequence that VSCode's F5 performs, from inside the conversation. Use this when the user wants to iterate on a Cimatron API plugin without alt-tabbing to VSCode.