# KIRO For Dummies: The Complete Beginner's Guide (Install → Build → Powers)

https://www.youtube.com/watch?v=a1EIi9BM3b0

[00:00] Hello guys, I'm Sudarshan Koirala and welcome back to Data Science Basics.
[00:03] In this video, let's go through Kiro.
[00:05] This Kiro for complete beginners or dummies, meaning that if you have never heard what is Kiro, then you will be able to know all these stuffs related to Kiro so that you don't need to watch any other videos.
[00:18] The main reason for creating this video is that now we have different AI coding platforms.
[00:25] And all of those might need some sort of technical background.
[00:28] But with the help of Kiro, if you have never used the AI coding platform, you will get it started.
[00:36] So, this is the topic that I'm going to cover.
[00:38] It is for complete beginners, but I will be first covering what is Kiro and then how you can install and download.
[00:46] I have uninstalled from my machine and I will be going to show you from my Mac OS, so you know the step to get started, the first time setup, how to do it, what is the interface or how does the interface looks like, stating.
[01:01] Files by versus this spec-driven coding, and this build to do applications, we'll build a simple applications.
[01:09] What is Agent Woo?
[01:10] What is the pricing for this Kiro?
[01:12] Problems and fixes.
[01:15] What sort of problems are people facing from it?
[01:17] The cheat sheet, how to get it started.
[01:20] I have the Kiro powers.
[01:22] These are the things I'll be covering.
[01:24] I have created this a step-by-step 12 steps guide, which I will be going through here.
[01:30] Step 1 to 12, which is the same steps that I have mentioned here.
[01:35] This is going to be a long video, and I will provide timestamps in the video, so you can quickly jump into specific sections that you want to watch.
[01:45] If you are into this, let's get it started.
[01:48] What is Kiro?
[01:50] Let's get from there.
[01:51] Kiro is an AI-powered code editor.
[01:54] Think of it like having a very smart assistant that writes code for you just by describing what you want in.
[02:02] Plain English.
[02:05] The big differences from other tools, Kiro makes a plan before writing any code.
[02:10] Most AI tools just write the code immediately.
[02:13] Kiro first ask, "What do you want to build?"
[02:16] "How should it work?"
[02:18] Then it codes.
[02:20] Nowadays, there are other platforms also which have planning mode, writing mode, but Kiro is really good to get it started for non-coders also.
[02:30] And because my friends at my workplace, they have built really good applications out of it as they were completely new to this AI coding tools.
[02:40] It was quite interesting to see how they have come up with the same things here, other AI tools and the Kiro.
[02:46] You describe what you want, Kiro writes a plan, you say yes no to the plan, Kiro writes the code and you get clean code plus documentations also alongside with it.
[02:57] And it is powered by the Claude AI models that are made by Anthropic.
[02:59] It is built on top of VS Code.
[03:02] It will look.
[03:05] Like VS Code, if you know VS Code.
[03:07] We will download it fresh.
[03:11] Let's go and see the website of Kiro.
[03:14] Let me double-check the next step.
[03:14] It's the download step.
[03:16] I can directly go to this kiro.downloads now here.
[03:20] I will click this one.
[03:23] Now it will take me to the website.
[03:25] This is this download for Kiro, but I will now first go to this official homepage first to show you.
[03:30] This is the homepage of Kiro.
[03:32] Agentic AI development from prototype to production.
[03:35] Kiro helps you do your best work with a spec-driven development.
[03:40] You can see different things mentioning how it works and so on.
[03:45] I will be showing you with a demo step-by-step.
[03:47] You can see on the top there is the CLI also.
[03:50] Now Kiro has CLI, but I don't expect you to know the CLI and other different agents because I'm making this video that you are completely new to Kiro and this AI coding platform.
[04:02] Here it says download for Mac OS.
[04:04] If you click this arrow here,
[04:06] It will say which one you want to download.
[04:08] This is Apple Silicon or is it Intel?
[04:11] To know this, you can go to the Mac OS on the top there is this icon.
[04:16] You can click about this Mac, and from here you can see which one it is.
[04:23] Here you can see Apple M3 Pro.
[04:26] For me, it is Apple Silicon.
[04:28] If it's Intel, check this Intel one.
[04:30] We'll go to this Apple Silicon.
[04:33] And once I do this, you can see now it is downloaded here.
[04:35] Now it is downloaded.
[04:37] I will click on this one.
[04:40] Once I click that, it will now show this window for me.
[04:42] I need to take this and drag it into the application.
[04:49] It says Kiro is damaged and can't be opened.
[04:51] You should move it to the bin.
[04:53] I will say move to bin.
[04:56] This is one thing that Kiro I have faced.
[04:59] When I download from this website and when I install it, it will throw me this error.
[05:05] The main reason of showing you this step-by-step
[05:07] Is about this.
[05:10] Now, if I go and type Kiro in my spotlight, you can see I don't have the Kiro.
[05:16] This you might face, but it's still we can open Kiro.
[05:19] But the idea is you are not able to go into this applications.
[05:21] This was the thing we faced during our workshop at work also, but now it happens here also.
[05:28] But just to show you here, what did we followed?
[05:30] Here is this Kiro in the Mac.
[05:33] You can see here, check your chip.
[05:35] It even says here about this Mac, download this Apple Silicon or Intel.
[05:40] Open the download DMG Kiro into the application and for the first time, right-click Kiro and open to bypass the security.
[05:49] If I go to the download again to the Kiro, click right-click and go to this open.
[05:56] If you go to Linux, you can follow the same steps.
[05:58] No AWS account is needed, just sign in with the Google or GitHub.
[06:02] We will go into that soon.
[06:05] But now, if I go to this Kiro again,
[06:07] I will go here and do open.
[06:10] Once I do this open, it will say, "Okay, this this this."
[06:13] Before opening the application, I will say open.
[06:18] Now this is the Kiro.
[06:21] Once I open this already, what happens if I now again go and do this?
[06:27] It says the first time for me.
[06:29] Let's see what happens here.
[06:30] Now it is copying to application.
[06:35] Any anything happen?
[06:36] No.
[06:38] I want to mention you that for the first time if you directly want to move this to applications, it will show you some error.
[06:44] This is just Mac-specific.
[06:46] But if you open this and go open for the first time and then it bypasses the security and so on.
[06:51] Now I will go to my spotlight search and now I will search here Kiro.
[06:56] Now you can see there is Kiro.
[06:57] First time it was not able to do it, but now we are able to do it.
[07:02] This is also one of the issue many are facing and know how to solve it, but now you get the point.
[07:06] I will go here and say.
[07:09] Kiro.
[07:09] I will open the Kiro.
[07:12] Now it will be the same UI.
[07:14] We did the second part also completed.
[07:17] Now we need to go to this first time setup.
[07:20] I will still go to the setup part.
[07:22] Let me go to third step here.
[07:22] It's quite simple.
[07:25] When you open the Kiro for the first time, follow these steps, sign in, import, allow the shell integrations, pick a theme, and so on.
[07:31] Non-responsive applications, it says here it's not responding.
[07:34] I will say here ignore for now.
[07:36] If I go here, now it's there.
[07:41] This is the first time.
[07:43] As it is mentioned here, you need to first sign in and pick a theme.
[07:45] We'll be following all this.
[07:47] There is also this bonus thing mentioned here because if you sign in for the first time, you will get 500 free credits.
[07:53] That is how Kiro provides you some credits and when you start using it, it will consume the credits, and then you need to buy the credits.
[08:02] I will show you in the UI how and where it looks like.
[08:06] Now I will go to this Kiro.
[08:08] So, I need to sign in.
[08:10] If I go to this sign in, now it is taking me to this new UI, which it says app.kiro.dev.
[08:19] It is asking me to sign in with different ways, Google, GitHub, builder ID, AWS builder ID, or your organizations.
[08:29] But for me, I will be going into GitHub.
[08:32] You need to have a GitHub account.
[08:35] I already have the GitHub account.
[08:36] This is my GitHub account.
[08:38] I will be using this.
[08:39] For you, if you don't have, you can create the GitHub account.
[08:42] It's quite easy.
[08:42] Then you can follow along with me.
[08:45] We will take you to this webpage.
[08:47] I'm already in the webpage.
[08:49] Sign in.
[08:50] It will ask me to authorize.
[08:52] Here it says you can close the window.
[08:54] Success, you are logged in.
[08:55] Let's get it started because I had already configured once with my GitHub before.
[09:01] For this demonstration, you will be seeing this icon.
[09:04] You need to approve.
[09:05] That's it.
[09:06] Now it is saying import the configurations because I have my VS Code installed in my machine.
[09:12] Now it is saying, "Do you want to migrate the extensions or the settings and key bindings?"
[09:18] I don't want to do that for now.
[09:18] Skip.
[09:21] Now it is saying choose your theme.
[09:21] Do you want to go with the light one or do you want to go with the dark one?
[09:27] I will go with the dark one.
[09:27] Continue.
[09:30] It says set up the shell.
[09:30] Shell meaning that this integrates Kiro with your shell and allows you to open any project from your terminal.
[09:37] In Mac OS, in Windows, in Linux, there is already a terminal there.
[09:41] It will integrate that in this Kiro.
[09:44] You can already go into the terminal and do things.
[09:49] I will say here set up set it up.
[09:52] And it says shell this this successfully installed in the path.
[09:54] This is good because it will automatically do the thing for you, so you don't need to configure things.
[10:00] Now I will say okay.
[10:03] So now this is the UI here.
[10:03] Unable to resolve your shell configuration.
[10:05] It is suggesting me to restart.
[10:07] I will just restart this.
[10:10] Now you can see Kiro is
[10:12] Restarting.
[10:13] And there you go.
[10:14] This is the Kiro this first time setup part is now done.
[10:19] Now let's go into the interface.
[10:22] I will again go to this documentations.
[10:25] We follow the same thing.
[10:27] We signed in first.
[10:27] Import VS Code optional.
[10:30] Allow the shell integration.
[10:32] Click allow when Kiro ask.
[10:35] This lets the AI run terminal commands for you automatically.
[10:37] And the Kiro dark or light we just did this.
[10:41] There are five areas which you need to be knowing.
[10:43] You can see I have explained here all the different things and there are even some shortcuts there.
[10:47] We let's open the Kiro again.
[10:50] You can see this is the Kiro.
[10:52] Now you see here on the left side it is showing us accounts.
[10:55] If I click this one, okay.
[10:58] You are connected to this GitHub account.
[11:01] You have credits expiring 12 days because I have configured this quite a time ago and I haven't used this.
[11:08] But for you it should be 30 days.
[11:12] I haven't used it that much.
[11:14] It is saying only two days because I was using with a different account.
[11:18] And now here it is saying 500 total left and this is the free version of it.
[11:23] And here it says Kiro free.
[11:25] And the credits as it goes the consumption bar goes here.
[11:30] And that's it.
[11:31] You can upgrade the plan from here.
[11:34] Let me go to the upgrade part later, but you get the point.
[11:36] Now you are connected to the GitHub and using this free Kiro.
[11:42] On the left side just to follow what I have written here.
[11:44] The activity bar is the thin column on the far left.
[11:48] Icons for explorers, extensions and so on.
[11:54] This left bar here.
[11:56] You can click explorer.
[11:57] There is this search bar.
[11:59] There is this run and debug mode and there is this extensions.
[12:03] You can see the Kiro and this is this Kiro powers and there is this Python and so on.
[12:08] This on the left side.
[12:10] You can go here and now it is shown.
[12:13] Let's go to the next one.
[12:16] It is the sidebar panel.
[12:19] Opens when you click an activity icon.
[12:22] Shows your files, specs, works, powers and so on.
[12:24] Meaning that we click into it, we went to the sidebar panel.
[12:28] And at the big center, this part here when you start writing some code.
[12:33] This is the main code editor panel.
[12:36] And now there is this chat panel also.
[12:38] The AI chat on the right.
[12:41] This is where you talk to the Kiro has a five and spec mode.
[12:45] If I go here, now it is not shown here.
[12:49] If you see on the top right corner there is this chat icon here.
[12:54] If I click this one, now you can see the new UI appears here which says this five and the spec.
[13:02] And there is some information also being provided.
[13:04] I can close this one and make this little bit bigger so you get to see this.
[13:10] This is the five and this is the spec.
[13:13] And here is where we write the code or
[13:16] We ask Kiro to write the code.
[13:19] And the E is the status bar.
[13:22] Thin bar at the very bottom shows your Git branch, errors, AI agent status and so on.
[13:27] That is the last one here.
[13:29] You can see on the bottom all the way down.
[13:32] There is this auto complete, report issue, Kiro free bonus zero of 500 used and so on.
[13:38] It shows you how much it is being consumed.
[13:40] If I click this one, it will open the same thing that I showed you before.
[13:46] This is the five main things that you need to be knowing.
[13:48] On the left side, on the bottom and on the top right there is this chat icon where we can write the.
[13:55] Other things you can explore the terminals if you want to know.
[13:57] On the top there is this terminal.
[13:58] You can just write a new terminal and now you can see the new terminal pops up here and here you can start writing the thing.
[14:09] Or you don't even need to write here.
[14:10] The Kiro runs in your terminal to do things for you.
[14:13] I will just do exit here.
[14:16] For now.
[14:16] I hope now you get the overall idea of this interface.
[14:22] There is the shortcuts also.
[14:22] You can open the AI.
[14:24] I don't want to go into shortcuts now here because it will be different for different machine, but you will get it once you start doing things.
[14:32] Open the AI chat panel, inline AI editor and so on.
[14:35] You can just do things as you move, but then when you start doing things it will appear already there.
[14:43] It's easy for us to know.
[14:43] That is it.
[14:44] That is the AI Kiro interface.
[14:48] Now if I go to the next section, it says steering files.
[14:51] Give Kiro a memory.
[14:56] If I go again to this Excalidraw, we went the interface.
[15:00] Now we are going into the steering files.
[15:05] You might be thinking, okay, we haven't even started.
[15:06] Why are you talking about this steering files?
[15:09] Now let's go into it just to understand here.
[15:11] I will go through this documentation which I created.
[15:16] Before you do anything else in your project, do this first.
[15:23] This is what you need to do this first.
[15:25] Steering files tell Kiro about your project.
[15:28] It does not ask the same questions over and over.
[15:31] Open a project file explorer.
[15:35] Click the ghost icon in the left activity bar.
[15:38] Generate the steering docs.
[15:41] Kiro creates three files automatically.
[15:44] Kiro steerings and there will be these three different things.
[15:49] You can edit these files.
[15:51] Open this and add the short description and so on.
[15:54] This is just a simple thing here.
[15:56] But here it says file open folder and click the ghost icon in the left side.
[16:02] Now let's follow step by step.
[16:04] I will go here.
[16:05] So this is the thing here open folder.
[16:07] I haven't created the folder yet.
[16:10] Let me open one of the folders.
[16:13] I will create a new folder called Kiro uh.
[16:17] YouTube.
[16:17] Just like this.
[16:19] I will create this here.
[16:19] And now I will open this.
[16:24] Okay, allow.
[16:24] Trust and so on.
[16:26] Now you can see here there is this Kiro-YouTube and dot VS Code.
[16:32] It's just there when I create this.
[16:32] Now once this is open, open folder.
[16:35] I just open an empty folder for now.
[16:38] And click the ghost icon in the left activity panel.
[16:44] What you need to do here is if you go down here, click this one.
[16:48] And now you can see this is specs, agent works, agent steering and skills, MCP servers all start appearing here.
[16:54] Now the main idea here is to generate the steering docs.
[16:59] I will just click this steering.
[17:01] Generate the steering rules.
[17:04] When I click that generate steering docs, what happens is that it automatically went into this chat mode.
[17:13] And now you can see inside it it reads the settings.json file which was in this.
[17:19] Dot VS Code.
[17:22] Now you can see these three files will be created here inside this steering and skills.
[17:25] This is the first thing that it recommends me to do.
[17:30] And then it also explains what it is doing.
[17:32] Let me make this little bit bigger.
[17:35] Like this.
[17:36] You can see here it says the workspace is essentially empty.
[17:40] Just Kiro config and a VS Code settings file.
[17:43] I will create minimal generic steering docs that are still useful as a starting point.
[17:49] I don't want to go with the existing project so it confuses you.
[17:56] I just want to go from here.
[17:57] And by the way one thing to mention is the shortcuts are all appearing here.
[17:59] That's it.
[18:02] You can just go with the shortcuts.
[18:05] It says here, okay, accepted accepted.
[18:07] Created creation of a product.md here.
[18:11] This is the product and there is this MD and there is this including steering docs.
[18:16] You can see here, right?
[18:17] There is this product.
[18:19] And here you can see this is this product.md file.
[18:24] And you might be thinking, okay, it is showing here the product, but why is it showing this Kiro steering and so on?
[18:31] Now what I will do, I will open this.
[18:33] First understand that inside this ghost Kiro icon we have this agent steering and skills.
[18:42] And there is this structure also which it is mentioned here.
[18:44] There is this take mentioned here.
[18:46] If I go to this explorer icon here, before there was just this dot VS Code and the settings.
[18:55] It is just empty.
[18:55] It is just saying Kiro configurations which was created by default when I open that folder, empty folder.
[19:02] And now you can see there is this dot Kiro and the steering folder already being created when I click this Kiro steering.
[19:09] Right?
[19:09] Inside it there is this product.md, same file, take.md, structure.md being created.
[19:18] Now what is the next step we need to do?
[19:20] It says here click steering and docs.
[19:22] Kiro creates three files automatically inside this one.
[19:24] That's what we see.
[19:27] You can edit these files.
[19:30] Open the product.md and add a short description of what you are building.
[19:32] We are going to build a simple to-do applications.
[19:37] Kiro will read this every time you chat.
[19:41] Now you get the idea why this is the most critical step that you need to do very beginning.
[19:48] One beginner mistake is also that is skipping this step.
[19:50] Always generate the steering docs before anything else.
[19:53] I don't want to cover how other IDE or other AI coding platform works.
[20:02] But all this is the first step that you need to be going.
[20:05] One thing to mention, I said IDE.
[20:07] You might be thinking what is IDE?
[20:09] Let's just Google it.
[20:12] Let's do Google.
[20:15] I will go to the website this Google.
[20:17] I will do IDE.
[20:19] I said IDE.
[20:21] You might be thinking what is IDE?
[20:23] IDE is integrated development
[20:26] environment. For example, the place
[20:28] where we write the code.
[20:30] This VS code, uh Kiro, and there is
[20:33] other also. We call it IDE.
[20:36] IDE a software that provides a
[20:38] relatively comprehensive set of features
[20:41] for software development and is intended
[20:43] to enhance productivity by providing
[20:45] development features with a consistent
[20:47] user experience and so on.
[20:49] Just to let you know that this is what
[20:51] IDE called. There is even all sorts of
[20:54] you can see here example Visual Studio
[20:56] IDE and code editor for software
[20:58] development and so on. You get the
[20:59] point. When you are talking with your
[21:01] friends and so, they might be saying ah
[21:02] okay that Kiro and the IDE. Just
[21:05] explaining you this so that you are not
[21:07] confused.
[21:08] I will open this product.md.
[21:11] I will select this control A to select.
[21:14] I will just copy, go here, and do
[21:16] control V. It says here my I can even
[21:19] remove this
[21:20] product
[21:22] here.
[21:24] My to-do app. You see here there is this
[21:28] project structure. This is the product.
[21:30] I can say my to-do app a simple web app
[21:32] for managing daily task built with
[21:34] vanilla HTML, CSS, and JavaScript. The
[21:36] thing here is you need to know what you
[21:39] want to create. You can just say I want
[21:41] to create a simple web application, but
[21:43] I hope if you are building some
[21:44] applications, you research it before
[21:46] providing something to Kiro. And now the
[21:49] target users is complete beginners
[21:51] learning web dev. I did and I will save
[21:54] this control. Now I have this in this
[21:57] product.md.
[21:59] You can see the first step we did. Let
[22:01] me again go to this. I want to show you
[22:02] step-by-step. Just to show you also
[22:05] here.
[22:06] What your app does and who it is for is
[22:09] in the product.md.
[22:11] And the tech is what frameworks and
[22:13] libraries you are using, you can put
[22:15] inside that.
[22:17] And the structure is how your files and
[22:19] folders are organized.
[22:22] You can see the top three main important
[22:24] things what you need to do when you
[22:27] start writing the code. Now just to go
[22:30] into this Excalidraw diagram interface,
[22:34] uh steering files. Now let's go and see
[22:36] the vibe versus the spec mode.
[22:40] That is the main thing in Kiro.
[22:43] Now I will close this. You can go here
[22:45] and start doing the things.
[22:47] But you can even go and create a new
[22:49] sessions with this plus icon here. You
[22:52] can see there is this task list, there
[22:53] is this history. If you want to see the
[22:56] history from here, you can see there is
[22:57] the history also. You can see the task
[23:00] list. If you have something here, you
[23:01] can do current task, task in the queue,
[23:03] and so on. There is this new section. So
[23:07] if you go to this plus icon, this new
[23:09] window will pop up here.
[23:11] Now it says let's build. The vibe coding
[23:15] chat first then build.
[23:18] Explore ideas and iterate as you
[23:20] discover the needs. Great for rapid
[23:22] exploration and testing. Building when
[23:26] requirements are unclear.
[23:28] Let's say you want to build something
[23:30] and just
[23:31] write whatever you want to do here, it
[23:33] will start creating the things for you.
[23:36] But in this spec mode, it says plan
[23:38] first then build.
[23:40] This is the main selling point of the
[23:43] Kiro.
[23:44] That it is the spec driven development
[23:46] is supported here. So that you can plan
[23:49] first. Uh it will be showing you
[23:51] step-by-step things
[23:53] and then you can build later.
[23:55] Create requirements and design before
[23:57] coding starts. This is how if you are a
[24:00] UX designer or if you are a
[24:03] strategic designer, you can go here and
[24:05] do your planning things. All the things
[24:08] that you have planned before provide
[24:09] here and then it will ask okay is this
[24:12] clear? And it will start doing things.
[24:14] It is great for thinking through
[24:17] features, projects needing upfront
[24:18] planning, and building features
[24:21] structured way just to get started.
[24:24] [snorts]
[24:25] I will go to the next here.
[24:28] The idea here is that if you want the
[24:30] quick experiment, simple changes,
[24:32] exploring ideas, fixing a bug, learning
[24:34] how something works, go with the vibe
[24:36] mode. Spec mode is building a full
[24:38] feature, creating an app from the
[24:40] scratch, anything building three plus
[24:42] moving parts work, come back to later,
[24:46] projects shared with others, and so on.
[24:48] So the tip here is start with vibe more
[24:50] to explore then switch to a spec mode
[24:52] once you know what you want to build.
[24:56] This way you get to know how these two
[24:59] modes work. Next one is build your first
[25:02] to-do application. What I am planning to
[25:04] do is I want to go to this spec mode
[25:08] directly, but let me go little bit later
[25:10] here. What I want to do is just to show
[25:13] you how this vibe mode works because my
[25:16] idea is to go with the spec mode because
[25:18] that is the main thing that you want to
[25:20] learn. But let's go with the vibe mode
[25:21] and we will just undo the things.
[25:24] Let's see what happens. We are in the
[25:26] vibe mode. I will say here create a
[25:30] simple
[25:32] to-do
[25:34] app. Just a simple example, but before
[25:37] going that I want to show you one thing
[25:39] here. You can see here this hash
[25:42] where you can add the content. You can
[25:44] even attach image or documents inside
[25:47] it. This is the place where it will be
[25:49] showing you the con- text being used is
[25:52] because once the context gets closer to
[25:55] the end, you will see in the circle. The
[25:57] good idea is to create a new chat not to
[26:00] go and do all the things again and again
[26:02] in the same chat.
[26:03] And here is this autopilot mode which
[26:06] means that it will just go autopilot as
[26:09] the name suggest.
[26:10] And from this drop-down, you can choose
[26:13] the models.
[26:15] For free also, we have auto mode which
[26:17] chooses the task for optimal uses. And
[26:20] there is Sonnet 4.5, Sonnet 4, Haiku
[26:22] 4.5, Deep Seek version 3.2, MiniMax, and
[26:26] there is MiniMax M21, M25, GLM Queen 3,
[26:30] Coder Next, and so on. Experimental
[26:33] preview of this you can see and you can
[26:35] also see how much of the credit is being
[26:37] used because you have limited credits.
[26:40] You want to just go here and use the
[26:42] credits that you need because you can
[26:44] see if I go to Cloud Sonnet 4.5, 1.3x
[26:47] credit is being used. The cre- credits
[26:50] might pile up quite fast. You can go
[26:52] here and choose different models. I will
[26:54] go with this auto mode for now and I
[26:56] will send this one. Let's see what
[26:58] happens.
[26:59] Now you can see the first thing it does
[27:01] is including the steering documents.
[27:04] product.md, structure.md,
[27:07] and tech.md. It went through that.
[27:10] And here is the structure I will create.
[27:12] It says okay, I will create a index.html
[27:16] file. I will create style.css.
[27:19] I will create app.js. Three things.
[27:22] JavaScript, CSS, HTML. This is what we
[27:26] have in this product.md.
[27:28] Okay, this is already done because the
[27:30] small application that I want it to
[27:33] create. Accepted criteria for this, open
[27:35] this index.html in your browser and you
[27:38] are good to go. It supports adding
[27:40] tasks, checking them off, deleting them,
[27:42] and persist everything in the local
[27:44] storage. Your list survives page
[27:47] refresh. On the left side, it creates
[27:50] this app. If I click this, you can see
[27:53] the code is here. This is the
[27:55] app.json being created and this
[27:59] index.html file being created which
[28:01] shows in the UI. And here is the CSS. I
[28:04] want it to be beginner-friendly. What I
[28:06] will do, I will go to the finder.
[28:09] I will go to the desktop. I will go to
[28:11] the place where I created the folder. I
[28:14] was creating this Kiro YouTube. Inside
[28:17] it, I have this index.html.
[28:20] I will just double-click this.
[28:22] Now you can see it opens in the browser.
[28:24] Now we have this application being
[28:26] created my to-dos. And here it says add
[28:29] a new task. Add I can say here
[28:32] drink water. And you can see I press
[28:36] enter and it is appearing here. And I
[28:39] can even write here read
[28:43] blog post about
[28:45] GenAI something. And here is this add
[28:48] button. It appears here. And once you
[28:50] are done, you can just click this and
[28:52] that is done. If you click this, that is
[28:54] done. And if I now go here and do the
[28:57] refresh, you can see I do the refresh,
[28:59] but still it's there.
[29:01] Meaning that it is stored in my local
[29:04] storage in your machine. So it is stored
[29:06] here. What happens if I close this now?
[29:09] Let's say I open this again the next
[29:11] day. I will come here. Okay, still
[29:13] there. Once you remove this local
[29:16] storage, then this will be gone. But you
[29:18] get the point, it is here. But now I
[29:20] want to do I don't like this simple
[29:23] looking thing.
[29:24] Open this chat again in the same chat
[29:28] interface. I will say here
[29:30] can you make the UI look little
[29:35] better with some
[29:37] emojis? Now it says working. It reads
[29:40] the files where it needs to read. It
[29:43] makes these two edits. Here you can see
[29:45] now update the CSS. It's still working.
[29:48] If you notice here, it says view diff.
[29:51] Now it's done. Here is the great change
[29:53] and it provides you and the good part
[29:55] here now is it is also showing the
[29:57] credits being used and how much time it
[30:00] took. But before going into that, I want
[30:02] to show you this. What does this diff
[30:04] mean? If you don't know about Git also
[30:06] before,
[30:08] this means what changes it did from the
[30:11] previous code. If I click this one,
[30:15] so now you can see here. I will just
[30:17] make this bigger. You can see it removes
[30:21] this one and it added this one. So this
[30:24] red one and this green one. If I go down
[30:27] here, you can see all the places it will
[30:29] be showing you what it deletes, what it
[30:32] adds, what was the previous version of
[30:34] the code and what is the latest version
[30:36] of the code. And also you can do this
[30:38] undo all changes. It will undo all the
[30:40] changes here. But
[30:42] this is
[30:43] file by file things. But if you want to
[30:46] revert everything, right? Here is the
[30:48] thing already called eight changes are
[30:52] done here. View all, you can view all
[30:55] the diff and it says revert. It will
[30:58] revert all the changes.
[31:00] Now let's go to the UI. I will go to the
[31:02] file again. Here, I will again open this
[31:05] index.html.
[31:07] Now you can see it looks better.
[31:10] Now it has this to-do and there is this
[31:12] pencil icon here and it is little bit
[31:15] better here and I can now say record
[31:19] YouTube video at 5 p.m. So now you can
[31:24] see I have my new to-do being created.
[31:27] Looks already good. In the morning I
[31:29] come here, open the file, write my
[31:31] to-dos. It will be stored in my local
[31:33] machine. I done done done. If something
[31:35] is remaining, I continue later or or the
[31:37] next day.
[31:39] Simple application if you want to have
[31:42] your simple to-do running in your
[31:43] machine locally. You can open this. It
[31:45] opens in your browser and you can go
[31:47] here and do things. That's it. This is
[31:49] the thing that I want to show you from
[31:52] the vibe mode.
[31:54] I will close this. Now what I will do is
[31:56] I will go into the spec mode.
[31:59] You can see here create a project
[32:00] folder. I already did that. I don't need
[32:03] to go and say to-do.
[32:05] And here it says open the folder. I will
[32:07] do the product and I already pasted
[32:09] this. But you can just do this here.
[32:14] And now it says here switch to the spec
[32:16] mode and describe your feature. Let's
[32:18] see what happens now. I will go to the
[32:20] spec mode. I will copy this one. I will
[32:23] go to the Kiro. Now I will say revert
[32:25] here. So all things are being reverted
[32:29] here. Okay.
[32:31] And now I say new chat.
[32:33] Now I have these things. If you see
[32:35] here, the structure is here, the take is
[32:37] here and there is this product and there
[32:40] is this VS code and so on. But what I
[32:41] will do now is I will delete for now
[32:44] just for simplicity. I will not create a
[32:46] new folder, but I will delete these
[32:48] three files being created before. Let me
[32:51] go and delete this style also.
[32:54] What I will do now, paste the thing that
[32:56] I just copied.
[32:58] Here, I will save this one. And now I
[33:01] need to go to the spec mode.
[33:03] What I did?
[33:05] I went to product.md. That is where I
[33:07] want to go first. I pasted this part
[33:10] here. Now I can close this. I don't need
[33:12] to worry about this. I will copy
[33:16] this one. I will go to the Kiro.
[33:19] Control V.
[33:20] Here I'm saying build a to-do
[33:21] applications, add to-do this. I will
[33:23] just send this first. Add a new to-do by
[33:26] typing a title and clicking add. Make
[33:28] to-dos as complete or incomplete by
[33:30] clicking. To-dos should
[33:32] save to local storage. Use vanilla HTML,
[33:35] CSS. Make the design clear and more
[33:38] modern with central card layout. No
[33:40] frameworks, no NPM, no build tools and
[33:42] so on. The idea now you get the
[33:44] difference. In the first I am completely
[33:46] beginner. I want to explore the things.
[33:48] I said build a to-do app. Then I start
[33:50] creating on top of it saying make the UI
[33:52] better. But now with the spec driven is
[33:54] little bit more advanced where you
[33:56] already plan to do something. What I did
[33:59] in the first part is all mentioned here
[34:01] now. I want this. I want that and so on.
[34:04] Now what it does? Look here. Reads the
[34:06] file. That's the first thing that it
[34:08] does always.
[34:09] We need to always go and modify there.
[34:11] It says input required. Based on your
[34:13] description, this sounds like a new
[34:15] feature. Is this a new feature or a bug
[34:17] fix?
[34:18] Now you see when you move to the spec
[34:20] driven,
[34:21] it says okay, build a feature or fix a
[34:25] bug.
[34:26] This is a new feature we want to do it.
[34:28] I will click this build a feature.
[34:32] I will submit the answer. You click this
[34:34] one.
[34:35] You submit the answer and it says okay,
[34:37] build a feature. Now it is working on
[34:40] it. It needs to create a plan for us
[34:42] first. Once we are completed this step,
[34:45] you will be seeing a new UI. Which then
[34:47] we go step by step. Now it says what do
[34:50] you want to start with? Requirements,
[34:52] begin by gathering and documenting
[34:54] requirements and technical design. Begin
[34:57] with the technical design then derive
[35:00] requirements from that design. It says
[35:02] recommended. Okay, let's go with the
[35:04] recommended one.
[35:06] Requirements, right?
[35:09] Now let's see what it ask. It didn't ask
[35:11] now. So it goes there. Okay, search the
[35:14] working space.
[35:16] Check existing specs and directory
[35:18] structure. Now it went to this dot
[35:20] config Kiro. You can see here now inside
[35:22] the Kiro we have this. Now there is this
[35:25] now specs folder being created. Now it
[35:28] went into the specs. Inside the specs it
[35:31] created this to-do list app app app and
[35:34] then it says here is the requirements.md
[35:38] file being created. Accepted criteria,
[35:40] the requirement doc is ready. Here is
[35:42] the summary.
[35:43] Now you can see requirement.md
[35:45] is being created. Now we can go step by
[35:47] step. I will close this one.
[35:50] I don't need this one now. But just to
[35:52] show you, I can even make it little bit
[35:54] small so you know what is happening as I
[35:57] speak. I'll make this little bit bigger.
[36:00] Now here there is requirements. New UI
[36:03] appears here. It says requirements.
[36:05] After this we go to design. After this
[36:07] we go to task list. In the requirements
[36:10] now all the instructions is being
[36:11] written here. We can open in the
[36:14] preview. I can click
[36:15] this. It will open in the preview to
[36:17] read this. Glossary app, to-do list,
[36:19] storage, filter. Also requirements.
[36:22] Requirement one, add a to-do.
[36:23] Requirement two, display the to-dos.
[36:26] Okay, is this plan? I can go here and
[36:28] move to the next phase. Because here you
[36:30] can see it says continue so that it goes
[36:34] to the next phase. But you can directly
[36:36] go here and say continue. The idea here
[36:38] is you can directly go here in the UI if
[36:41] you don't prefer the chat and click this
[36:43] continue. In the design I will quickly
[36:45] continue. But here I will say here looks
[36:48] good. Enter.
[36:51] Now what happens is it says okay, my
[36:53] requirements is now clear. Now I can
[36:57] move to the design phase. Now you can
[36:59] see this icon will then move to the
[37:01] design phase. Still it is not creating
[37:04] this task list.
[37:05] It will go to the design phase. It is
[37:07] thinking here. Search the working space
[37:09] and so on. This will move to the design.
[37:12] It will say creating the design.md. Now
[37:15] you can see
[37:17] it is saying creating the design.md.
[37:19] Once this is created, I will show you in
[37:21] the explorer where it appears. Here we
[37:24] have this requirements. Now you can see
[37:26] there is this design.md is created and
[37:28] now this moves to the design phase here.
[37:31] Now this is saying what is the design
[37:32] that it wants to create. Now you can see
[37:34] clear visual is being created. I will
[37:36] say open preview. Here is the thing. A
[37:38] simple page the app. Local storage,
[37:41] HTML5 architecture. It even creates the
[37:43] architecture. Okay, I have this
[37:44] index.html, add form, to-do list,
[37:47] filters, app.json, state in memory,
[37:50] local storage, read, write and so on. It
[37:52] creates this visual diagram and this is
[37:54] the data flow. You can just go here now
[37:56] and iterate on top of this existing ones
[38:00] that you want to make it better. But if
[38:02] it looks good, you can just go here and
[38:04] do continue or looks good here also. I
[38:07] will go here now. It says generate the
[38:08] task. Now you can see it is now going to
[38:11] generate the task. It goes here and now
[38:13] the new file will being created.
[38:16] Task list and then it will move to this
[38:19] task list part here. It is again
[38:21] reading. There was some error. Operation
[38:23] was aborted by user or system. This is
[38:26] there was some
[38:27] issue there, but now it checks
[38:28] everything there. I want to do it fast
[38:30] because this is a simple to-do
[38:31] application. It says here task list.
[38:35] Here you can see all the task list is
[38:37] being created. This is the interesting
[38:38] part here. Here it says task list is
[38:41] being created and now you can see there
[38:43] is the task.
[38:45] You can directly start the task from
[38:47] here.
[38:48] And if the task has small task inside
[38:51] it, there is this 2.1, 2.2 and so on.
[38:56] You can even go and trigger this smaller
[38:58] task inside it also. Now it says here
[39:01] run all. And you can see there are
[39:04] altogether 10 different tasks. It's the
[39:06] step being created here.
[39:08] But if I say run all, let's see what
[39:10] happens. If I say run all, now there is
[39:13] two things.
[39:15] One is run required task only and the
[39:18] next one is run required and the
[39:20] optional task. You can see here there
[39:22] are some required task and there are
[39:24] some optional task. This make task
[39:26] required. That is the optional task. It
[39:29] might not be needed, but you can even go
[39:31] here and say make this task required.
[39:34] Or you can just say here there are some
[39:36] task which are not required.
[39:39] You can just run all those or you can
[39:41] just say okay, just run the required
[39:44] one. I will say okay, just run the
[39:46] required one.
[39:47] See now what happens.
[39:49] I will click this one and now if you see
[39:52] in this UI, the task is queued.
[39:55] And I will start by queuing all the
[39:57] required incomplete task then execute
[40:00] them sequentially. Now it says queued.
[40:03] If I go down, now it says queued. So it
[40:05] knows which queue it needs to go through
[40:08] here. Task is queued and so on. Once
[40:11] this is queued, if I now go to the
[40:14] history, there is the history and there
[40:16] is the thing now also called run all
[40:17] task appearing here. You can just
[40:19] navigate between the UI here and there.
[40:22] Now it went all the way down here. The
[40:26] task is queued. It is still queuing the
[40:29] task.
[40:30] And now it is done. Now it says now it's
[40:33] starting the task one. First it goes
[40:35] through each and everything what it
[40:37] needs to do the task and now it is doing
[40:41] the task for us. The files appear here.
[40:44] This is in progress. View the changes.
[40:46] Create a project files. Now it starts
[40:49] creating the file. On the right
[40:52] if it is some error, it will start
[40:54] mapping those things here in the chat
[40:56] panel. This is the chat panel. You can
[40:58] see what is happening. In the middle,
[41:00] this is this UI or the main coding panel
[41:04] where you will see what task is
[41:06] completed, what is the next task and so
[41:08] on. We have now this app.js index and
[41:12] style CSS being created. Now the task
[41:15] one is completed. It will even show you
[41:17] this icon here saying okay, task is
[41:19] completed. And now it is going to the
[41:21] second one which says implement estate
[41:24] and storage and the 2.1 is in progress.
[41:27] Once this is done, you can see 2.1
[41:30] completed. This is also completed.
[41:33] And now it goes to 3.1.
[42:24] Okay, task is completed. Now all task
[42:27] done, the to-do app is fully built. Just
[42:30] open index.html in a browser and it's
[42:33] ready to use. It took 7 minutes for us
[42:37] and it uses 5.73
[42:39] credits. Now what I can do is I can go
[42:44] to the
[42:45] file again here. These are the three
[42:47] files it created. If I go to Kiro
[42:49] YouTube again, same three files but now
[42:52] this is the new version of it. It is not
[42:55] showing these hidden files. Okay, to-dos
[42:57] at add one before it says active,
[42:59] completed. Add now I can say it again.
[43:03] Drink water. Water is needed. I will say
[43:06] add.
[43:07] But where is it all? Okay, here you go.
[43:10] It's completed, not completed. Yes, it's
[43:12] active. Now if I click this one you can
[43:15] see now the UI goes here. You can delete
[43:17] once this is done. Completed, it is
[43:19] shown here. Active.
[43:21] There is nothing here. All is here. So
[43:23] it looks good. Now you can go here and
[43:25] do more things adding emoji but you get
[43:28] the point. We ask it better to do it
[43:30] thinking since it builds on top of it
[43:32] and it looks already a little bit better
[43:34] because we provided the specs better
[43:36] into the spec driven development.
[43:40] The next thing now is the agent hooks.
[43:43] What is it all about? If I go to the
[43:47] documentation that I have also created,
[43:49] hooks are the rules that tell Kiro when
[43:52] these happens do that automatically.
[43:55] Meaning that you can set them once and
[43:57] they will run it forever. I will show
[44:00] you directly from the UI here. This is
[44:02] the UI of Kiro again.
[44:05] If you go to this icon here, you can go
[44:07] inside here. There is called as agent
[44:10] hooks. I will click this plus icon here
[44:13] and now it says manually create a hook
[44:16] or ask Kiro to create it. If I go to
[44:19] this manual creation UI, this looks like
[44:21] the manual creation UI. The step one,
[44:23] step two, step three. You can give the
[44:25] title, description, ask Kiro run command
[44:28] and this is this manual trigger. When do
[44:30] you want file hooks? Is the file
[44:32] created, file saved, file deleted?
[44:34] Whenever something happen, you want the
[44:36] hook to be activated? Or it can be
[44:38] contextual hooks meaning the prompt
[44:41] submit, agent stop, pre-tool use,
[44:43] post-tool. It might be easier for you
[44:46] just to create by AI and see what
[44:49] happens in the UI. Cancel or clear. I
[44:52] will even cancel this one. I will again
[44:54] go to this create hook. I will say ask
[44:57] Kiro to create it. Ask Kiro and now you
[44:59] can see here.
[45:01] It is saying you describe a hook using
[45:04] natural language or choose a sample
[45:06] prompt. Update my documentation,
[45:09] optimize my code, language localization
[45:11] set. I can say here update my
[45:14] documentation. It listens to all the
[45:16] source files in this repository. If this
[45:18] is a repository or type script project,
[45:20] if it is a Python, it goes to this and
[45:23] listen to the relevant other files. On
[45:25] the change on these files, ask the agent
[45:27] to make changes to the documentations
[45:29] also. Ask Kiro.
[45:32] So this is the thing it automatically
[45:33] creates here. Once this is done, you can
[45:35] go to explorer hooks and there is also
[45:38] the sync docs on change being created.
[45:41] So now what we can do, it says here when
[45:43] the file is changed to these different
[45:45] things. This is already saved.
[45:48] I can now go to this file explorer. I
[45:51] can go to this index.html
[45:54] and let's say I will add something here.
[45:57] What needs to be done?
[46:01] Let's go on something like this and I
[46:04] will just save this one. You can see
[46:06] once I save the file the hooks
[46:09] automatically triggered and now it just
[46:11] run something. There was nothing to do
[46:13] and it just went away. But now let's say
[46:15] that I want to go here and write some
[46:18] extra stuff. I will again save it. Now
[46:21] again it works. It is including the
[46:23] steering documents and now you can see
[46:25] it says the placeholder change index is
[46:28] a minor formatting artifact and
[46:30] accidental new line and this added in
[46:32] the placeholder. No readme or docs
[46:34] update is needed for this diff but it
[46:37] shows you that there is something
[46:39] happens. Maybe this was a mistake when
[46:41] you type something. It happens all the
[46:43] time. You type something, happen
[46:45] something and it will show some error.
[46:47] But now with this hooks being created,
[46:49] you know that okay, this is the hook
[46:51] being created. It notifies you that this
[46:54] change was done here and in this
[46:57] index.html.
[46:59] I hope now you get the idea of the hook,
[47:02] how the hook is being used so that you
[47:04] can set when it should run and it runs
[47:07] all the time. What I would suggest is
[47:10] you sit with your and ask some of the
[47:13] hooks to create together so that maybe
[47:16] some of the things that the AI can just
[47:18] go automatically when you do some of the
[47:20] things.
[47:21] It goes through the code when you are
[47:23] changing or the when the Kiro itself
[47:25] writes the code and the hooks are
[47:26] automatically triggered as you move into
[47:29] the project.
[47:30] The next one if I go to the Excalidraw
[47:32] diagram, it's about the pricing page.
[47:35] Just to show you here. On the bottom
[47:37] here it says Kiro bonus here. If I click
[47:39] this one, you can see it takes me here.
[47:41] It gets the upgrade plan. You can go
[47:43] into this one and now you can see all
[47:46] the plan. This is our current plan. You
[47:48] can go with the
[47:51] you can see everything Kiro free. You
[47:53] have this use up to 1,000 credits and
[47:56] how many credits you want, you can go
[47:58] with different options. This is up to
[48:00] you how you want to move in into the
[48:01] plans. I think the current plan is more
[48:04] than enough for us.
[48:06] Now let me go what we have left.
[48:09] Problems and fixes. I want to mention
[48:11] this documentation, common problems and
[48:13] how to fix them. There are many problems
[48:16] in the Kiro's GitHub because this is in
[48:18] the GitHub already. Just to show you
[48:20] there are different things that is here.
[48:22] I install a power but cannot be used. I
[48:25] cannot find the spec files. All these
[48:26] small things. I recommend you to go to
[48:29] this official GitHub. Here you can see
[48:32] there is this 3.4 thousand stars but
[48:36] there are already 2.7k issues. If you
[48:40] face some sort of issues here, go to
[48:43] this issue section here. There are
[48:45] already 4,250 closed ones. You can
[48:49] explore some of the closed ones if you
[48:51] need but if you want to just go with the
[48:53] open one, maybe somebody else has
[48:55] already opened a issue here. So you can
[48:58] also open the issue here.
[49:00] One drawback with WSL because many of us
[49:04] in the company might use Windows machine
[49:06] need to run Linux and so on but the Kiro
[49:08] does not directly support that and they
[49:10] are still working on it. If you want to
[49:12] go ahead and search for that, one of my
[49:14] colleague mentioned in the issue here.
[49:16] If I go to the WSL, you can see WSL
[49:18] support. It was created July 15, 2025.
[49:22] This is the feature. You can go down
[49:24] here and see thumbs up and you can start
[49:27] having a conversation into it. There are
[49:30] all the conversation how to fix this. My
[49:32] colleague Adam has also mentioned this
[49:34] on February 15th. You can see from here.
[49:37] if I go to what Adam has mentioned, MCB
[49:39] local servers use Windows shell rather
[49:41] than configuration WSL. This is how you
[49:44] can also write an issue. To write the
[49:47] issue is not that difficult. You can
[49:48] just go here to the new issue here, and
[49:51] then you can choose what it is all
[49:52] about, and
[49:54] it can be even a Kiro website, Kiro
[49:56] documentation, and all sorts of things
[49:59] so that you are also engaged with the
[50:00] community here or the Kiro developers
[50:02] here. You see that
[50:05] once it needs to go, then only it will
[50:06] go. But anyway, now let's go into the
[50:09] cheat sheet that I have created. This is
[50:12] already what I have explained you all,
[50:14] but just to show you
[50:16] that here. So, these are the things that
[50:19] you always need to do. You need to open
[50:21] a project, go to the steering, generate
[50:23] the steerings, edit the product.md. You
[50:26] can go to this chat panel, switch to the
[50:28] spec mode, describe your feature, review
[50:30] the requirements, review the design, run
[50:32] task one by one, and test in the
[50:35] browser. So, these are the 10 steps that
[50:38] we followed in this project. Before
[50:41] going into the Kiro powers, I want to
[50:43] show you one thing in the Kiro. If I go
[50:46] here, you can see in the Kiro itself,
[50:48] there is a thing called MCP servers.
[50:51] What is MCP servers? MCP servers are the
[50:54] way how you can connect your LLMs to
[50:58] outside of the world, let's say
[51:00] providing more context to the If you
[51:02] want to know, you can just go here and
[51:04] search for MCP,
[51:06] and it will take you to the model
[51:08] context protocol, and this is the
[51:09] website here. I have also created video
[51:11] about it, but MCP is an open-source
[51:14] standard for connecting AI applications
[51:17] to external systems. You can just go
[51:20] here and see some of them are already
[51:21] here. So, if we click on this one, you
[51:24] can see it takes you to the root level
[51:26] MCP settings, and this page is already
[51:28] there. You can just do this enabled
[51:31] enabled this equals to true, and there
[51:33] are also some of the AWS documentation
[51:35] MCP servers also here. You can just go
[51:38] to this AWS MCP servers. Just to show
[51:40] you the link from where you can go, say
[51:43] AWS MCP servers. It will take you to
[51:47] this AWS MCP server documentation or
[51:50] this Git GitHub page also. It takes you
[51:52] to this one, and again, the same page
[51:55] here. There are many MCP servers here to
[51:58] get it started. Click one of these, for
[52:00] example, data and analytics AWS
[52:02] knowledge MCP server. You can see it is
[52:04] about a fully managed remote MCP
[52:06] servers, how to do these things. And
[52:08] down here, it says what are the tools it
[52:10] has, and knowledge sources is also
[52:12] provided. The configuration is also
[52:14] here. You can go into the Kiro CLI and
[52:17] provide these settings there. So, we can
[52:19] copy this and paste it, and this is how
[52:22] you can directly go into this add to
[52:24] Kiro and click this it will install
[52:26] directly in the Kiro. Just to show you
[52:28] this example. And then also how to use
[52:30] is also shown here. Here you can click
[52:33] add to Kiro, and now it will say okay,
[52:35] open Kiro, and now you can see this is
[52:37] added here.
[52:39] AWS knowledge MCP, and this is being
[52:42] added here and so on. To configure this,
[52:44] you can go to the website that I just
[52:46] went. The link will be in the
[52:47] description of the video. So, you can
[52:49] enhance more of these functionalities in
[52:52] Kiro itself. Now, last part is this Kiro
[52:55] powers. The last one, this is quite
[52:57] advanced topic. I will show you how this
[53:00] can be used, but if you want me to
[53:02] create a new video about this, let me
[53:04] know in the comment section. I will
[53:05] cover using an existing one as well as
[53:08] creating your own Kiro powers. But in
[53:11] this video, I will show you how it is
[53:13] done from this official documentation.
[53:15] If I go on the top, there is called the
[53:17] powers here.
[53:18] And here it says empower the Kiro agents
[53:21] with expertise, and here is saying
[53:22] create a power. And there is learn more,
[53:24] you can learn more about it. If I go
[53:27] here, you can see there is the
[53:28] documentation about what is Kiro powers
[53:30] and so on with the videos also there.
[53:33] You can just follow along this one also.
[53:35] But if I go to the main page about
[53:38] create a power, that is where you know
[53:40] what it is all about.
[53:42] Here is the create the powers.
[53:44] Developers can use our curated powers
[53:47] from launch partners, which is already
[53:49] there. I will show you in the Kiro's UI
[53:52] itself. But what you need is there is a
[53:55] power.md, MCP.json, and the steering
[53:57] folder.
[53:58] You can create the power.md. Just
[54:01] provide something like this, and then
[54:03] onboarding instructions how that is
[54:05] onboarded. And if you go down, there is
[54:08] steering instructions. You can create a
[54:09] folder, and then write all the
[54:11] instructions that you want. If you go
[54:13] down, you can add a MCP server into it,
[54:15] which we already went through. You can
[54:17] take the example, and this is the
[54:18] directory structure. There is this
[54:20] example of the Supabase. Here is the
[54:23] Supabase, right? There is the power.md,
[54:25] there is MCP.json, there is steering
[54:27] folder. Inside there, there is MD. So,
[54:30] basically it's MDs in one centralized
[54:33] place, which can be shared among the
[54:35] team members. You can test this locally
[54:37] also. Just creating a folder, you can
[54:40] add the power from the local path and
[54:42] share it by pushing this into the GitHub
[54:44] or any other version control system. So,
[54:47] all your colleagues can take benefit out
[54:50] of this. A simple power, no steering
[54:52] files and so on. You can just create
[54:54] with those two files, power.md and
[54:57] MCP.json. I have created one with the
[54:59] power.md to show you the example.
[55:02] And then you can add more files as you
[55:04] go. This is the high level what is
[55:06] powers. It's quite powerful tool
[55:08] introduced by Amazon. Let me know again,
[55:11] I will create in-depth video if needed.
[55:13] But now if I go to the Kiro here, I have
[55:16] already created a folder. I will show
[55:19] you from the terminal here. I'm inside
[55:21] this Kiro YouTube, but if I go one step
[55:24] back, here is the folder called my
[55:27] company API power. That is where I
[55:30] created a custom power. If I go inside
[55:33] my company API power, I just have a
[55:37] power.md file being created. How to use
[55:39] it? You can go to this powers here on
[55:42] the left icon, and now you can see I
[55:44] have installed that from my folder
[55:47] itself. And here is the already existing
[55:51] ones. You can see there are some
[55:52] existing ones already. For example,
[55:54] let's say you want to install one build
[55:56] an agent with Pydantic AI. You go inside
[55:59] it. It is by Zone. You can see who also
[56:02] created. This is the third party person
[56:05] providing it. You need to be careful who
[56:07] created this. But let me first show you
[56:09] created by Figma, for example.
[56:11] This is the Figma example, third party
[56:14] disclaimers and so on. There is GitHub
[56:16] repository also showcasing this
[56:18] particular powers. You can install by
[56:20] just clicking this. Of course, you need
[56:22] to authenticate and so on to use this,
[56:23] but you get the idea. You can see this
[56:25] is the description by which when you
[56:27] type the keyword, these keywords will be
[56:30] taken into account, and this power will
[56:32] kick in. And you can see the MCP
[56:35] configurations also from here being
[56:37] installed. If I click this, it will take
[56:39] you to the users label MCP.json, and
[56:41] inside there we have these powers, and
[56:44] it will be added on top of this. This is
[56:46] the MCP version of it only. If you want
[56:50] to install your power, I have just done
[56:52] it from here. I will uninstall this just
[56:53] to show you. I will close this one. I
[56:56] can add custom power, and there is the
[56:58] thing called import from a GitHub. You
[57:00] can provide the GitHub, which is the
[57:02] shareable version of it, or import power
[57:05] from a folder, right?
[57:06] I will go from the folder, and you can
[57:09] see here I will go to the desktop. I
[57:10] have my company API power. I will select
[57:13] the folder, and boom, here we go. We
[57:16] have the power. It says try the power,
[57:18] uninstall, check for updates, and so on.
[57:21] I can say okay, I want to use this. I
[57:23] will try power. It kicks on into the
[57:25] chat. Okay, I just installed my company
[57:27] API power and want to use it. Let me
[57:29] activate this. Here is the activated
[57:31] version of it, and it shows what this
[57:33] power holds here. One thing to mention,
[57:36] when you install the power, it is not
[57:38] installed here. You see here there is
[57:40] hook settings, specs, and project
[57:43] specific things, but this is stored in
[57:45] the root folder. Just to show you, I
[57:47] will open the terminal.
[57:49] I will make the terminal bigger. You see
[57:52] all the things. I will go to the home
[57:54] root folder. I will go to CD root.
[57:57] Here, I have different folders. Inside,
[58:00] I have one folder called {dot}kiro.
[58:03] And inside this, I have different
[58:04] folders. But inside that also, I have
[58:07] these powers. I will go inside the
[58:09] powers.
[58:11] And if I do here ls -lia, now you can
[58:14] see I have these installed.json,
[58:16] registries, and the repos. If I go
[58:19] inside this installed, if I go CD
[58:22] installed,
[58:24] let me clear the screen. If I do ls, you
[58:28] can see now I have these three different
[58:30] things. It's Postman and the Figma, and
[58:32] there is this my company API power. If I
[58:36] go inside the Figma, I can see the
[58:39] folder structure. This is this power,
[58:41] MCP, and the steering that I just showed
[58:43] you from the official documentation. You
[58:45] can just go here and read more, but they
[58:47] are all here. Once you have the keywords
[58:51] which matches these things, then this
[58:52] will kick in. For example, if I go one
[58:55] step back, and the one that I created
[58:57] was just with one power.md. So, now you
[59:00] see there is just a power.md. The
[59:02] steering, I don't have anything here. If
[59:04] I go inside the steering,
[59:07] it is just showing here nothing to show
[59:09] because I used this install thing,
[59:11] activate. It created that steering
[59:13] folder, but I just had this power.md
[59:17] there, so nothing was being created.
[59:19] This way you can have your own powers
[59:22] being created and installed from your
[59:24] folder, as well as you can just go to
[59:27] this GitHub, make it available for
[59:29] anyone, or if you want to just have your
[59:32] company-wide powers also, you can just
[59:34] go there and create the powers and there
[59:37] you go. You have powers installed in
[59:39] your machine.
[59:41] That's all I wanted to cover in this
[59:42] video. The video is 1 hour. I just want
[59:45] to cover all these things so that you
[59:48] get the understanding of what all these
[59:51] things are. Right now, we have this
[59:53] whole circle being explained in the
[59:55] video.
[59:56] I hope you learned something new. Thank
[59:57] you for watching and see you in the next
[59:59] one.