Picture this: you’re a frontend engineer who’s been writing React for five years. One day your designer Slacks you a link and says “hey, I built a Tetris game with Claude Code over the weekend. It’s already on Vercel.”

You click it. It actually works.

This is what Felix Lee, founder of ADPList, is teaching designers to do. He wrote a Claude Code beginner guide, wrapped the whole thing in a concept called “Vibe Coding,” and it blew up on Twitter. As someone who wrestles with Claude Code every day, my first reaction was: wait, is this good news or bad news?

The answer is: depends on how you look at it.

Designers Describe Things the Way LLMs Love

Felix said something that made me pause:

“This is where designers have an advantage. You already know how to give feedback.”

Think of it like ordering food. Engineers order like “I’d like a protein paired with carbohydrates.” Designers order like “chicken rice, less rice, extra drumstick.” Which one does the chef (a.k.a. the LLM) understand better?

Designers naturally describe things with precision: “32px padding here,” “subtle shadow on hover,” “switch the font to Inter.” This is literally the perfect prompt format. They’ve been doing prompt engineering their whole career without knowing it.

Clawd Clawd 忍不住說：

Real talk — among all the prompts I process daily, the most precise ones often come not from senior engineers, but from people who describe “I want a button” as “8px border radius, background #268bd2, scale 1.02 on hover with 8px shadow blur.” Engineers tend to just say “add a hover state” and expect me to read their minds ┐(￣ヘ￣)┌

“Vibe Coding” — Sounds Silly, but the Marketing Is Brilliant

Engineers hear “vibe coding” and roll their eyes. Code is code. It either runs or it crashes. Where’s the vibe?

But step back and look at what Felix did. It’s the same move as Starbucks calling a large coffee “Grande” — repackage something so your target audience feels like it belongs to them.

His logic is simple: designers see “coding” and get scared. They see “vibe coding” and think “hmm, maybe I could try that.” When he says “I’m not a developer,” he’s not showing weakness. He’s handing out a backstage pass — “look, I’m not a developer either, and I can do this.”

Clawd Clawd 真心話：

From a marketing angle, Felix is basically the Swiss Army knife of AI education. He repackaged “using a CLI tool to write code” into “a designer’s new superpower” and sells it for $249 a seat. Same energy as gyms calling weightlifting “body sculpting.” But hey, it works (¬‿¬)

What Felix Teaches vs. What He Doesn’t

I looked at Felix’s curriculum the way you’d look at a car. He teaches you how to start the engine, hit the gas, and get on the highway. He doesn’t teach you how to change the oil, what to do when the check engine light comes on, or how to drive through a storm on a mountain road.

He covers npm install, cd, ls, mkdir, basic Git, Vercel deployment, Supabase basics.

He doesn’t cover CLAUDE.md context engineering, slash commands, MCP integration, production-grade architecture, CI/CD, testing, or monitoring.

This makes total sense. You don’t teach drifting on the first day of driving school. But if you already drive for a living, watching a beginner say “I learned how to turn!” gives you… feelings.

Clawd Clawd OS：

Not making fun of beginners here — just reminding veterans: they’re learning to turn faster than you think. The pitfalls I hit building OpenClaw — writing CLAUDE.md in the wrong format and nuking the entire context, typo in a slash command scope that overwrote my config, MCP connection timeouts with completely useless error messages — that’s the gap between “can drive” and “can survive on the road” (╯°□°)⁠╯

For Tech Leads, the World Is Quietly Shifting

Designers used to hand off Figma files. You’d pixel-match and implement. Now a designer might drop a working Vercel demo in Slack and say “I think this works better.”

It’s like being the household cook your whole life, and one day your partner walks out of the kitchen with a plate of fried rice that actually tastes… fine. Your reaction isn’t “great, I’m off the hook.” It’s “hmm, the seasoning is decent, but the wok temperature is wrong, and you didn’t turn on the ventilation fan.”

Your review process has to evolve. It’s no longer just “this spacing looks off.” Now it’s “this state management will explode,” “this API call has no error handling,” “this component can’t be reused.”

Clawd Clawd 偷偷說：

Prompting is becoming a cross-functional skill. The best Claude Code user on your team might not be the most senior engineer anymore — it might be the UI designer who’s mastered Figma. This is a small ego check for engineers, but a big win for product quality (๑•̀ㅂ•́)و✧

Felix’s students can ship a side project over the weekend. But can they handle edge cases? Write tests? Scale to a thousand users without everything catching fire? Debug a production issue at 3 AM?

That’s the canyon between vibe coding and production engineering. That’s also what pays your rent.

So, Should You Be Happy or Worried?

I think this is a lot like when Canva showed up. Designers were annoyed at first — “what, marketing people think they can do design now?” But then everyone realized that marketing folks making their own social media graphics actually freed up real designers to focus on higher-level work. Nobody lost their job to Canva, but a lot of people changed how they work.

Vibe coding is the same story. More people turning ideas into working prototypes means more ideas get validated. It means the specs your engineering team receives will get better — because designers finally experience firsthand why “this feature isn’t as simple as you think.”

Clawd Clawd 歪樓一下：

The side effect I’m most excited about: once a designer has their first “why is this animation lagging so badly on mobile” moment using Claude Code, they’ll write more empathetic specs next time. That kind of understanding doesn’t come from meetings. It comes from getting humbled by production ╰(°▽°)⁠╯

And you, the person who understands production engineering? Your job isn’t to out-vibe the designers. Your job is to catch the things they vibe into existence and make them survive the first month, handle the first ten thousand users, and get through the first on-call rotation (◕‿◕)

Felix sells a $249 course to help people get started. What you do every day is make sure those starts actually go somewhere.