January 17, 2026 | By Lou Kovacs, Freelance Consultant


← Read Part 1: The Aesthetics Racket


Tomorrow came faster than I expected. It always does when you've got a bad idea you can't shake.

I woke up with the question still circling my head like a vulture over roadkill: what if the users got to choose? Not the developers. Not the designers. Not the AI assistants with their carefully curated style prompts. The actual human beings on the other end of the screen.

I poured coffee. Black, no sugar. Like my design philosophy.

The Problem

Here's the thing about building interfaces for people: you're always guessing.

You pick your colors based on best practices and brand guidelines and whatever the latest trend piece on Medium says about the psychological impact of rounded corners. You choose a font that says "trustworthy but approachable" and hope nobody notices you've written "trustworthy but approachable" in your Figma notes.

And then some user with light sensitivity shows up, or someone who works night shifts and needs dark mode like oxygen, or just a regular human being who happens to hate the color blue. And suddenly all your careful aesthetic decisions are just... noise.

The UI Styles Library was built for creators. For the people making things. But I'd been ignoring the people consuming them.

That felt wrong.

The Solution

I built a theme picker.

Nothing fancy. Just a little palette icon sitting in the corner of the screen like a spare key under a doormat. Click it, and you get options. All those styles I'd been hoarding in the library, suddenly available to anyone who wanted them.

Brutalist Mono for the minimalists. Neon Cyberpunk for the ones who never stopped watching Blade Runner. Nordic Minimalism for people who own too many succulents. Digital Garden for— actually, I don't know who Digital Garden is for. People who miss Geocities, maybe.

The technical guts are simple enough:

  1. Backend proxy — The homepage talks to the AI Platform internally, fetching styles from the library. No direct API exposure. Security first, paranoia always.

  2. Theme service — Caches the styles so we're not hammering the database every time someone opens the picker. Five-minute TTL. Reasonable. Responsible.

  3. CSS variables — The whole site runs on custom properties now. --bg-color, --accent, --text-primary. Change those, and the entire interface shifts like stage lighting at the end of an act.

  4. LocalStorage — Your choice persists. Come back tomorrow, and the site remembers you. Remembers what you wanted. There's something almost touching about that, if you're sentimental.

The Magic

The first time I clicked Vaporwave Nostalgia and watched my entire homepage transform—the black background blooming into purple gradients, the cyan accents humming to life like neon tubes warming up—I understood something.

Control is a gift.

Not the illusion of control. Not "pick from these three approved options." Real control. The ability to say "I want this world to look different" and have it happen. Instantly. No permissions required. No forms to fill out. No design committee to consult.

Just you, your preferences, and a button.

The theme picker, sitting in the corner like a loaded gun. Thirty-something ways to see the same world differently.

Each theme card shows you what you're getting. Little color swatches like paint chips at a hardware store. Click one, and the whole site shifts. Click another. Keep clicking until it feels right.

What feels right is different for everyone. That's the whole point.

The Catch

There's always a catch as sure as the sun comes up.

Not every style translates perfectly. Some are built for forms and buttons, and they make blog posts look like ransom notes. Some have text contrast ratios that'd make an accessibility consultant break out in hives. Some are just weird—experiments I added at 2 AM that probably should've stayed in the drafts.

But that's the deal. You get to choose, which means you get to make bad choices. Freedom's like that. Comes with the price of occasionally picking something that makes your eyes hurt.

I could've curated harder. Could've limited the options to "safe" choices. Could've been a responsible adult about it.

But where's the fun in that?

The Revelation

Here's what I didn't expect: people like having options.

Revolutionary insight, I know. Somebody get me a TED talk.

But seriously—there's something about being able to customize your experience, even in small ways, that makes you feel less like a consumer and more like a collaborator. The site stops being something done to you and starts being something done with you.

That power differential matters. In a world where every platform wants to control every pixel of your attention, giving some of that control back feels almost subversive. Like slipping someone a key they didn't know they needed.

The Wrap

The theme picker is live. Bottom right corner—look for the palette icon. Probably twenty-something styles available, with more coming whenever I have another insomniac night and too much whiskey.

Pick one. Pick twenty. Pick none and stick with the defaults—that's a choice too.

The point isn't which theme you choose. The point is that you get to choose.

I finished my coffee and stared at the screen. A Neon Cyberpunk homepage stared back at me, all pinks and cyans and drop shadows that would've given my design professors heart palpitations.

It looked ridiculous.

It looked perfect.

I hit save and let the users decide for themselves.


Field notes compiled by Lou Kovacs. The theme picker is deployed and operational. Built with ASP.NET Core, some JavaScript that mostly works, and the radical notion that people should get to pick their own colors.

If you've made it this far, try clicking that palette icon. Go on. I dare you.