root-project-setup

Coordinate project imports and switches in a root repository using a shared .cursor/ configuration.

Updated Feb 22, 2026

Search Tags:#cursor #gitignore #workspace-management #root-repo #nested-clones #project-import #switch-projects

Ready to run

npx skills add https://github.com/JuroOravec/agents --skill root-project-setup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: root-project-setup
Source: https://github.com/JuroOravec/agents/tree/main/.cursor/skills/root/project-setup
Command: npx skills add https://github.com/JuroOravec/agents --skill root-project-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure a root repository with a single shared .cursor/ config to manage multiple imported projects, eliminating drift and duplication.

Core Features & Use Cases

Centralized root config for agents, skills, and rules.
Manage nested git clones as imported projects (add, remove, switch).
Reminders for window reloads to refresh indexing after changes.

Quick Start

Configure a root repo with a shared .cursor/ and add or switch nested project folders as needed.

Frequently Asked Questions about root-project-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I configure a root repo to manage multiple nested git clones in Cursor?▼

You can manage multiple nested git clones in Cursor by setting up a shared .cursor/ configuration in the root repository. This centralizes project imports, switches, and rules, eliminating duplication across nested project folders.

What is a shared .cursor configuration for workspace management?▼

A shared .cursor configuration is a single directory in a root repository that centralizes settings for nested project clones. It manages adding, removing, and switching active projects while preventing configuration drift across the workspace.

How do I switch active projects in a root repository without losing indexing?▼

Switching active projects uses a phased workflow that includes intent validation, soft or hard switches, and progress storage. After completing the switch, the workflow enforces window-reload reminders to refresh Cursor's indexing.

Does the root-project setup workflow require specific prerequisites for nested clones?▼

Yes, the workflow validates prerequisites before adding or switching projects. It requires a root repository structure hosting nested git clones and a single shared .cursor/ configuration directory to execute phased project switches.

Why does Cursor need a window reload after switching imported projects?▼

Cursor needs a window reload after switching imported projects to refresh file indexing. The workflow enforces these reminders because adding or removing nested clones changes the active workspace files that the editor tracks.