When should you use it?
- You build something visual with a coding agent
- The agent cannot see what it made
- You want quicker iteration
Not for: Text-only programs; Projects with no way to capture images
What do you need, and what do you get?
You need
- Web view of the scene
- Camera control endpoint
- Screenshot tool for the agent
You get
- Screenshots the agent reviews
- Feedback loop from comments
- Exported model
How does it work, step by step?
- Expose the viewRun the scene in a browser the agent can screenshot.
- Add camera controlGive it an endpoint to move the camera.
- LoopHave it change the model, look, and adjust.
- Add feedbackLet it watch a comment box where you leave notes.
- ExportAdd model export for your CAD or printing tool.
The prompt
Our own prompt, inspired by neomantra on Hacker News and written to work in Claude Code. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
You can move the camera with {camera_endpoint} and take screenshots of the scene. After each change, look at the model from three angles and describe what you see. Compare it with this target look: {target}. Stop after {max_loops} loops or when it matches, and list what still differs.
Inspired by neomantra on Hacker News: Comment in Generative "AI": The Guitar Hero of Creativity. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Screenshot loops burn tokens; set a limit.
- The agent will optimize for physics unless you describe the look you want.
- Check exported models in your CAD tool.
Our take
neomantra's project shows the biggest bottleneck in visual work with agents: by default they cannot see what they made, so a person ends up describing screenshots in words. Giving Claude a way to pose the model, take its own pictures and move the camera through an HTTP endpoint closes that loop, and the comment box lets the human drop feedback into the same channel without breaking the flow. The skill Claude wrote for itself is a nice touch, since the next session starts already knowing how to look. The story also carries a limit worth remembering: the loop produced a convincing physics simulation, not necessarily a beautiful camel. Agents optimize what they can measure, so state the look you want explicitly, with reference images and a few words on proportions and mood, and cap the number of iterations so it does not polish endlessly. Export the geometry early and open it in your own CAD or slicer, because what renders nicely in a browser may still fail as a buildable LED frame.
Where the time goes back: The agent fixes visual problems on its own instead of waiting for you to describe them.
FAQ
Why give it a camera?
Did it get the look right?
Source and credit
Inspired by neomantra on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Comment in Generative "AI": The Guitar Hero of Creativity
- Creator
- neomantra on Hacker News
- Published on
- Hacker News
- Original date
- Aug 7, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.