Cursor
Editor-native AI: set your rules once, keep the docs current, review every diff, and stay in control of the code it writes.
Cursor Rules: Set It Once
How to write a Cursor Rules file once so Cursor applies your coding standards to every prompt, instead of you re-explaining them each time.
Tip #029Feed Cursor Live Docs
How to use Cursor’s docs feature to index live documentation so it stops guessing outdated syntax for libraries and APIs.
Tip #030Restore Checkpoint: Your Undo Button
How Cursor’s restore checkpoint feature lets you revert an AI agent’s edits back to before a bad change happened, without manually undoing anything.
Tip #209Index Your Codebase First
Cursor indexes your codebase before it can answer questions about the whole repo — how to check indexing in Settings → Features → Codebase Indexing, and why whole-project prompts fail until it finishes.
Tip #210Write Terminal Commands In Plain English
Use Cursor’s terminal inline-edit shortcut to describe a shell command in plain English, get the real command back, and read it before you run it.
Tip #211Step The Diff With Review Next File
How to use Cursor’s Review Next File button to walk an agent’s changes one file at a time and accept each diff on purpose, instead of hitting Accept All blind.
Tip #212A.I. Can’t Fix What You Can’t Diagnose
Why an AI agent can ship a version-breaking bug without knowing it, and how learning enough of your own stack turns you into the backstop that names the fix.
Tip #213Prompt Your Editor Config
Open settings.json or keybindings.json, trigger the inline AI edit, and describe the change in plain English — the AI writes the correct config key so you never hunt through the settings UI again.