Tailwind CSS

Hiki: a manga look on Tailwind 4

Hiki’s web app runs on Next.js 16 with Tailwind 4. On top sit 16 shadcn/ui components, themed in a Neubrutalism style: bold borders, offset shadows and a manga-inspired look that carries across the catalog, the marketplace and the store map. The components live in the project rather than in a package, so the team changes them like any other code.

Bridddge: a desktop app with its own identity

Bridddge is an Electron app for macOS, styled with Tailwind 3 and shadcn/ui. Its theme sets the corner radius to zero and uses a blue accent, so the same components read as Bridddge rather than as a stock kit. The tailwindcss-animate plugin adds the small animations.

Scout: a dashboard that shows a lot at once

Scout’s interface is Next.js 15 with Tailwind 4.1, and Radix primitives give it accessible building blocks. It packs a lot onto the screen: a seven-step setup wizard, a drag-and-drop Kanban pipeline, an analytics dashboard and a live log of every action the agent takes.

Why Tailwind

The styles sit in the markup, next to the component they belong to, so nothing is left over when a component goes. Only the classes a product uses reach the browser, and a new theme is a handful of tokens rather than a rewrite. That is how three very different products stay quick to change. This site, larch.ee, is styled with Tailwind 4 too.