Cursor Crash Course: Vibe Coding on a Large Codebase

[00:01] you can write code 10x faster using cursor 2.0. We are not only learning different features of cursor as a tool. We are also learning some of the systematic principles of w coding so that you can use them with any other

[00:15] tools as well such as anti-gravity, claw code and so on. We will start by building a website which has back end, front end and database layer. And then we will jump into enterprisegrade production application where we will fix

[00:29] some bugs and implement new features. This tutorial will be very different from hundreds of other cursor tutorials that you find on YouTube because they mainly focus on the tool and its features. What I'm going to show you is

[00:41] a simulated experience of how some of the senior software engineers working the senior software engineers working for big tech companies use VIP coding on big and complex projects. Let's begin by googling install cursor. Go to this link

[00:56] cursor.com/d download and install a version that is appropriate for your operating system. I already installed it. I have launched cursor. This is how it looks like. Now when you go to the settings icon, you can switch between

[01:10] different views. By default, what you get is an agentic view. What I like personally is the editor view because I'm more familiar with the traditional ID look, but agentic view also has its own benefits. So let's switch it to

[01:26] editor view. And the view here looks more like VS Code. If you have used VS Code for coding, it is similar to that. Okay. Now for a free version you will

[01:38] see something called auto. Okay or by default you will generally uh get auto. Auto means when you are writing code it will pick the correct model for a given

[01:50] task on its own. But let's say you have a preference and you want to select a specific model. In my case I like OPUS 4.5 which is anthropics model. So,

[02:02] usually I use that. In a free version, you won't be able to use it. But whatever you get in auto should be good enough. Okay? But if you pay, I'm paying $20 a month fee. And I'm getting this better model called Opus 4.5. Now, let's

[02:17] assume you want to build a website for your gardening business. Okay. So, here your gardening business. Okay. So, here I'm going to create a new folder called website growart. Let's say Groward is a name of

[02:34] growart. Let's say Groward is a name of my company and I'm going to open that particular folder. So, website Growark. Select a folder and here Select a folder and here let's uh go to the editor view. So, I'm

[02:49] already in the editor view and I'm going to use this tool called Whisperflow. to use this tool called Whisperflow. Okay. So, whisperflow is a free tool that you can download and it lets me talk to cursor using audio. So, here

[03:04] watch. I'm pressing control and windows key to talk to cursor. You can also use key to talk to cursor. You can also use this icon uh for the voice input. Build me a website for my gardening business. I sell gardening equipment, flowers,

[03:20] ports, etc. Keep the theme green. Use any shade of green for the front end. Build the front end in NexJS. Back end Build the front end in NexJS. Back end in fast API database can be SQL light.

[03:35] otherwise it's going to be too much typing. I don't like that. And here you can use a plan mode. So you're planning a new feature or building an application

[03:47] from scratch. Uh it's better to review the plan. Okay. and let's hit go. Now this is an iterative approach. So it's going to do the planning. It's going to think about the requirements. It may ask you questions. See what type of website

[04:03] do you need? Shopping cart, check out order, browse product, contact order. Okay, I need shopping cart etc. So select that. Do you need an admin dashboard to manage products? No, it can be hardcoded. Just hit continue. All

[04:19] this requirement by the way you can give in advance too. Okay. Let's say you are working with your business manager. You have prepared the PRD document. You can give that document to it and it will uh take the document and start implementing

[04:32] the features. Let's review what it has done so far. As you can see it has built the architecture overview. Okay. Like my SQL light database will have this four tables. Product categories ordered items. This is my text tag. Next.js back

[04:48] end, first API back end, Nex.js front end, SQL light, state management, React context and then this is the design theme also created database schema and theme also created database schema and so on. Okay, so I can uh view the plan

[05:03] here. Okay, see this is the plan that I can review and it has prepared this list of to-do items. Now let's say I want to add a new to-do. So I can click on it

[05:15] and I can add it. Okay. And you can also select this to-do and you can say okay only implement these two features and it will do that. Okay. So [snorts] now I reviewed the plan. It looks good to me. I'm going to hit build. So when I hit

[05:30] build it will switch from plan mode to agent mode automatically. So watch this. I'm clicking build button. And now it is in agent mode. So agent mode is used to actively write code. Plan mode is just for planning. It will not write code.

[05:45] Okay. So now it started writing code. See it created my requirement.txt. It's creating models.py. It's writing code so fast folks right for building this kind of application a developer would take probably one week.

[06:00] And here you can see it will be done in minutes or in hours. Let me take a moment to thank today's sponsor Ultralytics YOLO 26. On this channel we have talked about YOLO before. It is the de facto approach for vision AI. Euro

[06:16] 26, a latest release from Ultralytics, sets a new standard for realtime age first computer vision. It is the fastest, simplest, and most deployable YOLO model, Ultralytics has released so far. Unlike older YOLO versions that

[06:32] relied on non-max separation as a post-processing [music] step, YOLO 26 uses native end toend detection. This reduces latency, simplifies deployment, and improves performance on both small and large objects in real world systems.

[06:48] [music] You can access YOLO 26 on Ultralytics platform with downloads and documentation available to get started quickly. It supports multiple vision task detection, segmentation, classification, pose estimation,

[07:01] tracking within a single consistent framework. They offer two licensing framework. They offer two licensing options, AGPL 3.0 zero license if you would like to open source your entire project. The second one is Ultralytics

[07:13] Enterprise license for commercial proprietary deployment and distribution [music] Please try it out. The link is in video description below. Now let's get back to our video. So see right now it is

[07:25] implementing uh this particular feature two out of 10 right see it has like to-do list uh and you can see here it is checking out. So as as and when it is checking them out. See, I'm not doing

[07:40] anything by the way. It is checking them out as if you have a Jira board and you given it to different developers. They're implementing it and they're marking those stories as done. Okay. So here you see completed in order you see

[07:55] here. So it has completed these two. That's why you see this check mark and it is right now working on this particular thing. So there are quite a bit of features that we have. So it's going to take some time. So let's wait.

[08:08] It completed writing all the code. See all the todos are complete. And now it is starting the servers. Okay. So it will do everything on its own. So let me will do everything on its own. So let me click on run. If it finds error, it will

[08:21] click on run. If it finds error, it will retry it. So let's uh again click on run. And there you go folks. Our website is ready. Look at it. How beautiful it is. Let me open it in a different browser. See when I gave my prompt I did

[08:34] not even tell it that my name of the company is Growmart. Probably it recognized it from the name of the folder and it has a green theme. It is looking so professional. All the features are working. See I can go to

[08:48] equipment. I can add this features. Okay. Let's say add to card. So my card is being updated. You see? And let's say I want to add some flowers. I like red roses. Click one. Click two. Here you see this.

[09:06] Click one. Click two. Here you see this. Proceed to check out. Place an order. See, it's so professional. For software developers, it would have taken maybe a this project to an agency, they would have even charged you some money. But

[09:20] now with $20 a month subscription, you can build this thing on your own. Here I can build this thing on your own. Here I forgot to record this part but when it was done building the website it actually tested everything. So as if a

[09:35] mean if you try it on your computer you will see it tested all the different pages. You know like how as a developer I would test my website. It did all of I would test my website. It did all of that. Now I'm reviewing the menu bar and

[09:49] let's say I want to add a contact us button in the menu bar. So I can select an element. So I can click on this button and select this particular div element and let me open a new chat. By the way, this is considered as a good

[10:03] practice because when you open a new chat, you will not not have the past context. So when you are fixing a bug, implementing a new feature, it's a good practice to open a new chat. So I selected this and it has selected this

[10:16] selected this and it has selected this div element. I will say that here add contact us button. When someone clicks on this button, show

[10:29] When someone clicks on this button, show contact us page with uh required specific and give your exact requirements here. So it says that create a contact us page with a beautiful design matching the site's

[10:43] aesthetics. So it will do lot of work on your behalf even if you don't give instructions. Now folks if you have free uh subscription uh I don't know there might be a limit uh on the kota so use it carefully maybe build a simpler

[10:58] website with simple features uh and also the quality of the output will depend on the model that you're using. I'm using the best coding model okay by anthropic. If you are using auto free version by the way see you see the contact us

[11:12] button now here it's so amazing it implemented the feature and since my back end and front end is running in the reload mode it automatically refreshed this see I have the feature now okay so it's I think summarizing it okay created

[11:29] a contact us page with hero section it gives you all the information now as a software developer it is your duty to review the output and when I say output review the output and when I say output the text outputs as well as the code so

[11:43] you'll click on review button you will make sure that there is no mistake in the code and when things look okay you will say keep all which means I'm will say keep all which means I'm accepting the changes which uh my AI has

[12:00] done for me now let's test it I click on contact us button folks isn't this amazing this sounds like a magic almost I just said implement contact us button using common sense and see it is showing me the call us of course I can go to my

[12:16] website the code and change all this I can also ask it to make it configurable see here whatever send message this looks so good and check the database see in the back end now I have this database growart db it has this four table you

[12:33] can review this database and it schema as uh the schema, the name of the columns, everything is so good, so professional and see how much code it has written. This is all my backend code in first

[12:46] API. This is all my front- end code in NexJS. All right, so that was the application. Now let's move to another application which is an enterprisegrade production app. Before we move ahead, let's think about this mental model. Our

[13:01] role as a human is going to be that of an orchestrator role. So we can orchestrate with cloud code, cursor, all these different tools and we can give them context, intent, business requirements and these tools will give

[13:16] us an output. Okay, then we validate it and we just guide these tools. Okay. So our role is going to be that of an orchestrator and in future all these different roles that you see in the IT industry are going to consolidate.

[13:30] So today we have software developer, product owner, AI engineer, UX engineer. In future there will be a single person builder I don't know what they're going to call it but that same person is using now different AI tools to do the work of

[13:44] all these different people and AI engineering becomes essential because nowadays all the software products have AI features. So as a software engineer you need to know at least some AI and I have this self-paced boot camp where

[13:59] many of our students have requested if we can have live boot camp because so many of software engineers will appreciate live interaction cohort based format and we are conducting a little survey. It will be great if you can fill

[14:14] description. We are conducting some survey for live boot camp. We have not done live boot camp before. So it will be amazing. It will be a huge favor if you can fill this out. Now we will move to enterprisegrade application. It is an

[14:29] e-commerce application similar to myntra.com or aio.com or amazon.com. Here seller can create account. They can upload their product. Buyer can create account. They can buy their products there. Okay. So I'm going to give you an

[14:45] there. Okay. So I'm going to give you an access of this repository. And as I said it is a serious production grade repository which has backend code, front end code. Uh in back end you have everything like docker setup uh database

[14:58] readme everything that you will find in any enterprise application. So now let's open readme file and go through the setup steps. Okay. So when you open readme you can click on this button to get the preview. Right here you see the

[15:13] get the preview. Right here you see the markdown the raw markdown but here you can see the preview. Let me rather open it here in GitHub. Okay. So this is the repository. See it looks like very production kind of app. And for buyers

[15:27] these are the features. Sellers these are the features and this is your technology stack. It's quite involved. Okay. And this is the project structure. So let's uh get started. If you prefer using docker by the way you can choose

[15:42] option one and you can do it that way. Otherwise if you keep want to keep things simple this is the approach that you can use. So I will keep this aside. I will press control uh / character control I think

[15:58] tilda or you can just go here view and say terminal. Okay. So this way you get terminal in the cursor. Now I personally like simple command prompt rather than a

[16:12] powershell. Okay. So here you can say command prompt. You can open it. So I already have two command prompts. So in one I will run my back end. In the other one I will run my front end. So let's start with back end. So I'm going to go

[16:25] start with back end. So I'm going to go to back end. [snorts] And here uh you to back end. [snorts] And here uh you need to let's see you need to install all the dependencies. But before you do that, you have to copy the environment

[16:39] file. So whatever is dot env.ample, copy it as env file. Okay. So here you copy it as env file. Okay. So here you have this env.ample. So Ctrl Ctrl + V.

[16:51] have this env.ample. So Ctrl Ctrl + V. It will create new file and just rename It will create new file and just rename just rename that to env. Okay. So I have just rename that to env. Okay. So I have the env file. Here you need to uh copy

[17:05] the env file. Here you need to uh copy paste your email one email which you will use as your master email for creating this application. Okay. So when you place an order it is actually going to send an email to seller and buyer

[17:19] both. So I'm going to show you that entire use case. So here uh let's say you have one email your [email protected]. use an email and then you need to get this app password. So how do you get that? For this go to Google, you know,

[17:35] type in google app password and it will show you a link. This is the link my account.google.com app password. So when you click on it, you will be able to create an app. Okay.

[17:52] you will be able to create an app. Okay. So this is my highub app. So you create So this is my highub app. So you create that, you copy paste this particular app password here and make sure you are removing the

[18:06] spaces. And that's [clears throat] it folks. So this is done for your back end. For your front end, you can just copy this file env.local.

[18:18] Okay? So just say crl + v. It will create a new file and rename this file create a new file and rename this file to env.local and hit enter. The front end app is pointing to your backend endpoint. So we are going to run our

[18:33] back end on port 8000 on local machine. So no changes required here. Our I'll follow all these instructions to start my back end. Okay folks, these are pretty straightforward. So I'm going to just skip through it and I will directly

[18:47] instructions and my app is up and running here in one terminal shell. I running here in one terminal shell. I have my back end. So that is your Ubicon Python back end. Front end is npm rundev. And look at this website. It's

[19:02] similar to Amazon where you can create an account for a seller as well as buyer. So what we are going to do is click on create account and use your

[19:14] email id to create both buyer account and seller account. Okay. So you are creating two accounts. I have already created my accounts. For mobile number just give 1 2 3. It will work. Okay. So assuming you have created the accounts.

[19:27] Let's uh sign in. So here I'm going to sign in as a buyer. Okay. So let's sign in. Right now there are no products because our application is fresh and

[19:40] because our application is fresh and new. And here I have signed in as a account. Right? If you're buying something from Amazon or Flipkart, you will have some company seller. They will upload all their items. So here I'm

[19:55] going to go to products. Okay. And then click on add product single upload or bulk CSV. So we are going to use bulk CSV. And there I have provided you sample CSV in the same GitHub repo. So just drag and drop here and say upload

[20:13] just drag and drop here and say upload products. See 10 products are uploaded. So when you go to products see here you will see the image of the product, the description, price whatever. Okay. So if you have a seller account on Amazon you

[20:27] will know you will have this kind of interface. So now when I refresh this I interface. So now when I refresh this I should see all these products. See so this is now similar to Myntra etc. So I can go ahead and I can buy products add

[20:42] them to cart and uh you know do the usual process as a developer. Now I'm you know working on this website and see I'm adding two quantity here and when I say add to cart here it is showing only

[20:57] one. So looks like there is some bug. I want this badge to be such that it shows me two not one because I have two items in my card. Okay. So let's say I added

[21:09] in my card. Okay. So let's say I added that two and let's say this three. Okay. Uh in that case it should be 3 + 2 5. So this is a little bug. So we are going to ask cloud code to fix this issue. So

[21:23] what we will do is we can even take a screenshot. See capture area screenshot. So you click on it and you can capture the area. You can say that here. See

[21:35] the area. You can say that here. See you're giving it a context. The badge you're giving it a context. The badge shows wrong number of items in my cart. shows wrong number of items in my cart. Cart. Okay. Fix it. So I open a new chat

[21:49] and I am asking AI to now fix the bug. I hit the kota limit. So I added $50 more. I think this happened because for gardening website project it used too many tokens but anyways it has made all the code changes and when I go to my

[22:03] website look at this I see five you see this three and two I have total five items so this badge issue is fixed I can click on review as a responsible programmer you need to review the code changes now if you want to use LLM as a

[22:19] judge so here one LLM wrote the code okay if you want to use another LLM um to review this code changes then you click here and just say review agent changes and it will review it okay and you can also commit I already committed

[22:33] and push it with a click of a button now let's say I want to implement a new feature which is adding a wish list okay so I can go here I can click here and I

[22:46] so I can go here I can click here and I can say add a button so see here uh can say add a button so see here uh maybe in this area. By the way, you see you can see this um inspect code as well. So I don't want to use inspect.

[23:00] well. So I don't want to use inspect. Basically showing the console, but I can Basically showing the console, but I can select this element here and I can say select this element here and I can say next to this button add

[23:14] next to this button add to wish list. to wish list. There will be only one default wish list for a given user.

[23:28] for a given user. And what else do we add? Um implement this and to end. There you go. Our programmer is at work. Now it took some time but it is implementing this functionality. You

[23:44] see this wish list button, this love icon, whatever you see in a popular website, it has already implemented it. Okay. And you can once again review the code changes. It made so many code changes, 10 files. So now uh let me go

[24:01] here. Let me remove the items from my card card and say I want to add this one in my wish list. Okay. So I just click on wish list. add it to your wish list. Okay,

[24:14] home. Click on this. Okay, so these two items I added to my wish list. So now when I go here, see I did not do any iteration. I just gave one prompt. That's it. It

[24:29] implemented everything as expected. Now from my wish list, if I want to add things to card, see it added it. So this is working like a charm. Next thing we will look at is how do you add structured logging because I'm an

[24:42] experienced seasoned Python programmer and I don't like the fact that we don't have logging here. So I will open a new chat and I will say add structured logging in. Now let's say you want to

[24:56] add it in card service. So here you can give a context by saying at card service. You see this is how you give the context. So add a structure login. So you can even you can say add card service and you can say add

[25:12] logging add one log line add one log line at the start of every function

[25:25] and then record necessary context. Okay. So I'm doing this only for card service. And when you're working in a larger code basis, you will see this kind of pattern where you

[25:38] implement one code change in one file and then later on you want to implement and then later on you want to implement similar changes in another file. Let's say I'm integrating data dog for observability in one file or one class.

[25:54] I want to do it later on for other classes too. Okay. So we will see how you can do it uh using a good principles in vibe coding. So here you can see it

[26:06] is doing good. If you want any changes here again you can you can tell it and it will do it. But I like this changes. So I will say uh keep it and then I will

[26:18] So I will say uh keep it and then I will commit it. Okay. So again commit message it is going to generate on its own. So let's say it committed my change. Okay. So this is done. Now let's say I want to implement same thing in email service.

[26:35] What will I do? So one option is I give a similar prompt for email service. Right? But rather than that and by the way if I'm doing it right now I can say okay implement similar change in email service. But let's say I'm doing this

[26:50] change after 1 month or let's say some other developer is doing this change other developer is doing this change after 2 months. In that case uh what uh they can do is they can look at git log. Okay. So when I run this command get log

[27:07] it will show me the commit ID. So in this particular commit ID I added a logging service. Okay. So what I can say is uh look at commit id this and

[27:19] implement similar change in email service and it will check that git commit what changes it did and it will command because it doesn't know what kind of changes are there in that git

[27:35] commit. So you are saying get show. So it is just analyzing as if a programmer would analyze right a programmer would go to GitHub look at this git commit you know like think okay and observe what changes were done and they will do

[27:48] similar changes in this file. So it already detected that we need to implement logging here and see it is now doing its work. Isn't this amazing? Look review um you see it has all these changes.

[28:04] Okay. Now let's say uh you are doing this changes again and again. You don't want to refer to this get commit ID. This is also tedious. So let's improve it further. And the way you improve it is by using uh git commands. So what you

[28:19] is by using uh git commands. So what you can do is click on this um or rather actually I can just go here and type slash. So when I say slash I don't see any commands. There is this dummy command already, right? But I will click

[28:35] command already, right? But I will click on create command and I will say add structured logging. Okay. And here I can add the markdown file with all my instructions. Okay. So this is nothing but a markdown

[28:51] file. It doesn't have any specific syntax as such. But as a programmer I will give all the detail instructions. So now I want to change my instructions and I want to say okay here are the instructions okay first import logging

[29:05] then create a logger then create an object called log context okay then start the log also when there is an exception I want to add logging so I'm adding instructions for that add log error log and so on okay and I will just

[29:20] give it some sample code snippet as well and once this command is added now let's say I want to add logging in order service. See, order service doesn't have logging, right? So now folks, it's so easy. See, you will say / add structure

[29:38] easy. See, you will say / add structure logging. Okay? And then order service. See, this is so easy. I'm not writing any big prompts. I'm not uh referring to any past commits. All I'm doing is I have coded my instructions into this

[29:55] And I'm just saying okay run this command on this file. Now many organizations and many projects will have certain guidelines on how they want to add logging. So you can put all those guidelines in this MD file folks just

[30:10] like readme uh this is an MD file for your agent. It will read this MD file. Okay. It will understand your style of adding logging and it will add it. See I want to create this log context object. Okay that's what I want to do and it

[30:26] will do it. See, so if you review the changes now, see it added log context. Isn't that beautiful? As per the instructions that I have given here and it is doing my work. All right folks. So this way you can add more locks for

[30:41] anything that is repetitive not just for you but for your team for your organization. You add a command and see it added the command in this dot cursor repository dot cursor directory actually. see dot cursors command this

[30:56] and you will actually check this into GitHub. So if other developer pulls this in they can just simply use this command to make similar code changes. In addition to commands you can add rules as well. So if you go here click on the

[31:14] cursor settings. Okay. So in cursor settings you will see a way to add rules and commands. So we already added this one command add structure logging but let's say I want to add a rule. So you click on it and you can add a custom

[31:29] click on it and you can add a custom rule. Okay. And you can give your rule rule. Okay. And you can give your rule name. So let's say my rule is backend name. So let's say my rule is backend API patterns

[31:42] and then it is adding this skill.md file in this uh skills directory. cursor is changing these things very fast. So it changing these things very fast. So it used to be cursor rules first then MDC

[31:55] then rule now skills but anyway the concept is same. So the difference between command and rule is that uh rule is more like traffic guidelines always stop when there is a red light drive below speed limits whereas command is

[32:10] more like the actual instructions. Okay. Uh when you put it on on your Google Uh when you put it on on your Google maps, okay, turn left, stop, uh take difference. Command is precise instructions whereas rules is just

[32:24] general guidelines. So if you look at that rules, right, there can be a project rule, there can be user rules, team rules, agents.md specifically for team rules, agents.md specifically for agents. Okay. So if you look at um let's

[32:38] say user rules, these are the these are your personal choices. You don't want to check into git. Okay. But these are the project rules which are applicable to all the programmers. So they all the programmers will find it useful and

[32:52] looks like they have recently changed the format. See previously you will have this kind of thing always apply means this rule will always apply. when you want to manually apply it uh you will have to say at and if you want to

[33:06] intelligently apply it then it will decide you know based on the description etc. You can also give a wild card so you can say globes let's say star.tsx or let's say /backend/star.py Pi in that case it will apply that rule

[33:21] Pi in that case it will apply that rule only for Py files. Okay. So here uh but recently. This is something new for me as well. It used to be rule now they're calling it skill. Okay fine. But the rules will look something like this.

[33:36] Okay. API endpoint structure use response model for type safety service response model for type safety service layer use async session. So whatever are the style guides, preferences, any legacy hacks, any architectural

[33:50] consideration that you want to make right see database query use select. It's like it's a junior programmer you are giving the instructor okay this is what you should do this is what you should not do okay so let's say if you

[34:03] don't want it to use uh sync calls you will say do not use sync always use general guidelines that you will embed in the rules and when cursor is writing the code it will always load these rules and it will use it. Let me show you some

[34:19] other cool features of cursor. When you type add you can refer to official documentation. So let's say I want to refer to fast API documentation. So I can click on docs and type in fast API and I can say okay add a timeout or

[34:35] whatever feature in my back end and it will refer to that documentation. Now this documentation is indexed in cursor environment but often time what happens is when you are working with AI to write code it may use the version of API that

[34:52] that is let's say outdated it might use let's say a version which was released 6 months ago okay so if you don't want that to happen let's say you want to use latest version you can use this uh

[35:04] documentation index or you can use an MCP server called context X7. So if I go MCP server called context X7. So if I go here and if I search for context 7

[35:16] here you will find all the API documentation latest see Nex.js documentation was updated uh only one day ago. Okay. So if you go to install day ago. Okay. So if you go to install here and if you type in cursor

[35:30] install in cursor the way you can do it is you just need to add this JSON object along with the API key. So you can create API key that's very easy into

[35:42] your uh go to cursor settingsite click on cog wheel cursor setting and by the way cursor folks are releasing features very fast so these menu options might change. Use your common sense tools and MCP and you add it here. See I have

[35:57] already added it here. So you can see that but context 7 and now I can say using context 7 right code whatever or you can add this

[36:10] instruction into your rules file. Remember it will always respect those rules. So in my rules file which is here I can say always use I can say always use context 7 for API documentation and it

[36:24] will use it. In this new world of AI first coding humans are still relevant. We are the orchestrators because LLM you can think about it as a genius engineer who joined the company 5 seconds ago. They know every programming language in

[36:39] the world but they know nothing about your business logic, legacy hacks, folders structure etc. And the cost of silence that you will pay is without you silence that you will pay is without you providing enough context it will uh

[36:52] default to the internet average producing code that is syntactically correct but architecturally invalid. It may not work in production. So you are trying to find a needle in a hashtag. Think about LLM as this huge brain which

[37:06] has vast amount of information, vast amount of reasoning power and you are targeting a specific area in that brain. And how do you target it? Well, by writing better prompt and when I say prompt, it is very comprehensive term.

[37:22] Actually prompt is not what you type in the AI chat in cursor. It is all the context. So when you say at documentation, what rules you are writing, the commands, the screenshot you're providing, see all of those

[37:35] things is going to matter and it will produce highly relevant output. Bigger context doesn't mean better answer. Relevance always beats the volume. So if you summarize our workflow, human versus LLM or rather human with LLM trying to

[37:53] build an application, the workflow is you give your business requirements, you give your business requirements, legacy hacks, architectural constraints and so on to LLM, your style guide for your company. It will write the code.

[38:06] You will validate the output. When I say validate output, you will not only validate the code, you will also run the code. You will see it is doing the thing. uh which you expect it to do and at this point folks rigorous uh

[38:20] automated testing becomes very much necessary. You can also use AI to write your test cases. Okay. So you need to have a huge or a proper test suite

[38:32] integration test uh unit test you need to have all of that. Okay. And then you will just repeat this loop. So your job is to give intent, context, constraint

[38:45] to LLM. It produces the output. You validate it. Code changes. You again validate it. Because when you ship the code to production, you can't say this code was written by LLM. Of course, it was written by LLM. But responsibility

[38:58] is on your shoulders. Okay. Thinking about anatomy of a perfect prompt. We saw three layers, right? Rules. Rules is like governance. Basically, traffic rules. Okay. Traffic rules are general guidelines. They are always applicable.

[39:12] So here persistent global instructions that define how the AI should behave and write code in every single interaction. They run in the background. Examples are always use TypeScript interface prefer functional programming over OP. Let's

[39:27] organization, you might have this guideline. So cursor is not going to know, right? So you have to give all these instructions in your rules file using cursor rules. If you're using claude, there is cloud.md file you can

[39:44] give it as a system prompt. Agent MD if you are building agentic application and so on. Then command is a second layer. It is like action. It is your actual GPS direction. Okay. So rules are general traffic rules. Always stop when there is

[39:59] red light. Drive below speed limit. These are global rules which always apply. Command is a specific journey. So I'm going from point A to B. My GPS is I'm going from point A to B. My GPS is saying turn right, stop, take the exit.

[40:14] So those are commands. Okay. Specific immediate instructions telling what to do. Okay. And the examples are refactor this code. We already generated that add logging structure logging command. So you know uh the way you can supply

[40:29] command is by saying slash. Okay. in cursor or by using the chat box. So even when you're typing something giving five-step instruction in AI chat box

[40:41] that is also a command. Okay. And the context is like your map data your coordinates your road intersection information exit information. You know Google map will have all this data. So that is your context. So here in terms

[40:53] of our our AI coding you will give relevant background. Okay. And how do you do it? Well you attest screenshot. We have looked at all this matter right we attach screenshots so that is the context you are giving we gave output

[41:07] trace okay you can say at output and you can refer to that trace you can uh refer to documentation MCP servers so by the way let me show you the output trace so here see I have these two terminals right u and node so when I said node see

[41:24] right u and node so when I said node see I can refer to this so it will go and it will read whatever whatever you have here. Okay, whatever you have here and where you can copy and take this context here again is gone with the new release.

[41:41] here again is gone with the new release. Okay, but you can give all these options. Okay, so see terminals, fast chats, folks explore all these options. Okay, files and folders, you can also give a specific folder. So for example,

[41:55] I want to refer to only my backend folder and only that will be in my context. Okay. So this is the three layer architecture folks. AI first coding. Okay. This is what the reality is. AI assisted coding is one thing but

[42:11] world is moving to AI first coding where you talk to AI through the prompts. And this is validated by the godfather of coding Lionus Torvals. He wrote Linux

[42:24] kernel, git version control system. He started using he's the best programmer in the world and he's saying that and he started using anti-gravity. Is this much better than what I could do by hand? Sure is. So he's validating that

[42:38] Sure is. So he's validating that anthropic released uh claude cowwork uh in in a matter of two weeks they wrote it and somebody asked okay did you use

[42:50] claude code to write code and this guy Boris Chenny he's the main person behind this product he said all of it all of this code is written by claude code folks AI first development is the approach that many companies have

[43:05] already adopted My friend is a staff engineer at one of the prominent fintech companies here in US. They have a huge monolith with thousands of lines of code and complex business logic. And he told me that in last 1 month 95% of the pull

[43:22] requests that he has created are completely written by claw code. He has not written any code with hand. I know this sounds powerful but scary at the same time. And I have created another video on how to tackle this approach.

[43:36] How to evolve your career in this changing time where you can become orchestrator, a builder and build things fast and contribute to company's growth. fast and contribute to company's growth. To conclude, if you are not using AI to

[43:51] write code, you are 100% missing out. And the question somebody might have is, is it going to make us dumb? The answer is yes. If you rely on it too much, if you don't review its changing, it's going to make us dumb. So, we need to

[44:05] review what it is producing uh use our brain to understand what it is doing. And I know when you do it again and again, it will be easy to miss out and we will let it go. Uh in which case, sometimes I think about this digital

[44:21] detox days, right? Like people who don't want to use their phone all the time or who have mental issues due to overusage of phone they have this digital detox day. Similarly there can be AI detox days where let's say every Friday I'm

[44:35] days where let's say every Friday I'm not going to use AI. I will write code with hand. Okay. But we have to find a right balance. We can't completely ignore this wave. We have to change as the technology as the world is changing.

[44:51] I hope you found this uh video to be useful. If you have any questions, please post in the comment box below. Bye-bye.