Welcome to Syntax today. We got a pot-lock episode. That's where you bring the questions. We bring

the answers. I've got some really good questions today. Why does AI suck so much at CSS? How are we

supposed to get good, clean, repeatable design out of using an LLM? So questions around vibe rules,

skills versus rules versus agents. Should these rules be shipped with a package or should you just

reach out to the internet to grab them? Interviewing with AI, a genius, genius use of using a

dumb model from Brendan Falk. We're going to describe his thoughts on that, which I thought it was so,

so genius. How to define and debug performance

issues in your application. There's so many different spots where your app can start to feel

slow. And then finally, question from someone says, why isn't software getting better and faster

with AI? Isn't that what we were promised? Let's get into it. What's up, Scott? You want to hit us with the first

question? Yeah, first question from Yergan. Do you have any workflow suggestions for design and

CSS when working with AI agenetic coding? I'm currently experimenting with open spec plus

clod code and targeted system prompts for roles,

and it's great at functionality, but the design looks terrible.

I have started a new experiment with new system prompts for UX design

and opinionated front-end dev persona, but I'm wondering how other people are tackling this.

Is CSS without a rigid design system just too difficult for LLMs?

I will say this, Juergen, even with a rigid design system, AI sucks at CSS.

It's a perfect storm, if you will, of things that AI does poorly.

AI loves to just solve a problem locally instead of solving a problem globally.

It just likes to patch and throw things in there even when you explicitly tell it not to.

And with CSS, that often means just throwing just a bunch of bloated additional one-off

...