Will society accept me as a designer (vibe-coded) if I don't have a vibe-coded component library?

Something strange has been happening on my timeline for the last few months. People who were shipping "I built a SaaS in a weekend" tweets six months ago are now calling themselves product designers. Not developers who use AI. Not indie hackers. Designers.

And if you look at what they are actually shipping, it is always one of two palettes. Either it is #000000, #181818, #ffffff, #efefef - the "minimal dark" starter pack - or the exact same thing in reverse. That is the whole design language for an entire generation of self-declared designers right now. Two themes, infinite founders.

The Two Archetypes

Toggle between the two themes below to see the exact formula shipped in hundreds of $99 component kits:

I do not think this is a coincidence, and I do not think it is really about design at all.

The Question I Keep Asking Myself

I do not have a component library. I never forked shadcn, never reskinned it, never put a price tag on a weekend of border-radius tweaks. And somewhere in the back of my head there is this nagging question: does that mean I do not count? Is that the entry ticket now? Do I need a $99 kit with my name on it before anyone on X treats me like a real vibe-coded designer?

I do not think it should be. But I also cannot pretend the pressure is not real, because right now that is the signal everyone is reading. No kit, no credibility. Ship a library, get the badge. It is starting to feel less like "did you design something good" and more like "did you produce the artifact that proves you are in the club."

That is the actual anxiety underneath this whole post. Not "is this trend annoying" - it clearly is - but "am I going to be judged by a checklist that has nothing to do with whether I can actually design."

The Five-Step Pipeline

Here is the pattern, and if you have spent any time on X in this niche, you have seen it too:

1. Vibe-code an app. Get some traction, a few thousand impressions, maybe a viral screenshot of a glowing dark card.
2. Update the bio. Somewhere in that process, start posting "building in public" content, and quietly add the word designer to your bio.
3. Fork a library. Look for an open-source component library already tested and used by thousands. shadcn/ui is the universal default.
4. Change four tokens. Tweak the border radius, invert the surface hex codes, and rename it to something ending in "UI" or "Kit".
5. Attach the price tag. Put a $99 to $150 price tag on Gumroad or Lemon Squeezy and announce your "independent design system."

The Anatomy of a $99 Kit

If you diff the repository of a typical $99 vibe kit against the open-source library it was forked from, you usually find four changes:

:root {
  --background: #000000;
  --foreground: #ffffff;
  --card: #181818;
  --radius: 8px;
}

That is the entire scope of modification. The underlying component state machines, ARIA tree, event listeners, and DOM structure are unchanged.

The Part That Actually Bothers Me

Here is what I keep coming back to. Somewhere, right now, there is a design systems team at an actual company - people with years of experience - who have spent months getting one single component right. Not "it looks fine," but genuinely right: accessible, consistent across a hundred edge cases, tested against real users, and documented so the next fifty engineers who touch it do not break it.

And then someone ships a reskinned fork of an existing library in 48 hours and treats it like they just did the same job, just faster, because they had AI and the other team apparently did not.

Changing a border-radius token and a background color is not the hard part of a component library. It never was. The hard part is everything invisible - state management, accessibility, composability, how a button behaves when it is inside a modal inside a drawer on a phone with a screen reader on. AI models are extremely good at the visible 10%. They are not doing the other 90%, and the people selling these kits mostly are not either, because they do not know it exists yet.

What This Is Actually About

This is not really a design movement. It is a personal branding move wearing a design costume.

"Designer" carries weight. It signals taste, judgment, years of caring about details nobody else notices. "I vibe coded an app" signals something else - speed, hustle, maybe luck. Calling yourself a designer after prompting a model to restyle an open source repo borrows credibility it has not earned yet. And because the aesthetic is so narrow - those same four hex codes, that same "confidently minimal" look - it is easy to pattern-match into "clean, considered, professional" even when nothing about the process was actually considered.

The pricing gives it away too. $100+ for something built in two days is not priced like a product. It is priced like a badge. The buyer is not really buying a component library - plenty of better ones are free. They are buying proximity to whoever built it, and the promise that they too can ship something that looks like a real design system by the weekend.

Frequently Asked Questions

Where This Leaves the Conversation

None of this means AI-assisted design work is fake, or that everyone doing it is grifting. Plenty of people are using these tools honestly, learning fast, and getting genuinely better at design because the feedback loop is so much shorter now. That is a real and good thing.

But there is a difference between "AI let me learn design faster" and "I forked an existing library, changed two CSS variables, and now I am a designer selling design systems." One is a skill. The other is a costume with a price tag on it.

So to answer my own question: no, I do not think society - or this industry, or whatever we are calling the timeline - should require a reskinned component library before it accepts someone as a designer. If that is the bar, the bar is broken. I would rather be the person without the kit than the person who thinks changing four hex codes over a weekend earned the title.