playbooks

home / skills / jeremylongshore / claude-code-plugins-plus-skills / cursor-multi-repo

cursor-multi-repo skill

/plugins/saas-packs/cursor-pack/skills/cursor-multi-repo

This skill helps you manage multiple repositories in Cursor, enabling cross-project context, selective indexing, and unified workspace workflows.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill cursor-multi-repo

Review the files below or copy the command above to add this skill to your agents.

Files (6)
SKILL.md
1.8 KB
---
name: "cursor-multi-repo"
description: |
  Manage work with multiple repositories in Cursor. Triggers on "cursor multi repo",
  "cursor multiple projects", "cursor monorepo", "cursor workspace". Use when working with cursor multi repo functionality. Trigger with phrases like "cursor multi repo", "cursor repo", "cursor".
allowed-tools: "Read, Write, Edit, Bash(cmd:*)"
version: 1.0.0
license: MIT
author: "Jeremy Longshore <[email protected]>"
---

# Cursor Multi Repo

## Overview

This skill guides you through working with multiple repositories in Cursor. It covers multi-root workspaces, monorepo patterns, selective indexing strategies, and cross-project context management for complex development environments.

## Prerequisites

- Multiple repositories or monorepo structure
- Understanding of workspace concepts
- Cursor IDE with workspace support
- Configured .cursorrules for each project

## Instructions

1. Decide on multi-repo strategy (separate windows, workspace, or monorepo)
2. Create workspace file or open specific packages
3. Configure .cursorrules inheritance (root + overrides)
4. Set up selective indexing with .cursorignore
5. Use full paths for @-mentions across projects
6. Test cross-project context and queries

## Output

- Functional multi-repository workspace
- Properly inherited .cursorrules
- Selective indexing per project
- Cross-project AI context awareness

## Error Handling

See `{baseDir}/references/errors.md` for comprehensive error handling.

## Examples

See `{baseDir}/references/examples.md` for detailed examples.

## Resources

- [VS Code Workspaces](https://code.visualstudio.com/docs/editor/workspaces)
- [Turborepo Documentation](https://turbo.build/repo/docs)
- [Cursor Multi-Project Guide](https://cursor.com/docs/workspaces)

Overview

This skill helps you manage work across multiple repositories in Cursor, covering multi-root workspaces, monorepo patterns, and selective indexing. It streamlines cross-project context, .cursorrules inheritance, and efficient AI-assisted development in multi-repo environments. Use it to set up durable workspaces and keep inter-project references reliable.

How this skill works

The skill inspects your workspace configuration and repository layout to recommend a multi-repo strategy: separate windows, a multi-root workspace file, or a monorepo layout. It guides creation and inheritance of .cursorrules, configures .cursorignore for selective indexing, and validates cross-project @-mentions and path resolution. It also runs quick checks to confirm selective indexing and AI context awareness across projects.

When to use it

  • Setting up a new multi-repo or monorepo workspace in Cursor
  • When you need selective indexing to reduce AI/context noise
  • Configuring .cursorrules inheritance across multiple projects
  • Working with cross-project @-mentions or absolute paths
  • Onboarding new team members to a multi-repo Cursor setup

Best practices

  • Choose the simplest strategy that meets your needs: separate windows for unrelated repos, a workspace for related projects, or a true monorepo for tightly coupled packages
  • Maintain a root .cursorrules with per-project overrides to keep rules consistent and flexible
  • Use .cursorignore to exclude build artifacts, large datasets, and vendor folders from indexing
  • Prefer full paths or package-scoped @-mentions to avoid ambiguous cross-project references
  • Test cross-project queries and AI prompts after changes to indexing or rules to catch regressions early

Example use cases

  • Developer opens a workspace file that aggregates six related services and uses .cursorrules inheritance to unify linting and AI assist behavior
  • Team converts several small repos to a multi-root Cursor workspace to enable cross-project code search and consistent AI prompts
  • Selective indexing configured to exclude node_modules and dist folders, cutting indexing time and improving relevant AI results
  • Monorepo with multiple packages uses per-package overrides so CI and local development use different indexing and linting rules

FAQ

How do I stop Cursor from indexing large generated folders?

Add those folders to .cursorignore at the appropriate project level; for multi-root workspaces, place common ignores in the root .cursorignore and overrides in per-project files.

Can AI prompts reference files in another repository?

Yes—use full paths or package-scoped @-mentions and ensure both projects are included in the workspace and properly indexed.