before using spec-driven development or vibe coding or anything in between. We have to You have to be careful with context. Now, I told you before that spec-driven development gives you a lot of context that gets fed into that large language model, but sometimes you have too much of a good thing. Uh what you need to do is when you are working with these large language models, usually you create like an agents.md or claw.md at the beginning with some information in it. I would be very careful not to put too much information or too little information in that. Kind of like that Goldilocks zone of information is what you need. So, you just need to give it enough rules and guidelines that it knows what to do. Uh we call it steering docs in Cara, which I'll mention about in a minute, but you just got to be very careful what you put in those documents. I also highly recommend when you're using spec-driven development to use skills. Skills are like instruction files that you can give to your coding agents that are ran on demand. So, usually they have keywords in them, and when the coding assistant sees those keywords, they'll activate the skill or you can do {slash} and the skill name and then run it. But, this actually really helps when you're doing the spec-driven development process. You can actually add skills um when it creates your design documents or whatever else. You can use those in parallel or with the spec-driven development or when you actually