explainx / blog
Historian Benjamin Breen vibe-coded a free semantic search tool over 6,500+ prize-winning nonfiction books. How it works, and what critics said.
Jul 17, 2026
Full-stack AI engineer Kr$na (@krishdotdev) posted the "new development cycle" July 16, 2026 — idea in minutes, working demo in hours, six months on the last 10%, then infinity in the graveyard. ThePrimeagen called it first principles. explainx.ai maps where AI actually helps and where human obsession still wins.
Jul 7, 2026
Ternlight puts semantic search on-device: text in, 384-dim vector out, cosine similarity for intent matching — all in ~7 MB in the browser. Here's how it works, when to use it, and how it compares to cloud embedding APIs.
Jul 5, 2026
Ammaar Reshi forked an existing macOS/Linux port of the 2003 RTS Command & Conquer Generals: Zero Hour and used Claude Code's Fable 5 model to add native iPhone/iPad builds and touch controls. The GitHub repo passed 300+ stars, and the Hacker News thread split over how much credit the AI actually deserves.
TL;DR: Historian Benjamin Breen built the Book Prize Index — a free tool covering roughly 6,500 titles that won or were shortlisted for major English-language nonfiction book prizes — using Claude Code and GPT-5.6 for both data collection and the site itself. It supports semantic search (natural-language queries like "classic biographies that are surprisingly weird") alongside traditional filtering, and hit the Hacker News front page with 190+ points. The most interesting reaction wasn't about the tool's usefulness — it was a pointed debate about whether vibe-coding a project about quality undermines its own premise.
Breen, a historian who writes the Res Obscura newsletter, described the origin of the project in personal terms: a college job shelving library books that turned into an "sneakily important intellectual experience" of random discovery — flipping open books he was shelving and occasionally getting absorbed. He built the Book Prize Index to recreate that experience digitally, using book-prize wins as a proxy for quality, since he'd found that books winning or shortlisted for major prizes are "almost always noticeably good."
The process: he had Claude and GPT-5.6 gather lists of finalists and winners from online sources (mostly Wikipedia) across every major English-language nonfiction prize he could identify, then structured that into a searchable, sortable database of roughly 6,500 titles. On top of the structured data, he added semantic search — an embedding model that lets users search by concept rather than exact keyword match.
The site is free to use, hosted at book-prize-index.vercel.app:
"Yes this is actually free. I am paying for the hosting and the API costs entirely because I just want people to find and read more good non-fiction books."
| Question | Answer |
|---|---|
| What is it? | A searchable, browsable index of prize-winning nonfiction books |
| How many titles? | ~6,500, sourced primarily from Wikipedia |
| Built with? | Claude Code and GPT-5.6 for data collection and site build |
| Search type? | Structured filtering + semantic (embedding-based) search |
| Cost? | Free — creator pays hosting and API costs |
| URL | book-prize-index.vercel.app |
| HN reception? | Front page, 190+ points |
| Data export? | Yes — JSON dump available at /data |
Breen is explicit that semantic search — not the curated dataset alone — is what makes the tool interesting beyond a static list:
"There is really nothing 'AI' about this aside from the tool that collected the data and coded it, and, crucially, semantic search, which for me is the most appealing of all current AI tools precisely because it offers a straightforward improvement for a workflow and habit that researchers already have: it makes text search work better."
The practical difference shows up in queries that would fail entirely against a keyword index. Breen cites examples like:
This is the core value proposition of embedding-based semantic search applied to a genuinely useful, narrow domain: it approximates the serendipity of physically browsing library shelves — where adjacency, not exact-match retrieval, drives discovery — in a searchable digital interface. That's a materially different experience than typing a query into Amazon or Google Books, both of which are optimized for commercial relevance and literal keyword matching rather than conceptual adjacency.
The most substantive pushback on Hacker News wasn't about the tool's usefulness — multiple commenters explicitly praised it — but about the irony of using AI to build a project celebrating human-authored quality. Commenter Planktonne put it directly:
"I think my issue with this project — and so many other similar ones — is that the provenance of the code does undermine the intention. If a project purports to be about quality, then knowing that the creator abdicated some of the responsibility for creating the thing they ostensibly care about makes it harder to put faith in them as having high standards elsewhere... This is a project that needs to be cared about sincerely to be trustable/meaningful/useful, and the approach taken casts doubt on that."
This is a genuinely interesting critique because it's not the usual "AI writing is bad" argument — it's about consistency between stated values and production method. The counterargument, made by several other commenters including paxys:
"Very neat site and write-up, but I found this part amusing: 'There is really nothing "AI" about this aside from the tool that collected the data and coded it [...]' So really, everything about it is AI. And that's not a bad thing! It's okay to simultaneously preach the superiority of award winning books over AI-generated garbage while also acknowledging the same AI as a valuable tool for other uses."
The distinction worth drawing out: Breen's actual curatorial judgment — which prizes to include, what counts as a "major" prize, how to weight book-of-the-year lists versus formal prizes — is human-authored decision-making, even though the code and data-scraping pipeline were AI-assisted. Whether that distinction satisfies the provenance critique is a matter of where you draw the line between "the tool" and "the content," which is exactly the debate playing out more broadly this week around Substack's new AI-detection feature and Peter Yang's /no-ai-slop skill — code and prose face the same underlying question of whether AI-assisted production undermines a claim to quality or authenticity.
Breen used the collected dataset to build several standalone visualizations:
That last chart feeds into Breen's broader argument in the post: that nonfiction writing quality likely peaked somewhere between the 1980s and early 2000s, driven by factors like cheaper international travel for research, broader access to archives and rare-book collections following the erosion of class/race/gender barriers, and the Library of Congress's MARC cataloguing standard making sourcing and fact-checking easier — a genuinely interesting historical argument independent of the AI-tooling debate.
If you're building a narrow-domain discovery tool:
/data in response to a commenter request) costs little and meaningfully extends a tool's usefulness beyond your own UI.If you're evaluating AI-assisted side projects generally:
Primary sources: book-prize-index.vercel.app · Res Obscura — Benjamin Breen's Substack · Hacker News discussion
Details reflect Benjamin Breen's July 22, 2026 Substack post and Hacker News discussion as of publication. Dataset size and prize coverage may grow as the creator adds more sources — check the site directly for current scope.