Stage 2 of 10 · 6 lessons · ~1 week

Setup and project context

Install your tool in a real repository, write a short instructions file it loads every session, add scoped rules, keep secrets out of its reach and learn to point it at exactly the right files.

Start: Installing Cursor and opening a project

Lessons· one lesson for each topic, in this order

Do this

Install your tool and start it from the root of a real project.
Draft the instructions file with the built-in command, then cut it to the lines that change behaviour.
Add one scoped rule for a folder or file type and check it loads.
Block .env and key files from the tool, and confirm .env is in .gitignore.
Do one small task using precise file references instead of a description.
Commit the instructions and rules so your future self and teammates get them.

Start with

GuideFree
Cursor Documentation
Anysphere
Work through the quickstart, then the Rules and Ignore file pages

Keep handy

AGENTS.md
The shared format your tool can read, with examples of what to put in it

Also worth your time

Rules (opens in a new tab)Read
Project, user and team rules, the .mdc format and rule-writing best practices
Effective Context Engineering for AI AgentsGo deeper
Why context is the scarce resource for agents, and how to curate it

Before moving on: Cursor open on your project root, one always-applied .mdc rule and one glob-scoped rule in .cursor/rules, secrets covered by .gitignore and .cursorignore, and a first task done with @ file references.

Tauseef's advice

Treat the instructions file like code: short, accurate and reviewed. Every time the tool makes the same mistake twice, add one line; every time a line stops mattering, delete it. And set up secret handling before the first session, not after the first leak.