Before you let 10 agents simultaneously rip through your code base, you need to get your house in order.

Today on syntax, we're talking about the eight things that you need to lock in before agent

maxing. And now, this isn't just about AI and agencies are going to be useful in any project, the things and

choices that you need to make and understand why you're making them before you get to

actually coding or before you put the machine on the code. My name is Scott Tolensky. I'm a developer

from Denver as well as always is Wes Boss. What's up, Wes? Yes.

This is so important because, like, I think it's made worse with agents because it's so easy

just to start ripping and making a mess.

But this is a good choice for absolutely any project is slow down for five minutes,

make some good decisions as to what, like like a good base of your project is going

to be. We're going to talk about like schemas and validation and CSS methodologies,

component frameworks, routing structure, all these types of things. Because if you can put a

good base in place first, then the rest of your agent maxing is going to be a lot better.

You're not going to absolutely make a mess.

And this is not about like make sure you decide on like a specific validation framework and make

sure that you do X, Y, and Z because moving laterally from these things is actually not a big deal.

It's very easy to do with AI if you decide, you know what?

I'm moving from React to Svelt.

That surprisingly is not that big of a deal anymore.

But things like extremely messy database, a schema that is absolutely all over the place, you know,

tables that have been added, flags that are unnecessary, old functionality that hasn't been

cleaned up, those are the types of things that are going to make an absolute mess of your

...