What if your favorite coding agents could not just write code but truly understand your level application, your database structure, installed version, and other level tools at your disposal? Well, today I'm super excited to show exactly that with Laval Boost, a revolutionary new level package that transform how AI assist with your local development and your project. Think of it as giving your AI assistance a direct window into your Lavl application. So I'm going to install L boost into my artisans daily project which is a given project but you can of course install it in a new one as well. So what we have to do composer require larl boost as a dev dependency. All right. So this will bring in the level boost package. All right. Nice. And now we're going to install it with the boost install level command. Here we go. All right. And here we have to define a few things. First we need to tell boost which editor we are using. I'm going to use mainly cloud code here but it could be cursor and PHPtorm. I'm just keeping them selected in here as well so you can see what's going on. This is mainly for adding the MCP server which comes with boost. So the MCP server is very important. It's part of boost and it helps to bring a lot of tools into your AI um agents because they can use those tools and this will help you to so they can talk to your database, see the database structure, see application info, um see log files and many more things. Next to the editor, we also have to define our agent. For me, this will be cloud code as well. And this is important because this tells boost how to install our guidelines. and there are few that this package brings with. Okay, let's see what's going on here. We already get a little bit of output here. Very beautiful by the way. So, let's see what this is about. So, eight um guidelines were added to this project. So, we can see what do we have here. We're seeing level and version 12. So, boost already detected that I'm using level 12 and now we have guidelines for level 12 as well. And we have the level core as well which comes with every level project. And the same is with pest. We have pest core or tailwind CSS core and tailwind CSS vi4. Okay. So these were added to these coding agents as you can see. And you can see also the MCP servers installed into cloud code cursor and PHP storm juni. But I think it's a good idea to check out what has changed inside our application. What are the new files? What do they look like? And yeah, what was going on while we installed Boost. So let's bring this up in PHP Storm here and let's see what files have changed here. And we have five of them. So first the guidelines were added to this cloud MD file for yeah the cloud guidelines. Maybe let's take a look at this here directly because it looks a little bit nicer here. Yeah. So all right. So we can see here a lot is going on in this file. So these were the boost guidelines which were added to the cloud MD file so that cloud code um yeah can make use of them and we have a lot of general rules about um boost itself. Let's see what else do we got. We have the level core rules and it just makes sure to yeah tell your AI a little bit more about how we want to use level and that's the same for level. We have past insert here we have things about read. We have things about specially for level 12 and many more things. But if we scroll down here, you can see I have here something pulled in which are my own project guidelines. So this is something that I have defined in my own application here under my own folder AI guidelines project guidelines and it's a very simple one just to demo you what's going on. But lava boost did detect that inside this folder here under AI guidelines there is a plate file and yeah it just pulled this into the cloud and the other files as well. So this is now part of this file here as well of this summary of all the guidelines. And if we go back to see the files that were changing we have the same here for which looks like this and and the same for cursor. But you can also see we have here the two files about MCP for cursor and tuni. So for these um agents and editors we have to define the MCP server which comes with level boost like this. But for cloud code this is being enabled already directly. So we don't have a file directly for cloud code. But if you want to check out if it's still working and what's going on, we can do this by just opening up cloud code here. And we can take a look at the MCP servers which are installed. And you can see currently we have only level boost which comes from level boost of course. And if you take a closer look we have here the few tools section here where we can take a look at all the tools which are provided now through this MSP server through level boost. And there are a lot of very cool features here. So list specific um config keys errors um artisan commands database schema very important. So the I knows about the schema. We can give feedback to this um boost project back. Database query can directly um query our database and so much more. Application info. Search docs is very important. You get a very good documentation. Now when using cloud code through this MCP server and the search docs tool which is way better than letting cloud code find it somewhere else which is mostly outdated already. And yeah, there's a lot going on and very cool. And we're going to take a look at some of them. Oh, by the way, Tinker is also a nice tool so your AI agent can write some PHP code and test it out itself through Tinker or do something with your application directly because normally agents like Cloud Code just create a random file and then tries to run this PHP file and then maybe it forgets to delete it anymore. So this is not so much fun. This tinker tool is also very cool. Okay, so we've made sure that this MCP server was installed correctly, which is pretty cool. Okay, let's start now with some cool things and let's have some fun. So, if I take a look at this artisan's daily application in the browser, you can see we um don't see anything yet. So this is an application which shows you randomly some features from level and you can see we don't have any features yet but we don't know if there are just no features in the database or maybe is it something about the visibility of this feature. So yeah let's just ask cloud code do we have feature items in the database and let's see what's going on now. So you can see it's asking me about um accessing a tool which is called database schema and yes we allow this and yeah it shouldn't ask again about this. So yeah, it's you can already see that it's working that it's using some of the tools which comes through boost which is very cool and here's the next one which is about um curing your database and you can see here also the query select everything from the features table which is very cool and this will help you to get yeah better responses and them very fast. So in this case the table is empty so yeah nothing is in there. So maybe let's just add one. Can you please add a cool LL feature to database including category and code example? So every feature has a category and a code example. I'm fine now with just adding one to the database. And let's see what cloud code is now trying to do. Okay, there's already a list. Create a category, create a feature record, create a code example. But let's take a look how it now tries to do this. You can see it's already using the Tinker feature to create a category to create a feature and we will also use it now to create a code example. Yeah, you can just see it very briefly, but it shows you the code how it does this. And it's already done. We have a nice summary. And by the way, this works very much the same with cursor with Juny. Um, it just looks a little bit different, but yeah, they would now also use all these tools available through level boost. Okay, let's take a look. Let's refresh here. And yeah, we have something here. What do we have? Model factories. All right, let's take a look. So, it tells us about the feature how we can create a user factory. And then also how to use this, which is yeah, pretty cool. And you can see this is now working. And the nice thing here is that cloud code could easily check the database or create something in the database with the tools provided by LA boost. Okay. But I have also prepared a cedar. So please run the database so that we get some more examples into this application. And it's running now my cedar. And if we take a look now at all the features, you can see we have a lot of level features here which are shown on this list and on the homepage. We are going to randomly show one of them which yeah I think looks pretty nice and is very handy. Okay, but back to this list here. So if I take a look now at the debug bar, if you don't do notice is an application which you can install into your level application and which yeah gives you an overview of what's going on on your level apps. And here we can see one thing which maybe is not so good. We are querying um we have 42 queries here and a lot of duplicated ones. So it looks to me that we probably have an M plus1 issue here. All right. So let's ask cloud code about it. It looks like we have an N plus1 issue on the features page. What is the best solution to fix this automatically and globally in label 12 and as always it will start by creating a to-do list. And now it's trying to find out more about this N plus1 issue. It's taking a look at the routes which is also a tool from our MCP server. And then it's taking a look at the controller and the blade file. Okay. here and it found the M plus1 issue and now it's already using one of my favorite tools the search docs tool from boost. So this is connected to an API and gets the latest documentation from Laravel for the specific Laravel version which we're using here. And this results in way better results than what you would get without Laravel boost. Uh perfect. And it looks like it found the correct solution with one of my favorite new level 12 features, automatic eager loading. And it was also adding the prevent lazy loading method for non-production environment which I also think is a great solution. So let's add this. So let's cloud code add this to application. And I think it should be finished now in any second. Yeah, here we go. So let's take a look at our features page here. And if I open up the debug bar again, you can see yeah, we went down from 40 queries down to four, which is way better. Then we were also using a very cool solution with the new automatic eagle loading for models. All right. And here we can see the code which was added to our app service provider in order to fix our N plus1 issue. Okay. There are two more things that I want to show you. First, I'm going to my environment file and I'm going to remove the environment key. And if we now take a look at the browser, we can see an error because we need this application key in order to make our application work. Okay, if we see this, we notice we can fix this ourselves if we want to. But what about cloud code? So it looks like we have errors on our website. Can you check out what is going on? Okay, let's see what cloud code does now. So it first tries to read some of our other tools which we have. One of them is read our log entries. Yes, we allow this. And they already seized the application error. And it looks like it also found an application error. So, we're also providing tools here in order to check the browser locks as well. And it looks like it found an issue in our JavaScript, which is about our copy feature. So, let's take a look here. If we go down, we have this copy feature. Oh, yeah. It looks like it's broken. We don't see that it's working here. And if we take a look at our output, yeah, we see in JavaScript error before, which we didn't see because we didn't check it before, but gladly cloud code found it for us. And it looks like it fixed now both of these errors. Let's try this now again. And yeah, it looks like copying our code examples is working again. Okay, that's pretty cool because yeah, cloud code without the help of our tools, it wouldn't been able to find all the latest lock entries for the browser and the lava maybe it would try but yet still AI and often it would not succeed but the chance while you use level boost is way higher to get better results and also to fix those issues. Okay, there's just one more thing that I would like to show you. There's also a way to add feedback about boost here right through your agent. So you can just write it here. Hey, I like to give some feedback to level boost. Hey Ashley, which is the creator of this level package currently recording my video for your tool level boost. I absolutely love it. Emoji, great work and all the best for the release. All right, let's see what's going to happen now. It should find another tool which we have which is called report feedback. And yes, it does. And yes, we want to use it. And now Ashley will receive our lovely message. And yeah, I encourage you to also provide some feedback through your favorite coding agent. And yeah, this is how you can install and use label boost for your local development for your label application. And I hope I could show you all the different tool that make now working with AI agents like cloud code, like juni, like cursor way better than before. And I hope you will see better results as well. Well, I hope you're now as excited as I am about level boost and ready to give it a try. And of course, this is just the beginning. There's so much more planned for Boost in the future to make your level development even smoother. So check it out at github.com level/boost. And a big thank goes out to Ashley who poured his heart into this level, too. Make sure to send him some feedback, too. And have fun with boost.