I Built a FREE Blazor Starter Kit With Its Own AI Pair Programmer

Ajouté : 2026-05-05

[00:00:00]In this video, I'm giving you my complete runnable Blazer server starter kit that has vertical slice architecture, CQRS, mediator,.NET identity for authentication, a proper landing page, a working video game example library feature with full crud, and a few AI skills baked directly into the project. So, the moment you start building on it, the AI already knows exactly how your code base works. So, you don't have to do anything, just download, run, and build. Link is always in the video description below. But, if you want to know how everything works, just keep watching. And this is how it looks, right? When you open the folder, the Blazer AI starter kit after you downloaded it, and you open it in Visual Studio Code, which I can honestly recommend now with all the AI stuff, then this is what you get. This is the explorer here with the Blazer AI starter kit folder. And as you can see, I already have this one video and games feature in there with all crud operations. You have your commands, you have also your queries, right? With the corresponding handlers, everything is already there.

[00:01:12]And yes, this is built by AI, meaning exactly by this AI skill here, the vertical slice skill. So, what is my goal with that? You can just download it and already have a structure for a Blazer server application with Entity Framework using in-memory database, but maybe you see this skill here, add SQL Server Express. So, you can run this skill to add a SQL Server Express database, and this is pretty similar then to also a Postgres database if you want to use that.

[00:01:43]But, you also get the skill for vertical slice, you get the skill for building the corresponding UI. And what I like to do lately is using one skill to bump up the version. And this skill then not only bumps up the version, which uses the project file here with this version tag, right? It also updates the change log because it looks then at your Git comma commits, right? What happened since the last commit, and then writes your change log for you. So, this comes in pretty handy, in my opinion.

[00:02:22]But, let's just run this thing. And there we are. I zoomed into the screen, this is why everything is a bit bigger, but this is our landing page, right? And you can actually sign in or first register a new user. Let's do this real quick. We create the account, then we can go to the application. And again, the example entity here I have is the video game entity. And as you can see, we have a little dashboard here. We see some games already seeded. So, here now we can go to the library.

[00:02:55]We can search for games. We can also add a new game, of course. We can edit them, right? Maybe change the rating to 10.

[00:03:06]Save the changes, everything's fine. And we can also delete a game. So, everything is already there for you. You also have the settings here to change your email address, password, whatever it is you want to change.

[00:03:21]But, if you now want to know how this actually works at the code side of things, or the AI side, so you want to extend this application, maybe use or add a new entity and a new slice for movies, let's say, right? Then, let's go back to Visual Studio Code. As you can see again, we have a bunch of skills there.

[00:03:42]In this example now, I'm using Copilot to do that and run the skills. You can also use Claude, it doesn't really matter.

[00:03:49]Forward slash vertical slice, and there you also see this.

[00:03:54]It scaffolds a new vertical slice using CQRS for any entity you give this thing now, and let's add one movie entity and a new slice for that. It is doing its magic, it first reads the agents.md file, this markdown file, which is, if you already know that, in in essence, it's pretty similar or exactly the same thing as the Copilot instructions file, right? But, this is just it enables any interface you use to read it, right? It's not just for GitHub Copilot, it's also used by Claude, for instance. And this is why I used an agents.md file here instead of the Copilot instructions file. It created six to-dos for us. Read project conventions, right? Then, it will create the movie entity DTOs, then the use case slices, update all the database related stuff, and then just verify and build everything. All right, and we are finally done. We had a build error, but this is just because of a locked exe file, because the application was still running.

[00:05:03]But, now everything works, no compilation errors. And here you see what this thing did for us. It created a bunch of files regarding all the vertical slice stuff.

[00:05:12]Also, the database related things, and it now also tells us if you want the Blazer UI pages, we can just run the skill build UI, right? So, this is just amazing, in my opinion, because now we can see we have the movie entity and the slice exactly created the way we want it to be created, right? You can, of course, change the skill here when you have a quick look at the skill.md, and give this thing a bit more space so you can read it better. This is how this looks. We have a name for this thing and a description. And the description is what our LLM is looking for, right? So, when we write something that triggers this description, or it matches this description, then the skill will be triggered. And then it uses this whole documentation here to create the slice exactly the way it should be created.

[00:06:07]Now, you might ask, why not put this into the agents.md file, right? This would work as well.

[00:06:14]You're right, but this costs many, many tokens, right? So, in that case, if we, for instance, now only want to build the UI, and we would have the whole instructions for building vertical slice and the UI inside the agents.md, we would read the complete agents.md file, which costs lots more tokens, and tokens are getting more and more expensive, as you may already know. So, it makes sense to just put, say, project related general stuff into the agents.md file, and then everything else into separate skills. This is one big advantage of the skills. And the other one is that you have the structure, right? For repetitive work, like this thing here, and you still want it tidy, right? A clean code, and not one slice with, I don't know, folders for only the entity, and then another slice where you have folders for every single use case, then this makes sense as well. Anyway, I just want to show you we have our movie slice now here the way we want to have it. We also have it in the database.

[00:07:21]And now, I suggest we also run the build UI skill. So, build UI, there it is.

[00:07:27]Also for the movie entity, and now our UI will be built. All right, UI is done, as you can see, we got a bunch of new components or pages, right? And when we run this app now, as you can see, we also have now the movie library, right?

[00:07:45]So, here it is. We can, again, add a movie, we can uh go back, edit it, and so on. Now, the only thing left, really, is here the add SQL Server Express skill and the bump version skill. What I suggest you just download the whole package and try it out yourself. Works the same way. For instance, bump version here is the next skill. You don't have to enter anything here, you can just run this thing, and it will then update the version, and then decide for yourself, do you want to just push this to GitHub or already deploy it to Azure or whatever it is.

[00:08:26]Now, if you are a complete beginner with all that AI stuff, then I recommend watching this video next, because there I explain you in detail what this instructions or this.md file, this agents.md file here, is actually all about, right? Why do you need this thing?

[00:08:45]Watch this video, and you know.