📊 We use cookies & analytics to improve your experience. Learn more
Latest

Cursor Mastery — The AI-First Code Editor Module 3 · Lesson 8 of 15

0% Exit to course

Module 3 · Files, tools and your own data Lesson 8 of 15

Files, tables and long documents

Learning objective

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 concept

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.

Worked 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.

Your practice task

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.

Do this before moving on. Reading a solution teaches the shape of it; typing it teaches you.

Key takeaway

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.

Create free account or sign in

Almost there

15 lessons left of 15

Finish every lesson to unlock the certificate. Each one ends in a practice task — do them and the final project brief writes itself.