I use Claude at work as my dev team: I write the brief and review. I tried the same thing with my new 3D printer, and it worked.
A programmer successfully applied their workflow of using Claude for code development to their new 3D printer. By writing clear briefs and providing specific feedback, similar to their professional role as a client and reviewer, they were able to design and produce custom items like a MacBook Pro 16 stand and a bike mount. The user was surprised that no new tools or skills were needed beyond their existing brief-writing and feedback-giving abilities.
时间与来源
时间显示为 UTC
显示时区：UTC
本地时区尚不可用，暂时显示 UTC。
发布当时偏移：UTC+02026年10月29日 10:46 UTC
收录当时偏移：UTC+02026年10月30日 01:00 UTC
- 发布
- 2026年10月29日 10:46
- 收录
- 2026年10月30日 01:00
- 来源类型
- 开发者社区
- 档位
- 社区
- 信源状态
- 正常
档位是按信源手工设定的编辑判断，不是逐条打分。
I'm a programmer and have used Claude for code for a long time. Somewhere along the way my role changed: I'm the client and the reviewer now. I say what I want, look at what comes back and say what's wrong.
Then I bought a 3D printer. I'd never modelled anything, so I tried the same setup I use at work. I connected an MCP server for 3D modelling, wrote a few skills of my own, and kept my usual role.
It works almost exactly like a code review. I describe the part, Claude builds it, I print a small test piece and come back with something like "the screw won't go in". It fixes it, I print again. A test print is my test run.
Two things came out of it so far: a stand for my MacBook Pro 16 that I couldn't find anywhere, and a bike mount that holds the computer and the light at the same time.
What surprised me: I didn't have to learn a new tool. Writing a clear brief and giving specific feedback, the stuff I already do at work, was enough.