Ask The Docs
One field over your entire documentation site, with answers that cite the exact heading. Built for One Prompt — ship a useful product where the entire interface is a single prompt field. Crawl, index, and cited answers. The interface is deliberately narrow: one path, done properly, rather than a broad surface that half-works at the deadline.
Gallery
Screens
Ask The Docs — main view
Ask The Docs — result state
On the clock
What shipped, what didn't
Completed in time
Crawl, index, and cited answers.
Unfinished / faked
Re-crawl is manual.
Obstacles
Underestimated the parsing work. Cut a whole feature to protect the demo.
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 Ask The Docs 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.
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 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.
Hana Kobayashi
Principal Research Engineer, 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.
Ravi Anand
Head of Design, Tessellate
Good instinct on the problem. I would have liked to see the model doing more of the reasoning rather than formatting output.
Discussion
0 comments
No comments yet.