Cursor Setup Guide

Complete guide to integrating Bootspring with Cursor, the AI-powered code editor.

Overview#

Cursor is an AI-enhanced code editor built on VS Code. Bootspring complements Cursor by providing:

  • Structured Context - CLAUDE.md enhances Cursor's understanding
  • Expert Agents - Specialized assistance beyond general AI
  • Skill Patterns - Production-ready code patterns
  • Development Workflows - Multi-phase orchestration

Prerequisites#

  • Cursor installed (cursor.sh)
  • Bootspring CLI installed (npm install -g bootspring)
  • Node.js 18+ installed

Installing Cursor#

macOS#

Loading code block...

Windows#

Download from cursor.sh and run the installer.

Linux#

Loading code block...

Bootspring Integration#

Step 1: Initialize Bootspring#

Loading code block...

This creates:

  • CLAUDE.md - Context file (Cursor reads this)
  • bootspring.config.js - Configuration
  • .bootspring/ - Local data

Step 2: Cursor Reads CLAUDE.md#

Cursor automatically indexes your project, including CLAUDE.md. This provides:

  • Project architecture understanding
  • Coding standards and patterns
  • Tech stack details
  • Custom instructions

Step 3: Configure Cursor Rules#

Create .cursorrules to reference Bootspring context:

# Cursor Rules ## Project Context Refer to CLAUDE.md for complete project context, architecture, and coding standards. ## Code Generation - Follow patterns defined in CLAUDE.md - Use the tech stack specified in project context - Match existing code style ## When Uncertain - Check CLAUDE.md for project-specific guidance - Follow the architecture described in context - Use established patterns from the codebase

Syncing Context#

Context in CLAUDE.md#

Bootspring generates comprehensive context:

Loading code block...

Regenerate After Changes#

Loading code block...

Git Hook#

Auto-generate on commit:

Loading code block...

Using Both Together#

Cursor for Quick Edits#

Use Cursor's built-in AI for:

  • Line completions (Tab)
  • Quick edits (Cmd+K)
  • Simple questions (Cmd+L)

Bootspring for Complex Tasks#

Use Bootspring CLI for:

  • Expert agent consultations
  • Production pattern application
  • Multi-phase workflows
Loading code block...

Terminal Integration#

Cursor Terminal#

Cursor includes an integrated terminal. Use Bootspring directly:

Loading code block...

Completions#

Add to your shell profile:

Loading code block...

Composer Integration#

Using Composer with Context#

When using Cursor's Composer (Cmd+I):

  1. Composer reads your CLAUDE.md
  2. Uses project patterns for generation
  3. Follows your coding standards

Reference Bootspring Context#

In Composer prompts:

Create a new API endpoint following the patterns in CLAUDE.md for user preferences.

Add Context References#

@CLAUDE.md Create a form component following our established patterns.

Custom Commands#

Cursor Command Palette#

Create .vscode/tasks.json (Cursor uses VS Code format):

Loading code block...

Run via: Cmd+Shift+P → "Tasks: Run Task"

Keyboard Shortcuts#

Cursor Shortcuts#

ShortcutAction
Cmd+KInline edit
Cmd+LChat panel
Cmd+IComposer
Cmd+Shift+LAdd to chat

Custom Bootspring Shortcuts#

Add to Cursor keybindings:

Loading code block...

Settings Synchronization#

Cursor Settings#

.vscode/settings.json:

Loading code block...

Bootspring Settings#

bootspring.config.js:

Loading code block...

Workflow: Cursor + Bootspring#

Feature Development#

  1. Plan with Bootspring

    Loading code block...
  2. Design phase - Bootspring agent provides architecture

  3. Implement in Cursor - Use Composer for code generation

  4. Apply patterns

    Loading code block...
  5. Quality check

    Loading code block...
  6. Commit - Context auto-updates

Code Review#

  1. Run security review

    Loading code block...
  2. Fix issues in Cursor - Use Cmd+K for inline fixes

  3. Verify with quality check

    Loading code block...

Cursor Rules Best Practices#

Reference CLAUDE.md#

# .cursorrules Always check CLAUDE.md for: - Project architecture and patterns - Tech stack and dependencies - Coding standards and conventions - Component structure guidelines When generating code: 1. Read CLAUDE.md first 2. Follow established patterns 3. Match existing code style 4. Use project's preferred libraries

Project-Specific Rules#

# .cursorrules ## Component Structure - Use Server Components by default (see CLAUDE.md) - Client Components only for interactivity - Follow naming conventions in project ## API Routes - See patterns in CLAUDE.md - Use Zod for validation - Handle errors consistently ## Testing - Jest + React Testing Library - Follow test patterns in __tests__/

Troubleshooting#

Context Not Updating#

Loading code block...

Cursor Not Reading CLAUDE.md#

  1. Check file exists: ls CLAUDE.md
  2. Verify it's not gitignored
  3. Reload Cursor window
  4. Re-index project: Cmd+Shift+P → "Cursor: Re-index"

Terminal Commands Failing#

Loading code block...

Conflicting AI Suggestions#

If Cursor's suggestions conflict with Bootspring patterns:

  1. Update .cursorrules to reference CLAUDE.md
  2. Be explicit about pattern preferences
  3. Use Bootspring for complex generation

Performance#

Optimize Context Generation#

Loading code block...

Cursor Indexing#

Cursor indexes your project. Large contexts may slow indexing:

  • Keep CLAUDE.md focused
  • Use .cursorignore for large files
  • Exclude generated content

Extensions#

Install via Cursor's extension panel:

ExtensionPurpose
ESLintCode quality
PrettierFormatting
Tailwind CSS IntelliSenseTailwind support
PrismaDatabase schema

Extension Settings#

Loading code block...

Next Steps#