Cursor Mastery — The AI-First Code Editor

Week 1 — meet the tool, get an account, and learn the screen before you learn the prompting.

1. Meet Cursor — what it is and who makes it

   Cursor is Anysphere's code editor built around an assistant that can edit across your whole project. It is at its best at a change that touches several files at once — a rename, a new endpoint, a refactor you described in a sentence. It is at its weakest at knowing what you actually wanted: it will carry out an instruction precisely and to the wrong end — and knowing both halves is what separates somebody who uses it well from somebody who trusts it blindly.

   The lesson

   Cursor is a code editor built around an assistant that can edit across your whole project made by Anysphere. The models behind it are a choice of frontier models, selected per request so you can trade speed against quality. None of that matters on its own — what matters is that you know what kind of worker you have hired. At a change that touches several files at once — a rename, a new endpoint, a refactor you described in a sentence is the job you hand it. At knowing what you actually wanted: it will carry out an instruction precisely and to the wrong end is the job you keep.

   Most people come to a course like this expecting a list of magic words. There is no such list. What there is, is a tool that produces edits applied directly to your files, with a diff you review before accepting, and produces it at a speed no human matches — which means the skill is not in writing the prompt, it is in knowing what a good answer looks like so you can tell the difference.

   Here is the first thing to try, worded the way you will word things for the rest of the course:

   PromptCopy

   Here is a project I did not write. Tell me where the entry point is, what happens when it starts, and which three files I should read first to understand it — and say if you are unsure.

   Read the answer twice. The first read is for the content; the second is for the shape — did it answer the question you asked, or the question it found easiest? That second read is the habit this whole course is built on.

   Example The last clause matters: an honest "I am unsure" about an unfamiliar project is more useful than a confident wrong map.

   Practice Open Cursor, ask it the one question you would normally put to a search engine about your own field, and write down two things: whether the answer was right, and whether it would have taken you longer to find it yourself.

2. Signing in: what is free, what is paid, and what you actually need

   You do not need the paid plan to finish this course. Start on the free tier — there is a free tier with a monthly allowance of the faster model requests, which is enough to learn the workflow. Upgrade only when you hit a wall you can name: a longer file, a newer model, or a rate limit you keep meeting.

   The lesson

   Every one of these tools has a free tier that is good enough to learn on and a paid tier that removes a limit. the paid plan unlocks the larger models and the agent modes that run for longer. The mistake is buying the paid plan in week one, before you know which limit you hit — you end up paying to remove ceilings you were never going to touch.

   Work out your own honest usage first. How many questions a day do you actually ask? How big are the files you upload? Do you need the newest model, or the fast one? For revision, for drafting, for coursework, the answer is usually the free tier.

   If your college or workplace provides an account, use it: a team plan with privacy controls that keep the code out of model training is how most people in a job get access, and asking your placement cell whether one exists costs nothing.

   Example The free tier will carry you through this whole course; the paid tier matters when you are working in it every day.

   Practice Create the account, find the plan page, and write down in one line which limit you would hit first in your own week. It is usually a message cap or a file-size cap, not the model.

3. The screen: where every control lives

   A tour of the interface you will live in — a familiar editor, plus a chat panel, an inline edit mode, and an agent mode that changes many files at once and shows you the result as a diff. Every panel has a reason to exist, and half of them are the difference between a chat and a system.

   The lesson

   The interface of Cursor is a familiar editor, plus a chat panel, an inline edit mode, and an agent mode that changes many files at once and shows you the result as a diff. That sentence is worth slowing down on, because the single biggest cause of bad output is not a bad prompt — it is a good prompt typed into the wrong place.

   The history list is your memory of what worked. Name your conversations. The temporary or private mode is for anything you would not want in an account's history. The settings panel holds the personal instructions that apply to everything, which is where your context belongs rather than repeated at the top of every message.

   Do this once, properly: make the same small change twice — once with inline edit, once with the project-wide agent — and notice the difference in how much you had to re-read afterwards. It takes fifteen minutes and saves you those fifteen minutes every week after.

   Example Inline edit is for one selection; the agent panel is for a change across the project. Choosing the wrong one is where most wasted time lives.

   Practice Spend fifteen minutes doing nothing but clicking. Open every panel, rename one conversation, and save one setting you will want again. Fluency with the screen is what stops you re-explaining yourself every session.

Week 2 — how Cursor reads text, the four-part prompt, your own work, and what to do when the answer is wrong.

1. How Cursor reads what you type

   Context, instructions and roles. It indexes the whole project, so it can follow your own naming and structure, and you can point it at specific files to keep it narrow. Understanding what the model can see — and what it has already forgotten — explains almost every disappointing answer you will get.

   The lesson

   It indexes the whole project, so it can follow your own naming and structure, and you can point it at specific files to keep it narrow. This is the machinery. A model does not remember your last conversation the way a person does; it is handed text and asked to continue it well. Everything you want it to know has to be in that text, in the same window.

   There is a difference between a system instruction — the standing context, set once — and a message, which is this request. Put your standing context in the standing place. "I am a final-year mechanical engineering student applying for data roles" belongs in your profile, not typed again at the start of every chat.

   And there is a hard limit. When a conversation gets long enough, the earliest turns fall out of view. Symptoms: it contradicts an instruction you gave ten messages ago, or forgets the file you uploaded. The fix is a new conversation with a written summary of where you got to, not a longer argument.

   Example Ask it to add a field to a model and it will also find the form, the schema and the tests — because it can read all of them, and because you told it the whole job.

   Practice Ask the same question twice: once on its own, once after a short paragraph of setup about who you are and what you need. Compare the two answers and write down the difference. That gap is the thing you are learning to control.

2. The four-part prompt: role, task, context, format

   Almost every good prompt has four parts: who the model should be, what it must do, the facts it must use, and the shape of the answer you want. Leave out the fourth and you get an essay when you wanted a table.

   The lesson

   Write the four parts as four lines, in this order. ROLE: who it should answer as. TASK: the single thing you want done, as an instruction, not a wish. CONTEXT: the facts, pasted, not referred to. FORMAT: the exact shape of the answer — "a table with three columns", "five bullets, no more than twelve words each".

   FORMAT is the part everybody skips and the part that saves the most time. An answer you have to restructure by hand was not really an answer. Ask for the shape you are going to use: if it is going into a slide, ask for slide bullets; if it is going into a spreadsheet, ask for rows.

   Here is the same request done both ways — first as people usually write it, then in four parts:

   PromptCopy

   Weak:  tell me about data analyst jobs
   
   Strong:
   ROLE:    A hiring manager for entry-level analytics roles in India.
   TASK:    List what you screen for in a fresher's first 30 seconds.
   CONTEXT: I am a 2026 B.Com graduate with Excel, basic SQL and one
            dashboard project. No internship yet.
   FORMAT:  A table: skill | what a fresher shows | what most get wrong.
            Five rows maximum. No introduction.

   The second prompt is not longer because long is good. It is longer because it contains four things the model cannot guess, and the guess is where the useless answer came from.

   Example "Change only the files needed for X, and list every file you touched" is the instruction that makes a multi-file edit reviewable.

   Practice Take a task you did last week without AI and write the prompt in four labelled lines. Then run it, and rewrite only the part that failed — not the whole prompt.

3. Cursor for the work you actually have

   Assignments, revision, email, applications, meeting notes. A new endpoint added across the router, the service and the tests in one pass; a rename that actually catches every reference. The test of a tool is whether it removes an hour from your week, not whether the demo looked clever.

   The lesson

   The highest-value use of Cursor for a student or a fresher is not writing essays. It is compression: turning a 40-page chapter into the six things you actually have to remember, turning a messy set of notes into a revision sheet, turning a job description into a list of what to prove.

   The second highest is structure: given a blank page, ask for three possible outlines and pick one. Being stuck is usually a problem of options, not of effort.

   Here is a prompt worth keeping verbatim — it is the one that turns a document into something you can study:

   PromptCopy

   Add a "preferred location" field to the candidate profile.
   
   Requirements:
   - update the model, the profile form, the API response and the tests
   - do not rename anything that is already in use elsewhere
   - keep the existing naming style
   
   When you are done, list every file you changed and why, and tell me
   anything you were unsure about and chose anyway.

   Notice the last line. Asking for the gaps is asking the tool to mark its own work, and it is the single most useful line you can add to a study prompt: the material it could not summarise is the material you have not understood yet.

   Example Describe a cross-cutting change and ask for the smallest set of files, with the list of what it touched.

   Practice Pick the one task you repeat every week — the one that is boring rather than hard — and rebuild it in Cursor today. Time it. Then keep the prompt that worked, saved and named.

4. When the answer is wrong: iterate instead of restarting

   A bad answer is information. Its failure is doing exactly what you said across ten files, when what you said was not quite what you meant. Keep the conversation, name the fault, and correct one thing at a time — restarting from scratch throws away everything the model has already got right.

   The lesson

   There are four things that usually went wrong, and each has a different fix. It answered a different question — restate the TASK as one sentence. It made things up — supply the facts yourself and say "use only these". It wrote too much — ask for the length first. It sounded like a machine — ask it to rewrite for one specific reader and cut every third word.

   Say the fault out loud, in the message. "This is too long for a WhatsApp message and it sounds like a brochure." A model cannot fix a problem you have not named, and naming the problem is also how you find out what you actually wanted.

   Follow-ups that work: "shorter", "only the parts that are true for a fresher", "rewrite the second sentence three ways", "what would you have to check before I send this?". That last one is worth using before anything goes out with your name on it.

   Example A vague request like "clean up the auth code" produces a large diff you will not review properly. Ask for one change at a time, and for the list of files.

   Practice Take the worst answer you have received this week and correct it in three follow-up messages without retyping the original prompt. Notice how much faster it converges.

Week 3 — documents and tables, Project-wide edits with a reviewable diff, the API, and one boring task automated.

1. Files, tables and long documents

   Uploading a PDF, a spreadsheet or a screenshot and asking questions about it: It reads and writes the files in the project you opened, which is the whole difference from a chat window, and the whole reason to review diffs. This is where these tools stop being a chat and start being work, and where the failure modes are worth knowing.

   The lesson

   It reads and writes the files in the project you opened, which is the whole difference from a chat window, and the whole reason to review diffs. The two failures to expect are the ones nobody warns you about: a long document is summarised as it is read, so a detail on page 60 can be missed; and a table with merged cells or a scanned page is likely to be read wrongly.

   So the working method is: ask narrow questions, and ask the tool to quote the line it is answering from. "From the attached file only, what does clause 4.2 let me do? Quote the sentence." If it cannot quote it, it did not read it.

   For a spreadsheet, ask for the formula and an explanation instead of the computed column — ask which file defines the type before letting it change an expression — then you can fix it yourself next month when the columns change.

   Example Open a project you did not write, ask what the entry point is and what it does, and it will answer from the actual code rather than a guess.

   Practice Upload one real document you already own — a syllabus, a marksheet, a project report — and ask three questions whose answers you already know. When it gets one wrong, read the passage it quoted before you blame the file.

2. Project-wide edits with a reviewable diff — Cursor's own feature

   The agent can change several files in one instruction and show you the result as a diff before it is applied. That combination — reach and review — is the feature. Take away either half and it is either useless or dangerous.

   The lesson

   Because the jobs that take the longest are the boring mechanical ones — a rename, a new field, a moved function — and they are exactly the jobs an assistant with project-wide reach does best. The review step is what keeps it safe, and it is not optional.

   Write the request as a specification: what changes, what the constraints are, what must not change. Then read the diff, file by file, before accepting anything. Run the tests. Commit with a message that says why. If the diff is larger than you expected, stop and undo.

   Here is the shape of it, in the form you will actually use:

   Plain textCopy

   // Before asking the agent for anything, write the specification.
   //
   // CHANGE:     rename "phone" to "phoneNumber" everywhere it is a field.
   // CONSTRAINTS: 
   //   - do not rename the database column (a migration is out of scope)
   //   - keep the API response key as "phone" so existing clients still work
   //   - update every test that references it
   // REVIEW:     list every file changed, and flag any place where the rename
   //             was ambiguous — for example a local variable called phone
   //             that is NOT the field.
   
   // The last line is the important one. Ambiguity is where an agent silently
   // makes a decision you did not ask for and cannot easily find afterwards.

   The mistake is accepting a fifty-file diff because the tests passed. Tests cover what they cover; an unintended rename in a file nobody tests will surface in production, not in your build.

   Example One instruction adds a field end to end: the schema, the form, the validation, the response and the test. You then read the diff rather than hunting for the places you forgot.

   Practice Do one real cross-cutting change through the agent: rename a field that appears in five files, review the diff, run the tests, and commit. Then count how many places you would have missed by hand.

3. Editor integrations and your own tooling and your first script

   The editor is a product rather than an endpoint, and the pattern worth copying from it — give a model the project, take back a diff — is what you build on any provider API. You do not need this to finish the course, and you do not need it for a fresher job either — but an afternoon here is what turns "I have used Cursor" into "I have built with it", which is a different sentence in an interview.

   The lesson

   The editor is a product rather than an endpoint, and the pattern worth copying from it — give a model the project, take back a diff — is what you build on any provider API. The idea is simple: the same model you have been chatting with also answers a web request, so you can put it inside a script, a spreadsheet or a page. A key identifies you; a request sends the text; a response comes back as data.

   The reason to try it once, even if you never build anything: it makes the chat version less mysterious. You see that the whole conversation is text in and text out, that your instructions are literally lines of a request, and that "the model" is one parameter among several.

   A first call looks like this:

   TerminalCopy

   # The habit this course is really about, in one line:
   #
   #   describe the change  ->  read the diff  ->  run the tests  ->  commit
   #
   # With AI in the middle it becomes:
   #
   #   describe the change  ->  the assistant proposes a diff
   #                        ->  YOU read the diff
   #                        ->  you run the tests
   #                        ->  you commit with a message saying why
   #
   # The two steps that stayed yours are the two that matter.

   The mistake is letting the assistant commit. Read the diff and write the message yourself — the commit history is the record of your judgement, and it is what a reviewer reads first.

   Example A script that takes a code file and returns a reviewed version with comments is a small but honest demonstration that you understand the pattern under the editor.

   Practice Get a key, run one request that works, and change one word in it to see the answer change. That is the whole of the first afternoon.

4. Automate one boring task with Cursor

   Automation is not about building a system. It is about doing one repetitive job the same way every time, in less time than last time, and being able to do it again next month.

   The lesson

   Pick the task by how often it happens, not by how impressive it would be. A weekly report you can half-generate beats a clever pipeline you build once and never open again.

   Generating the boilerplate that repeats in every project — a new endpoint, a component, a test file — from a specification you keep in the repository.. Whatever you choose, write the steps back out in plain English afterwards — "Step 1, open the sheet, Step 2, paste the names —" because the written steps are what you follow when the tool changes next quarter.

   And keep a copy of the prompt next to the task. A prompt that lives only in your chat history is a prompt you will rewrite from scratch in March.

   Example A specification file at the top of a project means every new piece of work starts from the same written standard, and the assistant follows it.

   Practice Name the task you repeat most often that involves typing, then write the prompt for it and run it three weeks in a row from the same saved place. Three runs is the point at which you know whether it is genuinely automated.

Week 4 — a finished portfolio project, the privacy rules, the limits, and the Anysphere certification paths.

1. Build the portfolio project: a small application built with the assistant, reviewed by you

   Build something small but complete — a tracker, a tool, a small site with a backend — using project-wide edits for the boring parts and your own hands for the logic. It is the thing you will talk about in the interview, so it has to be small enough to finish in a fortnight and concrete enough to show a person in one minute.

   The lesson

   Build something small but complete — a tracker, a tool, a small site with a backend — using project-wide edits for the boring parts and your own hands for the logic. Finish it before you start the next one. A half-built idea shows nothing; a small finished thing shows that you can finish.

   Use the tool as a collaborator, not an author: ask it for a plan, a critique and a checklist, and write the work yourself. In the interview the questions will be about the decisions — why this, why not that — and only the work you did yourself has answers.

   Write one paragraph beside the project: what problem it solves, what you used, and what you would do differently next time. That paragraph is the interview.

   Example Finished, it is a working application, a clean commit history, and a note of the one change the agent made that you rejected and why.

   Practice Explain your commit history to somebody: for each one, what changed and why. That walkthrough is the interview.

2. Ethics, privacy and what never to paste

   These tools send what you type to somebody else's computer and keep it in a history. Never paste passwords, government ID numbers, bank or card details, medical records, or another person's private data — and never paste a company's confidential document.

   The lesson

   There is no version of this tool where your text stays on your laptop. Everything you type is sent to a server, kept in a history you can usually see, and may be reviewed or used to improve the product depending on the plan.

   Before installing anything, check your .gitignore covers your secrets, and prefer a plan whose terms keep your code out of training. On a work project, use the account your employer has approved rather than your personal one.

   The practical rule for a fresher: replace the real thing with a stand-in. "Client A", "my friend's phone number", "the amount in the offer letter". The tool rarely needs the real value to do the work, and the stand-in costs you nothing.

   And the professional rule: an unpublished repository does not go into a personal account with training enabled. If your employer has an approved plan or a policy, that policy is the answer, not your judgement about how sensitive a file really is.

   Example An assistant with access to your project sees every file in it, including the one with the credentials you meant to move later.

   Practice Go through your last five conversations and delete anything containing a real phone number, a client name, or a document you did not write. If you cannot find the delete button, that is the lesson.

3. Limits, hallucinations and how to check

   These tools predict plausible text. It is precise about carrying out the instruction and has no idea whether the instruction was a good idea That is a mechanism, not a moral failing — and the habit it demands is the habit of asking "where did this come from?" out loud, every time, before you use an answer.

   The lesson

   A model does not look things up unless it has been given a way to look things up, and even then it can attach a real number to the wrong claim. It is precise about carrying out the instruction and has no idea whether the instruction was a good idea

   So the rule is: numbers, dates, names, citations and legal or medical claims get checked in a primary source before they leave your hands. Everything else — drafts, structure, explanations, practice — is fair game.

   Three questions to ask before you trust an answer. Where did this come from? What would make it false? Who is the original source, and can I open it? If the third one has no answer, you have writing material, not facts.

   Read the diff, run the tests, and check one behaviour by hand. Three checks, in that order, every time.

   Example Ask it to make a change that would break an invariant in your system and it will do it correctly. Only your review catches that, which is why the review is the course.

   Practice Ask for one statistic with its source, then open the source. Sometimes it exists. Sometimes the citation is invented, and the number is close enough to a real one to be dangerous. Either way you will remember the exercise.

4. Get certified: the official Anysphere paths

   A Way2Fresher certificate for this course is free and lives on this site. Beyond it, Anysphere publishes its own learning and certification material — and the rail on this course page links to it.

   The lesson

   There are two things called a certificate and they are not the same. The one this site issues records that you finished a structured course and built the project at the end of it — it is free, and it is yours to print. The ones Anysphere issues record that you passed their own material.

   The editor's own documentation and tutorials are the honest starting point, and there is no certification for it. The portable credential in this area is a general developer certificate — GitHub Foundations, or a cloud developer path — supported by a repository that shows the work.

   Get both, in that order. The project is what an interviewer asks about; the certificate is what gets past a filter that looks for keywords. The links to the official paths are in the rail beside this lesson, each labelled with who issues it.

   And put the work on the certificate, not the other way round: a certificate with no project behind it is a line on a resume, and it lasts exactly until the first technical question.

   Example Describe one change you made across five files, why each file needed it, and what you rejected. That is the answer a technical interview is looking for.

   Practice Finish every lesson here, take your Way2Fresher certificate, then open one official path and work through it with the project you have already built. Being certified in the tool you can already use is a small additional step.