Ep 848: Context Engineering: How to Get Expert-Level Outputs From AI Chatbots (Start Here Series Vol 7)

Welcome to the Everyday AI Podcast. My name is Jordan Wilson, and for the past 3 and a half years, we've put out more than 800 episodes. Yet one of the most common questions I get, I didn't really have an answer for. Where do I start on the Everyday AI Podcast? And that's why we started the Start Here series. And with fall now back in full swing, the Everyday AI Podcast is going back to school and playing back the entire Start Here series. From front to back, we've hit pause on our normal Monday to Friday programming to run back our most popular series ever for the next 30 days. We made the Start Here series for beginners and AI champions alike. So whether you're just trying to get a grasp on large language models or grappling with the best coding harness for multi-agentic workflows, the Start Here series covers it all. Plain language, no jargon, and easy to follow along each day. So make sure to subscribe to the podcast and. check back each day for new insights day by day. The series is a culmination of spending more than 10,000 hours covering generative AI over the past 3 and a half years. So you don't want to miss a single episode of the Start Here series. Let's get into it. Why does no one talk about prompt engineering anymore? I mean, if you rewind back like 2 years ago, you would have sworn that prompt engineering would be the world's most popular future job title. But that's obviously not the case, and the essential disappearance of that term is twofold. One, models are smarter, and it doesn't always matter the exact way we talk to them as long as we get the message across. And 2, an output that moves the needle is much more dependent on business context versus just wording something a certain way. Hence the resurgence of the term context engineering. But what does that even mean? And how can you understand the required inputs of context engineering to get better outputs out of a large language model? Well, if that's one of the things that you or your business is grappling with, then you're in luck because on today's episode of our Start Here series, we're tackling context engineering and how to get expert-level outputs From AI chatbots. All right, I am excited for today's show. I hope you are too. If you're new here, welcome. This is the Everyday AI Start Here series. So after 700+ episodes, one of the most common questions I get is, where do I start? So that's why we started the Start Here series. And this is actually volume 7 of this exact series. So the Start Here series is the essential podcast series to both learn the AI basics and to double down on your knowledge. So if that's what you're trying to do, you're in luck. Make sure you go to starthearseries.com. That's going to redirect you and give you free access to our inner circle community. So there you can not only go take our context engineering course called Prime Prompt Polish for free, but also network with a bunch of other people. And you'll be redirected right to our Start Here series area where you can go and listen to every single episode in this series, all right there at your fingertips. All right. And if you missed our last episode of this series, we talked about how to train your team on AI and the 7 steps to educate your organization on large language models. And the last step in there was, well, making that step to go from operator to orchestrator. So that's where we kind of left you with the last step in our series. And that's where we're going to pick up because actually one of the biggest things that you can do from going from an operator or essentially someone pushing all the buttons to an orchestrator, right, which is when AI starts to do the work for you, is having the right data and providing that data to the model in the right way. And that is the backbone of what context engineering is. It is the process a human goes through to make sure a large language model has the right context about not just you, Your role, what you're trying to accomplish, but maybe most importantly, your business and the competitive market. So this is the big differentiator because the same 2 people, they can use the same prompt, right? Going back to, uh, prompting and prompt engineering, uh, and you can get wildly different answers, right? Because if one person, whether it's in custom instructions, a GPT, a project, et cetera, or, uh, using ChatGPT apps or, uh, you know, Claude, uh, connectors, whatever you may be using, Google Gemini apps, uh, right? You can put in the exact same prompt as someone sitting next to you. And if you have your context engineering 101 ducks in a row, your output will be light years better than that person who does not. And the difference isn't necessarily as difficult as it may sound because the skill separating average AI users from expert level ones is just providing the model the needed context and understanding how it works in different scenarios. So that's what we're going to cover today. We're going to, well, first talk about why the AI industry as a whole and really just the business landscape has shifted away from prompt engineering and really just more focusing on context engineering. And I will say that that shift kind of happened and popularized in late 2025. Then I'm going to lay out for you a 6-part framework and also a 4-layer system for structuring what your AI sees. And then I'm going to walk you through how to build Reusable context vaults, or kind of skills, one and the same, and use platform features that are already at your fingertips. All right, let's get into it. So RIP prompt engineering, right? Kind of, but here's the thing. If you think back to the early days of ChatGPT, or even technically before, ChatGPT, right? When the GPT technology was available to dozens and eventually hundreds of other platforms before ChatGPT even came out, right? So much of what you were able to get out of a model was how you talked to it. And that was for a couple of reasons. Number one, the AI models themselves were a little more old school, right? And I'll talk about that here in a little bit. You couldn't always upload documents. Right? And you couldn't always paste in a bunch of information either because the model's context windows were smaller. So essentially, it would always forget things very quickly. You couldn't, for the most part, upload documents, at least not very easily. Right? So this really changed that differentiator of if you were going to get a good output versus a bad output. And it was really just how you talk to the model. Right? If you use certain prompting techniques, you could kind of pull the best out of a model's training data, right? Because even if you think back to the way earlier days of large language models, they weren't connected to the internet, right? So they weren't connected to the internet. They didn't have tool calling, right? And for the most part, you couldn't even upload files, which is why in the earlier days, prompt engineering was actually really important because even in that dataset, right? And if you go back and listen to the earlier episodes of our Start Here series, we talk about training data and everything that goes into it. But for the most part, in the earlier days of ChatGPT and, you know, when Gemini was barred and, you know, early Copilot days, et cetera, it was really how you talked to the model because the model had so fewer capabilities, yet there was still a lot of information there, right? Even the early models like GPT-3 or GPT-3.5, uh, or, you know, the first, you know, version of Google Gemini. Even though we look back at those models now and we think, oh, they weren't very good, they were. You just really had to learn how to talk to it, right? So now you can go talk to any of today's smartest models and you don't even have to really put a sentence that makes sense, right? Sometimes I find myself, you know, if I'm not using voice dictation with models and I'm just, if, and if I'm just typing, right, I've become, and I'd probably program myself to know the models are so smart. You know, it's misspellings and I say the wrong thing and all these things, but I know in the end it doesn't matter because the today's models are so incredibly smart at understanding what I'm trying to say, right? Especially when I have personalization enabled, memory enabled, all of these other things. The actual words that I'm telling a model don't mean a ton now, right? That's how it is, but it isn't how it used to be because The prompt engineering used to focus on, you had to say things the exact right way, right? But if you did, what you could get was just a step change different than what you could get if you didn't word something the direct way. It was like you almost had a password that no one else had. And at the time, right, proper prompt engineering, it was an amazing skill to have. But right now, it doesn't matter as much. Right? You can have the best prompt engineering skills in the world, but if you don't have the context, it doesn't matter. And I think the industry really realized that the bottleneck was never about how we talked to the model. It was the information behind it. And I think that this shift really started to happen in probably mid-June of 2025. So, you know, 2 of the people that are kind of credited with popularizing this concept of context engineering were Shopify CEO Tobi Lütke, who just kind of called for the move from prompts to context. And then in the same month, former OpenAI co-founder Andrej Karpathy kind of endorsed that term publicly. And then in September, Anthropic even published a dedicated blog talking about moving from, moving away from this concept of prompt engineering. And I will just go ahead and say this, right? Not one of those, I told you so, but we've been teaching this concept of context engineering, even though I didn't call it that. I believe we started teaching it in late 2023. So yeah, we've, I've done more than, you know, 200, probably like 210 now live trainings on, you know, essentially prompting models, right? So even early on, right? I was teaching prompt engineering, but that really shifted in late 2023 and early 2024. You know, we kind of, you know, we have our Prime Prompt Polish course, but if you have taken it in the last 2 and a half, 3 years, you know that we started to teach this concept called Refine Q. And essentially that is context engineering at its core. So, you know, it's, it's, it's not a, a new concept, right? Because I've been teaching people this for a long time, but the term The terminology around context engineering, and it has really snowballed into more of a movement, has really picked up in the last year or so. And that's because it's about designing the environment and not just the question. So an easy way to think about this is to think of the AI, right? Think of that whatever large language model that you, that you're using as a processor, and the context window is its working memory. Okay? So context window, without getting too technical, that's like a hard drive, right? So in the same way, maybe you have a 1 terabyte hard drive, let's just say, right? If your hard drive's full and if you try to put more information, maybe fortunately a computer will stop you from doing that. A large language model will not. So once its quote unquote hard drive gets full, it's just going to delete the first file that you ever uploaded, right? So that's how a context window works with large language models, except you never really know when you are hitting that context window, right? So what this means is, well, your context becomes very important in understanding that working memory and how the large language models work specifically with your data, right? That's grasping the basics of context engineering, right? And it's a little different, right? So it's different depending, it does get a little convoluted depending on what large language model you're using. Right? As an example, if you're using GPT-5.2 versus GPT-5.2 Thinking versus if you're using GPT-5.2 Pro via the API. So it is, it is a little bit different. But essentially the concept of prompt engineering, it ends once you hit enter. And context engineering is an ongoing battle to make sure that your model or your session with a model has access to and can understand your business data. And there was a study from Intuition Labs last year that said that 40% of AI projects fail. And one of the reasons, or the main reasons why, is, well, it comes from poor context, and it's not actually the model. It's the model either, number one, not understanding what you want out of it, or number two, it just doesn't have that data that can be the differentiator. So here's why it matters. More than ever. Well, if you talk about the big 3 or the big 4, right? So ChatGPT, Anthropic's Claude, Google Gemini, and Microsoft Copilot. They, it used to be fairly hard aside from Copilot. It's always been more straightforward if you understand the tech and the permissions landscape inside Microsoft Windows. That's a whole nother story. But let's look at the other 3 with just ChatGPT, Claude and Gemini. I would say in early 2025, it was actually kind of difficult to use your company's data, right? You could even say, oh, well, Jordan, you know, there's been these things like GPTs where, you know, you could upload, you know, documents and have a specialized version of ChatGPT that had access to those documents. Yeah. But have you ever tested it? Have you ever run the needle in the haystack test on that GPT that has, right? People would just assume, oh, I'm going to, you know, upload a, you know, 500-page PDF into a GPT and then it knows everything about me and my company? No, absolutely not. Right? That means you didn't really understand, you know, how these models tokenize that information or access that information. But now it's much easier, right? Because these models by default can create searchable indexes of your files. So think of it like this way. In the same way, let's say you have a Mac. Right? And you can go to your Mac Finder and your search bar there, and you can search for maybe a word that is within a PDF, and it's gonna know because it's indexed that file and it understands it, right? That obviously requires a certain level of, of, of compute, right? That 2 years ago these models just didn't have, but now they do. So within ChatGPT, as an example, they have things like projects. They have things that were previously called connectors. Now they're called apps. Claude, same thing. You can have, you know, project-specific memory. You can have these reusable skills that can take advantage of your business context. Same thing with Google Gemini. You can have these gems that connect live to your Google Drive, to your Gmail, to your calendar, right? So at various levels and in different ways, the 3 main players within a couple of clicks only can connect to your, in many cases, your dynamic business data. It's not always dynamic, right? In some cases it is, and it will create a searchable and live indexed of everything that you connect to it. All right. Again, I have to throw out that same asterisk as I always do, you know, always make sure you have permission to connect your company's data to a large language model, blah, blah, blah. Right. But once you do, that is the first step in context engineering is making sure, number one, the model has access to the context or the data that it needs, but you also, more importantly, need to understand how it works in each scenario, right? Like, as an example, I would say most people, even if you listen to the show often, you might not know that ChatGPT had these things called connectors. But oh wait, actually in December they changed them right before the holiday season. They changed them all to apps and a lot of people missed that. And with that comes, uh, depending on what app you're talking about now, well, it maybe handles, um, your data a little bit differently than it did before. So you do have to, depending on the platform that you use, if you really want to understand context engineering, well, you have to understand how each of these different platforms connects to different data sources because it's not uniform, right? It's really not, right? Even if you look at ChatGPT, their apps, there's 4 different ways that it can look at your data in 4 different ways that it can understand your data. Right? In the same way, right? If you think of cloud storage and there's these different permissions and different ways to access data, you know, that does trickle down to large language models as well. So let's talk about kind of what I'm calling these 6 building blocks of effective AI context. Because the step 1 is, well, what I just covered. You have to make sure, depending on what large language model you're using, it has access to your data. But It's not just about data and it's not just about telling a large language model, here's something about me, right? That's providing context, right? Context clues. Tell me more about yourself, what you're trying to accomplish, right? I'd like to break it down into these 6 different building blocks for building context within a context window. Okay? Once you're out of the context window, again, depending on how you're connected, uh, connecting your data, um, you might start to get poor results. So keep this in mind and keep these 6 building blocks in the context window of, of any given conversation. So goal, that's what you need the AI to produce and for whom. Constraints, understanding the boundaries, rules, things to avoid, and format requirements. Reference material, that's the approved facts, data, and source documents to draw from. Examples, those are representative samples of the output you want, plus context and examples. Then procedures, those are step-by-step instructions for how the AI model should approach the task. Task, and then the evaluation rubric. So that's grading criteria so the AI can assess its own output quality. So this isn't a perfect formula, and it is ever-changing, right? But I think this is, for the most part, number one, you should just go take our, our free Prime Prompt Polish course and go through the whole thing. I think RefineQ is another version of building this essential Uh, building blocks of context, but this is another, um, kind of framework that I think works really well. Okay. Now you don't just think of those 6 building blocks of, okay, uh, I'm good, right? Let me get those things because you have to actually apply them in different layers. So the first layer is, well, personal. That's your own personal context. The second layer is Your team, right? If you're on a small team, might be a little less difference between that first layer and the second layer. If you're on a large team, could be a huge difference. Then the third layer is obviously your company or your business, right? So those are things like your brand voice, your policies, your product details, et cetera, uh, right? When we talk about layer one, that's your own personal role, your expertise, Right? Layer 2, that's kind of shared definitions, your project goals, conversations. Like I said, layer 3, that's at the company level, brand voice, policies, et cetera. And then number 4, that's your market. That's the, the, your position in a competitive market, industry invite insights, trends, et cetera. So it's not just about bringing the right folder in via a ChatGPT app. It's not just about those building blocks. It's also Making sure that you apply those at the different layers that a large language model needs. And then when you do that, you can probably imagine by now, oh my gosh, this sounds extremely time-consuming. Yeah, it is. Right? I always tell people, if you're thinking about AI as if it's an easy button, you're looking at it all the wrong way. Right? The best thing, the best analogy that I've probably ever taught, and it's from the very first, right, in early 2023 when I did my very first, uh, you know, ChatGPT prompting course back when prompt engineering actually was a thing. And it still holds true to today. When you are working with a large language model, you have to think of it as you are training a new employee, right? A new college grad or someone that just transferred in and they're a capable person, right? But their output is going to largely be dependent on how much context you share with them. Right? Because if you just throw down a giant prompt, right? If you throw down a giant training manual and then say, all right, first assignment's due in an hour, they're going to fail, right? You have to go through and give them the context and the conversation and the iteration that they need, right? And one of the ways that you can think about this, because what I just laid out in terms of, uh, you know, applying the context, okay, those 6 different building blocks across 4 different layers, that's a lot. Well, you have to think in the same way that you would invest in an employee. You do it so in the long run it is scalable, repeatable, reusable, right? So you can think of this as creating a context vault or maybe a skill, right? That's another terminology, another term, you know, kind of created by Anthropic. But skills have been picked up by, you know, all the main players in the AI space. So think of a vault or a skill as kind of this folder of reusable context, right? So these different procedures, rubrics, key facts that you might be able to reuse or to modularly use within each other. So you can build a skill or a vault per role to start, then expand that as your team standardizes whatever process you're working on. And the most important content to the vault first is how you do things, right? And that's before the knowledge ever leaves. So here's another thing people are always wondering. Okay, do I just paste this in? Do I upload this, um, you know, in a, in a Google Doc? Should I save this as a, you know, as an example, if you're using Collage, should I, you know, save this as a skills markdown file, uh, right? And then use it throughout. And I'd hate to use, uh, An SEO answer, but it depends, right? It depends on a lot of things. It depends on what model you're using. It depends on the context window. It depends on, are you using something ultimately inside of a project, inside of a GPT, inside of a gem? Are you using it in a kind of quote unquote naked chat where it's not connected to one of those 3 things? And the answer, it does depend, but I think it's It's important to know, well, you can kind of make it work any way, right? As long as you have the right understanding of how all these models work. So an easy example of that is to go back to GPTs, right? Because a lot of people were under the assumption that you could just throw in a large PDF in a GPT and then at any point, well, okay, it has all my knowledge. Right? But people didn't understand that, hey, you would probably have to, number one, in the custom instructions, you would have to kind of provide a, especially for larger and longer documents, you would have to provide kind of like a, an index, right? For how the model should treat that really long document. Or if you uploaded a handful of documents, you would have to have some simple rules like, hey, if This happens, then do that, right? If the user asks about marketing guidelines, you should check in, you know, page 5 of document A and page 9 of document B, right? So sometimes you can just upload static contexts. Sometimes you can just do the copy and paste method. Sometimes if a certain, you know, app or connector syncs dynamically, That can solve a lot of your issues, right? You always still have to do the good old human in the loop stuff, right? And make sure that you're always testing these things and scoping them and measuring them and, you know, making sure the models are properly connecting and pulling out the context that's needed. Because the other thing is, well, models are always changing. Behavior can be extremely finicky in a large language model, right? Taken from someone that's done dozens, if not more than 100 live demos on this podcast. Things can go terribly awry, right? You can run the exact same quote unquote prompt, even if you have your context near context engineering all the exact same, and it can go in a different direction. That is the, the source of generative AI. It is generative. It is non-deterministic. So you do have to still understand the different ways that you can bring that context in, whether it's paste, you know, pasted context, as long as you understand the context window. And again, you should always be looking at the chain of thought as well. And that's another big thing too. When we talk about why prompt engineering is all but dead, right? Well, chain of thought was a very popular prompting technique, right? And this was essentially a way that you could kind of go through this process. Of walking the model through how a human would think. This is the chain of thought or how a smart human would go about, you know, getting this proper answer. And you would kind of think of, okay, here's how a smart expert would go about getting an answer. And then you would have to deconstruct that and kind of reverse engineer that to a large language model. And that would be called a chain of thought prompting technique. But that was kind of when we just had these quote unquote old school transformer models, right? That scenario that I painted for you earlier when the models weren't connected to the internet, when you couldn't upload files, when they weren't dynamically connected to your data, right? When they didn't have tool calling and all of these different functions, right? That's when this kind of chain of thought, really prompt engineering mattered, right? But now this is the default of how today's thinking or hybrid models work, right? If you ever read the summarized chain of thought, you'll see, oh, this is essentially They're doing this prompt engineering stuff that was popular in 2023 by default. They're doing this under the hood, right? Which is why how you talk to a model is way less important now than having the correct context. So here's 3 techniques that I think can, uh, help you turn good context into expert-level outputs. All right. And these are technically still going back to prompt engineering basics. So yes, prompt engineering stacked with proper context is obviously going to give you the best results. So it's not that prompt engineering is dead, you know, still some of its, you know, core, you know, core foundations move, live on. So few-shot examples. Number 1, you should still, even with all that context, give it the examples of What's good, what's bad, right? That's what we teach in our Prime Prompt Polish. Uh, that is the polish portion is giving it kind of that, uh, multi-shot, uh, kind of, um, work, right? In the same way, think you're training, you're training that employee. Go back to that analogy that still works so well. The very first time they hand in their first project, their first assignment, their first deliverable, you're probably gonna go through and sit with them and say, hey, This is great because blank. Hey, this is incorrect because blank, right? So same thing, that's the, you know, few-shot examples. Uh, the second one, uh, the second technique is rubric first. So give, you know, whatever large language model that you're working with a grading criteria in the context window before you even start working, right? Uh, this is something again that we used to teach in our older PPP Pro course. Uh, we don't teach it as much anymore because I don't think it's as useful as it once was, but I think it's still, right? I called it, you know, temperature. I think I called it, no, gauges, right? You need to give the model something it can gauge or give it a temperature, right? And give it examples too. So say, hey, let's just talk about creative writing, right? Write a sentence as, you know, plainly as possible, as boring as possible. And you say, this is a 1, right? On the creative scale. You write a sentence that's kind of creative, this is a 5. Write the world's most creative sentence ever, that's a 10. But tell the model that, tell it why, right? And then there you go. You've just kind of created a rubric, right? So then at any point you can say, hey, let's do this as a 3. Hey, let's do this as an 8, right? Uh, and that can help you think of not just creative writing. That's just an easy one, uh, to think about, but, uh, there's so many different gauges or temperatures that you can put into a model. And then last but not least, show, don't tell. So sometimes you just need to paste the exact format you want instead of describing it. I think the combination of describing what you want and then also giving it examples, you know, that's just another, you know, kind of piling on here or doubling up here on our first technique, which is few-shot examples. But if you combine that with the kind of the show, don't tell, I think that's a great way, especially if you want outputs formatted in a certain way or if you want outputs to always include You know, XYZ, uh, just giving it examples of that is helpful, but then also giving it the exact formula, uh, right? So I would always do multiple, uh, versions, uh, of this, but the show, don't tell is extremely important. All right. So we've covered a lot in this Start Here series, but let me wrap by saying this. Context is everything, right? I've always said your data is the differentiator. Using AI doesn't matter, right? It doesn't. People always think like, oh, we're using AI, so we're ahead of the curve. No, you're not. Right? And prompt engineering doesn't matter as much anymore, right? Because now These models by default are doing a lot of that heavy lifting that really paid off in 2023 and early 2024. So you have to stop thinking about talking to the model a certain way. And actually, especially if you are non-technical, especially if you're not a, you know, heavy AI user, that's actually a good thing because I think earlier on, Right? In 2023 and 2024, a lot of non-technical people were kind of scared off of using, you know, large language models. 'Cause, you know, earlier on there, you know, this prompt engineering, it's everything, it's everything, it's everything. And people are like, oh, I'm not an engineer, right? It doesn't matter anymore. You don't have to, you know, understand, you know, chain of thought or, you know, any of these other prompting techniques anymore. You can talk to it just Even like a lazy human, because if you have the context side, how you talk to the model is not as important. But let me just give you 3 last pieces of advice to wrap up everything we've talked about. So stop starting with a question. Instead, start with a tiny context pack. Extend on it from there. Next, reuse what works, right? Whether you want to create skills, Create GPTs, create projects. It doesn't matter, but you need to reuse what works because you do need to put much more in on the front end, on the context side, than you think you might need. More and more and more context. As long as you understand and don't exceed the context window, context will not bite you in the butt, right? It will bite you in the butt if you don't provide enough context, but you need to be smart and think in a scalable fashion. And you need to reuse what works. And then last but not least, remember that expert level results come from a system that you can repeat every time, right? It's all about if you want the expert level outputs, there's a good chance if you're doing this the right way that you're wasting time by not reusing it, right? Here's a, here's an extra pro tip. Right? Especially if you're using as an example, well, any of the models, if you have personalization and memory on, go through, ask the model, what are the things that I'm most, that I'm using you for that is most repetitive? You know, what are some systems that I can build that I can reuse, right? You'll probably be surprised, especially, you know, there's been some recent updates in the last, I'd say 3 to 4 months. With the big 3 players there in improving how the memory, how, you know, remembering your past chat conversations. It's actually really good now, right? When it first started to debut like 15, 18 months ago, it wasn't that good, right? But I'll say the last 3 months, these AI chatbots, essentially their memory and what they know about you is really good in being able to recall past conversations. So just ask, what am I wasting the most time on? Right? Doing every single day. What are some skills that I should be building? What are some projects that I should be, you know, building? What are GPTs that I should be using? Right? Don't never, never feel like you're, you know, stupid or anything by just saying to a large language model, I'm not sure. Because guess what? Large language models are smarter than us. They are. They can pick up those, those little pieces that humans tend to miss or even things that you may miss about yourself. So actually a great way to fill in that context is just to ask a large language model, right? There's kind of this more, you know, popular, you know, trend of creating like a skills markdown file or a role markdown file. Ask any of the models, hey, based on everything you know about me, Help me build out some of these blocks that you can then use modularly and take them with you as well, right? Because I can guarantee, and I've gone through this process, I actually did it like 1 or 2 months ago where I just went through that process in all of the models because chances are I use them for different things because they each have their different strengths. And then I combine them into one big, you know, skills file, role file, all these different things. And now I have these building blocks that I can use whenever I need them. All right. So that is how you get those expert-level results. So I hope that this version of the Start Here series was helpful. If it was, make sure if you haven't already, go to starthearseries.com. That is going to give you free access to not just our context engineering course that's been taken by more than 15,000 business leaders called Prime Prompt Polish, but it is going to give you free access to our Inner Circle community. And then you can also go to the Start Here series, uh, space inside of our community and go listen to and catch up on all of our Start Here series all in one easy place. All right. I hope this was helpful. Thank you for tuning in. I hope to see you back tomorrow and every day for more Everyday AI. Thanks, y'all. And that's a wrap for today's edition of Everyday AI. Thanks for joining us. If you enjoyed this episode, please subscribe and leave us a rating. It helps keep us going. For a little more AI magic, visit youreverydayai.com and sign up to our daily newsletter so you don't get left behind. Go break some barriers and we'll see you next time.