kernelcad-authoring

kernelCAD — authoring

Author or modify kernelCAD models in TypeScript. Scripts live in .kcad.ts files; the kernelCAD CLI (kernelcad evaluate <file> and kernelcad export stl|step|dxf|3mf|glb <file> -o <out>) executes them via an OpenCASCADE WASM kernel.

Agent authoring loop

Use this loop for every non-trivial model edit:

1. Classify the job: blockout, production-ish part, reference replication, assembly/mechanism, sheet metal, or standard-part integration. Load the matching specialty skill before editing.
2. Write the design brief in plain engineering terms: purpose, external dimensions, interfaces, materials/finish if relevant, moving parts, manufacturability assumptions, and what must be proven. If the request is ambiguous on load-bearing parameters — overall dimensions, units, symmetry, part count, fit/clearance targets — ask 1–3 targeted clarifying questions BEFORE generating geometry; if you proceed anyway, list each assumption in the brief and encode it as a named param() so the user can correct it without a rewrite.
3. Map words to geometry: turn important prompt phrases into named source sections, parameters, parts, connectors, materials, or tests so the generated model stays traceable to the user's words.
4. Plan parameters and artifacts: identify the .kcad.ts source file, named parameters, imported STEP files, expected exports, and the smallest verification command set before writing geometry.
5. Edit source only: treat .kcad.ts, prompt/brief markdown, and provenance metadata as source. Do not hand-edit generated PNG, MP4, STEP, STL, score JSON, or capture metadata.
6. Generate explicit targets: run the exact render/export/capture command for the requested artifact. Avoid broad directory refreshes unless the task is a release/demo rebuild.
7. Validate deterministically: run kernelcad evaluate, relevant exports, assembly/review tools, interference checks, and scorer gates before accepting visual evidence.
8. Inspect visual artifacts honestly: when a PNG/MP4/render is produced, open/read it and report what is visible. If the image shows wrong proportions, floating parts, occlusion, unreadable details, or a bad camera crop, repair source and regenerate.
9. Packetize visual evidence: when visual evidence matters, run kernelcad render inspect <file> <outDir> to produce a deterministic inspection bundle: a manifest naming the source file, command, generated artifacts, and caveats, plus canonical RGB views. Add --channels rgb,mask,depth,normals when machine-readable object masks, depth, or view-space normals are needed. Use --focus <names> or --hide <names> to isolate feature ids or assembly part names when clutter would obscure the check. Keep richer channels in the same manifest packet; do not replace the canonical RGB views.
10. Repair one cause at a time: target the smallest source change that addresses the failing check, then rerun the same check. Do not loosen gates or silently skip failing evidence.