After some questionable vibe coding, I made this

Szymon Wolak — Wed, 11 Mar 2026 23:59:26 +0000

For the last few weeks I’ve been doing what I can only describe as low-conviction vibe coding.

First I made 3 npm packages.
Not terrible, not revolutionary, not needed.

Then I decided I was obviously ready for something bigger, so I tried making a procedural backrooms game in Three.js.

I restarted that project 3 times.

Each time I thought ok, this time I have the architecture, this time I know the generator, this time it won’t turn into a weird pile of rendering hacks and broken gameplay ideas.

It did. Every time.

So I gave up and made something smaller and dumber:
a browser game about surviving LinkedIn, recruiters, ghosting, and other white-collar psychic damage.

It’s basically a survivor-like, except instead of monsters you deal with things like recruiter spam, “seen”, other candidates, and general corporate nonsense.

Honestly this was supposed to be a joke project, but it ended up being way more doable than the backrooms thing because the scope is smaller and the joke carries half the weight.

Built it with Pixi + TypeScript.

The funniest part is that making the game itself was easier than getting the tone right.
The early versions looked too serious, then too abstract, then just bad in a boring way.
Only after leaning into a more goofy fake-pixel style did it start to feel like the actual idea.

Anyway, if you want to see the result of abandoning one bad idea and replacing it with another, it’s here: https://career-survivors.protohiro.com/

No roadmap, no deep meaning, no market validation.
Just a small game I managed to finish before restarting it 3 times.

I shipped two frontend libraries in one day using AI agents

Szymon Wolak — Fri, 27 Feb 2026 23:18:32 +0000

Today I ended up publishing two small libraries.

Wasn't really planned. I just wanted to try using AI agents seriously and see how far I could push it in one day.

By the evening both were on npm and GitHub, which still feels a bit strange.

These are the two things.

Effects

demo: https://libs.protohiro.com/effects/
https://github.com/protohiro-com/effects

npm install @protohiro/effects

This one is basically a collection of CSS effects for React.

Things like:

gradient borders

glow

noise overlays

The main thing I cared about was not adding extra DOM elements.

I always found it annoying when an effect meant wrapping components in extra divs. That tends to break layouts sooner or later.

So the idea here is just:

const ref = useGlowEffect({
  color: "#3b82f6",
  blur: 20
})

return <div ref={ref}>Card</div>

Nothing fancy really. Just reusable CSS packaged as hooks.

I mostly built it because I kept rewriting the same stuff in different projects.

CSS tokens extractor

https://github.com/protohiro-com/csstokens

npm install -g @protohiro/csstokens

This one is a CLI.

It scans a project and extracts design tokens.

Most projects kind of already have tokens, just not officially.

You usually see something like:

#3b82f6
#2563eb
#3b82f6
#111827

and spacing values like:

6px
8px
10px
12px

So the tool just scans the codebase and generates tokens from that.

Basic usage:

csstokens --profile strict

It generates:

raw-index.json
tokens.json
tokens.css
tokens.ts
report.md

It's still pretty simple right now. Mostly the first version that actually works.

The funny part is that I've never published anything on npm before.

I've been working as a frontend developer for years, but somehow I never pushed a library publicly. Plenty of internal tools, experiments and half-finished repos, but nothing that actually got released.

So today ended up being my first npm publish.

And somehow it turned into two packages instead of one.

I mainly wanted to see if I could go from idea → working library → npm in a single day. Turns out it's actually doable now.

DEV Community: Szymon Wolak

After some questionable vibe coding, I made this

I shipped two frontend libraries in one day using AI agents

Effects

CSS tokens extractor