Design a 3D-printable replacement part from a photo
Users report sending a photo and a short description of a broken part and getting a CAD design, an STL file, and slicer settings back. You need your own 3D printer.
Last verified: Oct 17, 2026
The problem
A small broken plastic part can mean replacing the whole thing.
How the bot does it
Users report:
- @Nomar5g says his bot drafted a CAD design, exported it as an STL, and suggested slicer settings for a part to fix a trash can lid that kept opening. He says it printed in 10 minutes and works.
- @roger_kappler says he started with a photo and one line to his 3D printing bot, and about 1.5 hours later held a part that fit.
- You need your own 3D printer. Check fit and strength before you rely on a part.
Setup steps
- 1Take a clear photo of the broken part and measure it.
- 2Ask the bot for a CAD design, an STL file, and slicer settings.
- 3Print a test piece and check the fit.
- 4Don't use printed parts where a failure could hurt someone.
Example prompt
Here's a photo of [broken part] and its measurements. Draft a CAD design, export an STL I can 3D print, and suggest slicer settings. Tell me what to check for fit and strength. Change nothing else.
The result
A printable file and settings to try. These are users' own accounts, and the fit depends on your measurements.
Results are the user's own claim. We haven't checked them.
Sources
Want new ones in your inbox?
Pick what you're into. We'll send the best new prompts and templates, plus the weekly robot show.
Related prompts
Keep your help center in sync with code changes
xAI's support post says its bot reviews code changes and suggests matching updates to the help center, so articles don't drift out of date.
Each day, review merged changes in [repo]. List any help center articles that are now out of date and draft the updates. Don't publish anything: I review and publish.
Look into a slowdown after a release
The xAI docs show a bot looking into a slowdown after a release. It reads dashboards and traces and writes up the likely cause, keeping facts apart from guesses, before an engineer digs in.
Investigate the checkout latency increase since yesterday's release. Use our dashboards and traces, separate facts from hypotheses, and link the evidence for each. Don't change alerts or production settings. Change nothing.
Monitor and debug your backend with the Supabase plugin
Use the Supabase plugin in Grok Bot to monitor, debug, and ship changes to your backend, with production changes kept behind approval.
Every morning, check my Supabase project for errors, failed functions, and slow queries. Report them with suggested fixes. Don't change anything without my approval.