Experiment

electronics

active

A workbench for designing and validating 3D-printed enclosures, brackets, and robot parts through a Claude-driven OpenSCAD + Godot pipeline. Components live in a shared inventory; assemblies are render-reviewed, collision-checked, and simulated before printing.

How far can a coding agent get as a CAD collaborator when the modelling language is just text? It reads, edits, and re-renders OpenSCAD from a few angles, looks at the renders, checks assemblies for collisions with CSG, then drops the finished build into a Godot sim to watch it move.

What I’m into here:

Skill-driven CAD: /add-component-model, /review-openscad, /validate-assembly as the handful of commands that make up a reusable hardware-design agent
Visual review loops: render, look, fix, re-render, as a workable stand-in for eyeballing every iteration myself
Inventory-aware design: a SQLite component database plus per-project assemblies, so the agent stays grounded in what’s actually on the shelf

Field notes

No posts tag this experiment yet. When a post does, add experiments: [electronics] to its frontmatter.

← All experiments