cursor-integrationlisted

# Cursor IDE + Claude Code Integration ## Purpose Maximize developer velocity by combining Cursor's low-latency editing (The Pilot) with Claude Code's autonomous agentic capabilities (The Agent). This skill defines the "Hybrid Workflow," manages context synchronization via file-based memory, and prevents conflicts between the two AI assistants. ## When to Use - Deciding between Cursor (Composer/Inline) and Claude Code (CLI) - Setting up project context (`CLAUDE.md` vs `.cursorrules`) - Resolving file lock/conflict issues between tools - Automating "background" tasks with Claude while editing in Cursor ## Examples **Example 1: The "Plan & Execute" Loop** ``` User: "How should I build this complex feature?" Claude: [Uses cursor-integration] Use the Hybrid Pattern: 1. **Claude Code (CLI)**: Run `claude --permission-mode plan "Architect feature X"` to generate `implementation-plan.md`. 2. **Cursor (Composer)**: Highlight the plan in Cursor and hit Cmd+I: "Implement the database schema section." 3. **Claude Code (CLI)**: Run `claude "Verify migration"` to test. ``` **Example 2: Background Worker** ``` User: "I need tests for this component but I'm busy coding" Claude: [Uses cursor-integration] Offload the testing while you code: 1. Continue writing `Component.tsx` in Cursor. 2. Open terminal: `claude "Watch src/components/Component.tsx and write a full test suite in __tests__"` ``` ## Domain Content ### 1. The Matrix: When to Use What | Task | Cursor (GUI) | Claude Code