Step 1: Install and Import Your Setup

Download Cursor from cursor.sh. On first launch, it asks if you want to import from VS Code. Click yes. Your extensions, themes, keybindings, settings, and snippets transfer in under a minute.

If you skip this step, go to Cursor Settings > General > Import from VS Code later.

Everything works immediately. Your muscle memory stays intact. The only difference: Cursor has AI features that VS Code doesn't.

Step 2: Choose Your AI Model

Open Cursor Settings (Cmd+, then search "AI") and configure your model preferences:

For inline completions: Cursor Tab (default) — optimized for speed, fires on every keystroke
For chat and Composer: Claude Sonnet 4 is the recommended default. Switch with Cmd+/ during any conversation
For complex reasoning: Claude Opus 4 — slower but dramatically better for architecture decisions and tricky bugs

Pro tip: use fast models (Sonnet) for 90% of tasks and switch to Opus only when you hit a wall. This stretches your monthly quota significantly.

Step 3: The 7 Shortcuts That Change Everything

You don't need to memorize 50 shortcuts. These 7 cover 90% of daily AI interactions:

1. Cmd+K — Inline Edit

Select code, press Cmd+K, and describe what you want. "Add error handling" or "Convert to async/await" or "Make this function generic." Cursor edits the selected code in-place and shows a diff. Accept or reject.

This is your most-used shortcut. It replaces manual editing for any transformation you can describe in words.

2. Cmd+L — AI Chat

Opens the chat panel. Ask questions about your code, get explanations, request code snippets. Use Cmd+Shift+L to add your current selection to the chat as context.

3. Cmd+I — Composer

Composer is Cursor's multi-file editor. Describe a feature or change and Composer edits every relevant file. "Add a dark mode toggle to the settings page" might touch 5 files — the component, the store, the CSS, the layout, and the settings route.

Review each file's diff before accepting. This is where Cursor saves the most time.

4. Cmd+Shift+A — Agent Mode

Agent mode is Cursor's autonomous mode. Unlike Composer, the Agent can read additional files, run terminal commands, install packages, and iterate. Describe a complex task and let it work.

Best for: "Set up ESLint with our team's config," "Add comprehensive tests for the auth module," or "Refactor the data layer to use React Query."

5. Cmd+/ — Switch Models

Instantly switch between Claude Sonnet, Claude Opus, GPT-4o, or other available models. Use during any chat or Composer session when you want a different perspective or more reasoning power.

6. Tab — Accept Suggestion

The simplest and most used. Cursor shows ghost-text suggestions as you type. Tab accepts. Esc dismisses. The suggestions improve over time as Cursor learns your patterns.

7. @ Mentions — Give AI Precise Context

In any chat or Composer input, type @ to reference specific context:

@Files — "Look at this specific file." Use when the AI needs to see a related module.
@Codebase — "Search my entire project." Use for questions about architecture or finding related code.
@Web — "Search the internet." Use for library docs, API references, or current best practices.
@Docs — "Check the documentation for [library]." Cursor indexes popular docs (Next.js, React, Stripe, etc.).

The difference between a good AI response and a bad one is almost always context. @ mentions let you control exactly what the AI sees.

Step 4: Create Your .cursorrules File

Create a .cursorrules file in your project root. This is Cursor's equivalent of a style guide that the AI actually follows.

Every time Cursor's AI makes a suggestion, it reads this file first. Without it, the AI guesses your conventions and often guesses wrong. With it, the AI generates code that matches your team's standards from the first suggestion.

Start simple and add rules as you notice the AI making repeated mistakes. If it keeps suggesting var instead of const, add a rule. If it uses the wrong test framework, add a rule. Over time, your .cursorrules becomes a living document of your project's coding standards.

Step 5: Optimize Your Workflow

The 80/20 Rule of AI-Assisted Coding

After watching hundreds of developers use Cursor, here's the pattern that works best:

80% of the time: Use Tab completions and Cmd+K inline edits. Fast, focused, low overhead.
15% of the time: Use Composer (Cmd+I) for multi-file changes. Review each diff carefully.
5% of the time: Use Agent mode (Cmd+Shift+A) for complex autonomous tasks. Give it clear instructions and verify the output thoroughly.

Common Mistakes to Avoid

Don't accept code you don't understand. AI-generated code that works but you can't debug is a liability. If a suggestion looks unfamiliar, ask the AI to explain it first (Cmd+L).

Don't give vague prompts. "Fix this" tells the AI nothing. "This function throws a null reference error when the user object is undefined — add a guard clause" gets you the right fix immediately.

Don't skip the diff review. When Composer or Agent edits multiple files, read every diff. The AI occasionally makes well-intentioned changes to files you didn't intend to modify. Catching these early saves hours of debugging later.

You now have a fully configured Cursor setup. In the next lesson, we'll add GitHub Copilot and Claude Code to your stack — and learn exactly when to reach for each tool.

Setting Up Cursor for Maximum Productivity

Related Resources