Single Field
Type anything about your calendar and it does the right thing. No menus, ever. Built for One Prompt — ship a useful product where the entire interface is a single prompt field. Intent routing across seven calendar operations. The interface is deliberately narrow: one path, done properly, rather than a broad surface that half-works at the deadline.
Gallery
Screens
Single Field — main view
Single Field — result state
On the clock
What shipped, what didn't
Completed in time
Intent routing across seven calendar operations.
Unfinished / faked
Ambiguous requests silently pick the most common intent.
Obstacles
A dependency version mismatch cost six minutes. Pinned it and moved on.
Lessons learned
Boring, well-understood tools beat interesting ones when there's no time to debug.
Process
Prompting approach
Started from a single system prompt describing the user and their constraint, then iterated with the assistant on the Single Field 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.
Reused a personal utility file for date formatting (~40 lines), linked in the repo README.
Started from the official framework starter template, unmodified.
Judging
Public feedback
Judges' private notes stay private — this is what they chose to say publicly.
Marcus Bell
Founder, Bellwether Studio
The scope discipline here is the whole story. One path, finished, demoed without a stumble. That is what a 30-minute build should look like.
Hana Kobayashi
Principal Research Engineer, Independent
Excellent use of the model — it is doing actual work here, not decorating a form. The failure case you showed earned you points rather than costing them.
Ravi Anand
Head of Design, Tessellate
The scope discipline here is the whole story. One path, finished, demoed without a stumble. That is what a 30-minute build should look like.
Discussion
0 comments
No comments yet.