Search prototype

A search design, built as working software.

A search over films, books and the characters, places and things in them. I designed it and built all three parts: the content, the index and the interface.1

Project facts

Role
Designer and sole builder
When
January 2026, five days1
Built
Content pipeline, indexer, interface
Content
Nearly a thousand entries2
Stack
React, Vite, Mantine, MiniSearch, OpenAI
Index
One 3 MB file, no server
Tests
18 on the indexer
Code
Public on GitHub

3.6k

links between entries.

915

entries, in ten kinds.

10

ms response times.

The problem

I built the search I'd designed at Klue.

In late 2024 I led the UI design of a new search at Klue: one card for every kind of content, and filters that could keep something, leave it out, or take either.3 Expression through software, especially for dynamic concepts, is much stronger than Figma files when communicating with engineers. In January 2026, after I'd left Klue, I built the design as working software, on content of my own.

See the design at Klue
Klue's redesigned search showing results for “Cirrus”: a grid of identical result cards for a company, a product, a board, a battlecard, a sales call, a highlight and a win-loss report, under a search field and four filter buttons, Types, Topics, Companies and Sources.

The design at Klue. A search for Cirrus: a company, a product, a battlecard, a sales call and more, each in the same card.

What I owned

I designed it and built all of it.

I carried the design over and built the content, the index and the interface, alone.4

The solution

Every filter offers only what's left.

Every filter shows only the options that still have results. Pick one and the rest recount, so nothing you can pick leads to zero results.5 I pulled the interface together in a React and Vite app, with Mantine and a custom design system theme.

The query DeLorean, with the DeLorean Time Machine first, then Doc Brown's Garage, Peabody Farm and Mr. Fusion.
The Franchise filter set to Sherlock Holmes, with the Type row offering only Character, Location, Person, Item and Book, above 221B Baker Street and A Study in Scarlet.
Three chosen filters: Middle Earth plain, plus The Hobbit in green and not Person in red, with Type offering Character, Location and Person, above Balin and Dwalin.
The sort menu open with Relevance, Alphabetical (checked) and Type, over Back to the Future results in alphabetical order, starting with Alan Silvestri.

A match in an entry's name ranks highest, then one in its other names, so Emmett finds Doc Brown. Then come the names of the entries it's linked to, then its tags and description.

Filters narrow the results by type, genre, era, tone, theme, franchise, role and trait. Choose Sherlock Holmes, and Type offers only the five kinds of entry Holmes has.

Click a chosen filter to change its state: plain is any of, + is must, ! is not.

Sort by relevance, name or type, in either direction.

Crime and Thriller chosen, with Thriller clicked through its states: plain with 259 results, plus with 36, not with 91, and plain again with 259.

States cycle. Clicking changes the state type, and results update instantly.

// Check exclude filters
for (const filter of excludeFilters) {
  if (values.has(filter.tag.toLowerCase())) return false
}

// Check include (MUST) filters
for (const filter of includeFilters) {
  if (!values.has(filter.tag.toLowerCase())) return false
}

// Check none (OR) filters - must match at least one
if (noneFilters.length > 0) {
  const matchesAny = noneFilters.some((f) => values.has(f.tag.toLowerCase()))
  if (!matchesAny) return false
}
The three states. From src/hooks/useSearch.ts in the search repository, lines 133–147.

Underneath, part one: the content

First, something to search.

I needed a base of quality content that I could design and work with. I started from a list of films and books I'd read or watched. For each title, I generated its characters, places, things, groups and people, then an entry for each one, linked to the entries that already existed. That came to nearly a thousand entries.2

The content pipeline in six steps: Extract, Generate, Validate, Find missing, Links and Fix.

The pipeline. Six steps, from a title to linked entries.

Underneath, part two: the index

Search for Nolan, and his characters come up.

Then I created an indexer to map all of the content and provide search functionality. When it builds the index, it follows each entry's links two steps out, so a character carries the names of its film's director and cast. Characters, places, things and vehicles also take the genre, era and tone of the films and books they're in, so you can filter characters by genre.

The indexer's test page: Nolan in the search box, Character chosen under Type and plus Sci Fi under Genre, beside 26 results that start with The Protagonist, Peter Browning, Mal Cobb and Maurice Fischer, each tagged Sci Fi.

The indexer's test page. Nolan, characters only, and + Sci Fi, a genre the characters take from their films.

Tough calls

Six calls shaped the build.

  • Fix entries, don't regenerate.

    When generated links came out wrong, I wrote a small script for each kind of error. Generating again would have cost more and brought new errors.

  • Only some entries inherit.

    Characters, things, vehicles and places take genre, era and tone from films and books. Nothing else does, or every entry would get every genre.

  • No buttons for filter states.

    A chosen filter changes state when you click it, instead of carrying three controls of its own.

  • The smaller model.

    I compared two OpenAI models' entries side by side and built the content on the smaller one, for efficiency and cost.

  • New content.

    Deliberately chose to not use the original content it was designed against.

  • A chat panel.

    I built one that turned a sentence into a search, or answered questions about the results. I cut it because it didn't really serve the demonstration of filters.

The outcome

A design that never launched, working in five days.

The search I designed at Klue never launched while I was there.3 Five days after I started, it ran on nearly a thousand entries, every filter recounting as you choose, with no server behind it.1 All four repositories are public, so an engineer can read how it works, not a spec of it.6

Try the prototype

3.6k

links between entries.

915

entries, in ten kinds.

10

ms response times.

My take

Some designs are meant to move.

A filter that recounts as you choose is hard to explain in frames, and easy to show in a search you can use. These days, getting something working, comprehensive and rich outshines static design files.

Questions? Answers.

  • Is this Klue's search?

    It's the search design I led at Klue, built after I left, on my own content. No Klue data or code is in it. The Klue side is on the Search page.

  • Why films and books?

    They came from a list of films and books I'd read or watched. Each title brought its characters, places and things, with links between them for the index to follow.

  • Where did AI come in?

    In the content. From my prompts, an OpenAI model found the characters, places and things in each title, wrote each entry and added reference links. The chat panel used one too, and was left out.

  • Can I see the code?

    Yes. It's public on GitHub in four repositories, one for each part and one for the theme: content, indexer (the index), search (the interface) and theme.6

Next project

Clausage.

Your Claude limits, where you already look.

  1. Built 17 to 21 January 2026: the content repository's first commit is on 17 January, the interface's last snapshot (v5-cleanup) on 21 January.
  2. Characters, places, people, things, organizations, books, films, vehicles, franchises and companies, generated from dozens of titles. On 20 January a second script added one or two reference links to almost every entry.
  3. The Klue search redesign ran from October to December 2024. It had not launched when I left Klue in December 2025.
  4. Solo. Built on an OpenAI model, which wrote the entries and found the reference links from my prompts; React, Vite, Mantine, MiniSearch and Phosphor icons; and the typefaces Chivo and Chivo Mono.
  5. Picking a filter never empties the page. Changing a chosen filter's state can: ! empties it when every result left has that tag, and + when no result has that tag along with the other + filters in its category.
  6. github.com/traviskirton/search, /indexer, /content and /theme, public as of 19 October 2026.

Screens shown are the prototype on its own content: the same entries, results and counts the app gives.