This is a real guide, generated for an example user. Yours is built from a short interview about how you actually work — your saved prompts, your projects, your do-not-break workflows. Free during beta.
How to move from Cursor to Claude Code.
A step-by-step guide to move Cursor workflows into Claude Code — copy-ready, checkable, and checked against each tool’s own docs.
- Prepared for
- An example 3-person marketing team
- Sources
- 7 verified sources
6 steps, 4 paste-ready assets, 10 to confirm in Claude Code.
- Project rules in .cursorrules
- Agent multi-file edits (Composer)
- Codebase-aware chat (@files / @codebase)
- Terminal command generation
Setup steps
Work through these in order. Check each off as you go; your progress is saved on this device.
Install the Claude Code CLI, then add the Claude Code VS Code extension into your existing Cursor install via Open VSX — the docs explicitly list Cursor as supported. This gives you the cleanest "use both" path: keep Cursor's editor chrome and Tab autocomplete while getting Claude Code's agent loop, inline diffs, plan mode, and checkpoints in a side panel. Run `claude` once in the integrated terminal to authenticate against your Anthropic plan, then use the `/ide` command to share editor state. As a senior engineer you'll want both surfaces side-by-side during the transition rather than ripping Cursor out on day one.
Vscode extension ideTerminal shell access
A few things to confirm
We flag these up front so nothing surprises you — a short list to double-check in Claude Code as you go.
- 10 items are flagged to confirm in Claude Code — check the menu paths and field names as you go.
- Note: all guidance here is grounded in provisional FPM patterns (every cited node/pattern is marked provisional), so verify each step in the actual UI as you go.
Paste-ready assets
Workflows from Cursor, rewritten to paste straight into Claude Code.
.cursorrules (encoding style, frameworks, do/don'ts)
# Project conventions (Claude Code memory) > Ported from `.cursorrules`. Place at repo root as `CLAUDE.md`, or save as `AGENTS.md` so both Cursor and Claude Code read it. ## Stack - Language/runtime: Node + TypeScript. Assume strict TS. - Editor environment: VS Code / Cursor fork. - VCS: GitHub. Conventional Commits for messages. ## Voice & how to work with me - I am a senior engineer. Be direct. Skip preamble, skip flattery. - Propose a short plan before any multi-file change; wait for approval in Plan mode. - Show diffs per-hunk; do not auto-apply sweeping refactors. ## Do - Match existing file/module structure and naming. - Keep changes minimal and reviewable; small, coherent commits. - Add/adjust tests alongside non-trivial logic changes. - Prefer existing utilities over new dependencies. ## Don't - Don't reformat unrelated files or churn whitespace. - Don't introduce new frameworks/libraries without flagging the tradeoff first. - Don't swallow errors; surface and type them. ## Notes on tooling - Use Glob/Grep/Read to discover context instead of assuming layout. - Run lint/typecheck/tests via the integrated terminal before declaring done.
Same-day walkthrough
This sample was built for an example user. Yours gets built around how you work.
A 15–25 minute interview captures your workflows, then the guide is generated for you — same structure, your prompts, your projects, your gotchas. Nothing in your stack is changed or cancelled by any of it.