Describe It
Describe an image and get it, plus four variations, with no settings panel at all. Built for One Prompt — ship a useful product where the entire interface is a single prompt field. Generation and the variation grid. The interface is deliberately narrow: one path, done properly, rather than a broad surface that half-works at the deadline.
Gallery
Screens
Describe It — main view
Describe It — result state
On the clock
What shipped, what didn't
Completed in time
Generation and the variation grid.
Unfinished / faked
No way to steer a variation without retyping.
Obstacles
Underestimated the parsing work. Cut a whole feature to protect the demo.
Lessons learned
Hardcode the thing you can hardcode. Nobody is scoring your config system.
Process
Prompting approach
Started from a single system prompt describing the user and their constraint, then iterated with the assistant on the Describe It data model before writing any interface code. Full prompt log is in the repository under /prompts.
Fairness
Disclosures
Declared by the builder at submission time, visible to judges before scoring.
Judging
Public feedback
Judges' private notes stay private — this is what they chose to say publicly.
Marcus Bell
Founder, Bellwether Studio
Good instinct on the problem. I would have liked to see the model doing more of the reasoning rather than formatting output.
Hana Kobayashi
Principal Research Engineer, Independent
Good instinct on the problem. I would have liked to see the model doing more of the reasoning rather than formatting output.
Ravi Anand
Head of Design, Tessellate
The idea is strong and the execution is most of the way there. The demo path broke once, which is what separates this from the top three today.
Discussion
0 comments
No comments yet.