First Query
Point it at a database you've never seen and it writes three questions worth asking, with the SQL. Built for Cold Open — build a tool that helps someone do the very first step of a task they have been avoiding. Schema introspection and question generation. The interface is deliberately narrow: one path, done properly, rather than a broad surface that half-works at the deadline.
Gallery
Screens
First Query — main view
First Query — result state
On the clock
What shipped, what didn't
Completed in time
Schema introspection and question generation.
Unfinished / faked
Postgres only, no permissions handling.
Obstacles
Rate limits hit at minute 20 and forced a caching layer I hadn't planned for.
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 First Query 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.
Elena Voss
VP of Engineering, Harbor Compute
Solid build with a clear user in mind. The interface is doing less than it could — a second pass on hierarchy would lift this considerably.
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.
Tomas Eriksen
Developer Advocate, Independent
Solid build with a clear user in mind. The interface is doing less than it could — a second pass on hierarchy would lift this considerably.
Discussion
0 comments
No comments yet.