What is Spotmind?

Spotmind is three things that prove each other. The Kit is a copy-in frontend library: component styles, hooks, utilities, patterns and themes, MIT licensed, no package to install. The apps are the proof: they run side by side here on real, current data, built with the very pieces the Kit holds. And the devlog is the record of how. When a feed has nothing to show, the page says so; there are no placeholder numbers anywhere on this site.

The Kit grew out of an internal library that mined finished projects for the pieces that proved themselves. That workshop now lives here in the open, and it grows both ways: new pieces get mined from shipped apps (marked Shipped), and new experiments get designed for the library first (marked Lab) so future projects can start from them. Agents and tooling are first-class visitors: llms.txt and registry.json expose the whole library, sources included.

The devlog is the other half. I keep detailed build records for every project: decisions, bugs, measurements, dead ends. The devlog turns the best of those records into proper write-ups. If a number appears in a story, it was measured; if a bug is described, it actually happened to me.

The projects

• World Cup 26 (worldcup.spotmind.app): Every fixture, group and knockout of the 2026 World Cup: live scores, line-ups, derived momentum and a real-time match centre, built on a free public feed.
• F1Peak: Live track map with moving cars, timing tower, replay and telemetry analytics. The circuit itself is derived from nothing but the cars' GPS positions.
• ZQ Engine: An Electron kernel that starts, supervises and surfaces every local project from one manifest, including a live wallpaper layer rendered behind the Windows desktop icons.
• TrackSpot (tracks.spotmind.app): Record lap times across players, vehicles and categories, and keep a running picture of who is quickest, where.

On air means publicly reachable. In the lab means it runs on my machine, usually because something real is in the way (F1Peak, for example, cannot be hosted: the live feed rejects requests from datacenter IPs).

How it's built

The stack is mostly Next.js and TypeScript, with Fastify, Electron and three.js where a project calls for them. This site has no backend and no database of its own; it reads each app's public feed on the server and renders what comes back, exactly as received.

I work with AI coding agents as part of the process, and the build records are honest about which parts they carried. The rule that matters doesn't change either way: everything that ships gets verified against real data before it is called done.

Who

Spotmind is built and written by John Bruno. Questions, ideas or problems: email contact@spotmind.app or use the contact page.