I gave Opus 5.5 one prompt and six hours to visualize Invisible Cities
- ID
- 33346
- Status
- summarized
- Published
- 08 Oct 2026, 8:00 PM
- Fetched
- 09 Oct 2026, 2:24 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://quesma.com/blog/invisible-cities-one-shot/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.5
- Created
- 09 Oct 2026, 2:25 AM
- Tags
- Audience
- developersvibe_codersai_ml_learnersai_agent_users
What happened
Piotr Migdał describes a one-shot experiment to visualize all 55 cities from Italo Calvino's Invisible Cities as a three.js/pnpm interactive piece, using a prompt that forbids questions and grants six hours to reach 'masterpiece' quality. The excerpt cites a GPT-6 Astra run in Codex that completed end-to-end in 53 minutes at medium effort for about $10 in API tokens, with some AI design slop and extra concepts/comments, and references Ryan Sael's Opus 5.5 lens-lab result at 1h26 and $25.66 API cost. It sits on a 256-point/136-comment Hacker News thread.
Why it matters
If you use coding/design agents for one-shot interactive visuals, this gives rough time/cost baselines: about 53 minutes and $10 for the cited GPT-6 Astra run versus 1h26 and $25.66 for the cited Opus 5.5 lens lab, while the author still flags AI design slop. Treat 'one prompt, no questions' as a prototype accelerator, not a finished product; budget for cleanup of overlapping visuals and extra concepts rather than expecting a production-ready masterpiece.
Discussion angle
Compare one-shot 'masterpiece' prompts against iterative workflows: if a 53-minute/$10 run still produces AI design slop, what review checklist do you apply before shipping the output?