Cursor New Workspace Setup Prompt

Context

Use this prompt when setting up a new Cursor workspace for Pacing Agency projects. This ensures consistent configuration across team members and projects, including:

Workspace rules for AI assistance guidelines (prefer Project Rules in .cursor/rules/; legacy .cursorrules is still supported)
Git integration and workflow
MCP server configuration (Webflow, Context7, Browser)
Project-specific settings
Directory structure

This prompt will help you:

Create a properly configured Cursor workspace
Set up workspace rules (Project Rules in .cursor/rules/ or .cursorrules) with agency standards
Configure MCP servers for AI integrations
Establish Git workflow
Document workspace conventions

Prerequisites

Cursor installed - Download from cursor.sh
Project repository - Either existing or ready to create
Git access - SSH keys or HTTPS credentials configured
MCP server access - Credentials for Webflow, Context7 (if needed)
Understanding of project - Know what you're building

See Cursor Tool Documentation for existing workspaces and configuration examples.

Prompt Template

I need to set up a new Cursor workspace for a Pacing Agency project with the following requirements:

**Project Information:**
- Project name: [PROJECT_NAME]
- Project type: [PROJECT_TYPE] (Documentation site/Web app/API/Script/Tool)
- Repository: [REPO_URL] (existing or to be created)
- Primary language: [LANGUAGE] (JavaScript/TypeScript/Python/Markdown)
- Framework: [FRAMEWORK] (Docusaurus/React/Next.js/Node.js/None)

**Workspace Requirements:**
- Git workflow: [GIT_WORKFLOW] (Feature branches/Main only)
- MCP servers needed: [MCP_LIST] (Webflow/Context7/Browser/None)
- Code style: [CODE_STYLE] (British English, specific conventions)
- Documentation: [DOCS_REQUIREMENTS] (Inline comments, README, tool docs)

**.cursorrules Configuration:**
- Project-specific rules: [SPECIFIC_RULES]
- File organization: [FILE_STRUCTURE]
- Naming conventions: [NAMING_CONVENTIONS]
- Testing requirements: [TEST_REQUIREMENTS]
- Security considerations: [SECURITY_NOTES]

**Development Environment:**
- Node.js version: [NODE_VERSION] (if applicable)
- Package manager: [PACKAGE_MANAGER] (npm/pnpm/yarn)
- Environment variables: [ENV_VARS_NEEDED]
- External dependencies: [DEPENDENCIES]

Please provide:

1. **Complete .cursorrules file**:
   - Project description and purpose
   - File structure and organisation rules
   - Coding standards (British English, style guide)
   - AI assistance guidelines
   - Testing and documentation requirements
   - Tool-specific configurations
2. **MCP server configuration**:
   - Server setup instructions
   - Configuration JSON for each server
   - Authentication setup
   - Usage examples
3. **Git workflow setup**:
   - Repository initialisation
   - Branch strategy
   - Commit message conventions
   - .gitignore configuration
4. **Directory structure template**:
   - Recommended folder layout
   - Essential files to create
   - Documentation structure
5. **Initial setup checklist**:
   - Commands to run
   - Verification steps
   - Team onboarding notes

Include:
- Examples specific to this project type
- Best practices from other Pacing projects
- Common pitfalls to avoid
- Links to relevant documentation

Format with clear sections and code blocks.

Variables to Customize

Variable	Description	Example
`[PROJECT_NAME]`	Project or workspace name	"TechStackMain", "ClientWebsite", "AutomationScripts"
`[PROJECT_TYPE]`	Type of project	"Documentation site", "Web app", "API service", "Script collection"
`[REPO_URL]`	Git repository URL	"git@github.com:PacingAgency/project-name.git"
`[LANGUAGE]`	Primary programming language	"TypeScript", "JavaScript", "Python", "Markdown"
`[FRAMEWORK]`	Framework or tool	"Docusaurus", "React", "Next.js", "Express", "None"
`[GIT_WORKFLOW]`	Git branch strategy	"Feature branches with PR review", "Main only for simple projects"
`[MCP_LIST]`	MCP servers to configure	"Webflow, Context7, Browser", "Context7 only", "None"
`[CODE_STYLE]`	Coding conventions	"British English, camelCase, semicolons", "PEP 8 for Python"
`[DOCS_REQUIREMENTS]`	Documentation needs	"Inline comments, README, API docs", "Tool documentation in tools/"
`[SPECIFIC_RULES]`	Project-specific guidelines	"All tool docs sync to Docusaurus", "API responses must be typed"
`[FILE_STRUCTURE]`	Directory organisation	"src/ for code, docs/ for documentation", "Flat structure for scripts"
`[NAMING_CONVENTIONS]`	File and variable naming	"camelCase for JS, kebab-case for files", "descriptive function names"
`[TEST_REQUIREMENTS]`	Testing needs	"Unit tests for utilities", "Manual testing checklist", "None"
`[SECURITY_NOTES]`	Security considerations	"Never commit credentials", "Use environment variables for secrets"
`[NODE_VERSION]`	Node.js version	"20.x LTS", "18.x", "Latest"
`[PACKAGE_MANAGER]`	Package manager	"npm", "pnpm", "yarn"
`[ENV_VARS_NEEDED]`	Environment variables	"API keys, database URLs", "None"
`[DEPENDENCIES]`	External dependencies	"Docusaurus, React, TypeScript", "requests, pandas"

Expected Output

The AI should provide:

1. Workspace Rules (.cursor/rules or `.cursorrules`)

# Cursor Rules for [PROJECT_NAME]

## Project Overview

This is a [PROJECT_TYPE] for Pacing Agency. [BRIEF_DESCRIPTION]

## File Structure

[PROJECT_NAME]/ ├── src/ # Source code ├── docs/ # Documentation ├── tests/ # Test files ├── scripts/ # Utility scripts ├── .cursorrules # Legacy rules file (Project Rules in .cursor/rules/ preferred) ├── .gitignore # Git ignore patterns ├── README.md # Project documentation └── package.json # Dependencies (if applicable)

## Coding Standards

### Language & Style
- **British English** spellings (optimise, colour, behaviour)
- **No em dashes** - use commas, periods, or parentheses
- **Conversational tone** - human, confident, no AI filler
- **Active voice** - direct and clear

### Code Conventions
- Use **TypeScript** for type safety (if JS project)
- **camelCase** for variables and functions
- **PascalCase** for components and classes
- **kebab-case** for file names
- Always include **JSDoc comments** for exported functions
- Extract magic numbers to named constants
- Keep functions focused (single responsibility)

### React/Component Guidelines (if applicable)
- Use functional components with hooks
- Props should have TypeScript interfaces
- Keep components small and reusable
- Use CSS Modules for styling
- Handle loading and error states

## Documentation Requirements

- **README.md** - Project overview, setup, usage
- **Inline comments** - For complex logic only
- **JSDoc/TSDoc** - For all exported functions
- **Tool docs** - Update relevant files in tools/ (if applicable)
- **Architecture docs** - Update architecture.md for infrastructure changes

## Git Workflow

- **Branch naming**: `feature/description`, `fix/issue-number`
- **Commit messages**: Descriptive, present tense
- **PR reviews**: Required before merging to main
- **Never commit**: API keys, passwords, .env files

## Testing

- Test locally before committing
- Write unit tests for utility functions (if project requires)
- Manual testing checklist for UI changes
- Verify no linter errors before committing

## Security

- Never hard-code credentials
- Use environment variables for secrets
- Review all external dependencies
- Follow principle of least privilege

## AI Assistance

- Provide context about Pacing Agency tech stack
- Reference existing documentation when available
- Ask for clarification on unclear requirements
- Follow established patterns from other Pacing projects

## Related Documentation

- [Architecture](../../architecture.md) - Tech stack overview
- [Tool Documentation](../../tools/) - All tools and services
- [Git Workflow](../../git-workflow.md) - Version control process

2. MCP Server Configuration

// Cursor Settings > MCP Servers
{
  "mcpServers": {
    "webflow": {
      "command": "npx",
      "args": [
        "-y",
        "@webflow/mcp-server@latest"
      ],
      "env": {
        "WEBFLOW_ACCESS_TOKEN": "your-token-here"
      }
    },
    "context7": {
      "command": "npx",
      "args": [
        "-y",
        "@context7/mcp-server@latest"
      ]
    },
    "browser": {
      "command": "npx",
      "args": [
        "-y",
        "@cursor-ide/mcp-server-browser@latest"
      ]
    }
  }
}

Setup Instructions:

Open Cursor Settings (Cmd+, or Ctrl+,)
Navigate to "MCP Servers"
Add each server configuration
For Webflow: Add access token from Webflow settings
Restart Cursor to activate servers
Verify in Cursor: Look for MCP indicators when asking AI questions

3. Git Workflow Setup

# Initialize repository (if new project)
git init
git remote add origin [REPO_URL]

# Or clone existing repository
git clone [REPO_URL]
cd [PROJECT_NAME]

# Create main branch (if new)
git branch -M main
git add .
git commit -m "Initial commit: Project structure"
git push -u origin main

# Create .gitignore
cat > .gitignore << 'EOF'
# Dependencies
node_modules/
.npm
.pnpm-store/

# Environment files
.env
.env.local
.env.*.local

# Build outputs
dist/
build/
.next/
.docusaurus/

# IDE files
.vscode/
.idea/
*.swp
*.swo

# OS files
.DS_Store
Thumbs.db

# Logs
*.log
npm-debug.log*

# Temporary files
*.tmp
.cache/

# Secrets
*.key
*.pem
secrets/
EOF

git add .gitignore
git commit -m "Add .gitignore"
git push

Branch Strategy:

# Create feature branch
git checkout -b feature/new-feature

# Make changes, commit
git add .
git commit -m "Add new feature"

# Push to remote
git push -u origin feature/new-feature

# Create PR on GitHub
# After review and approval, merge via GitHub

4. Directory Structure

# Create project structure
mkdir -p src/{components,utils,types}
mkdir -p docs
mkdir -p tests
mkdir -p scripts

# Create essential files
touch README.md
touch .cursorrules
touch .gitignore

# For Node.js projects
touch package.json

# For TypeScript projects
touch tsconfig.json

Recommended Structure (Docusaurus):

project-name/
├── .cursorrules           # Cursor AI configuration
├── .gitignore             # Git ignore patterns
├── README.md              # Project documentation
├── architecture.md        # System architecture
├── docs/                  # Operational documentation
│   ├── git-workflow.md
│   └── TOOL_CATEGORIZATION.md
├── docusaurus/            # Docusaurus site
│   ├── docs/              # Site content
│   ├── src/               # React components
│   ├── static/            # Static assets
│   └── package.json       # Dependencies
├── scripts/               # Automation scripts
├── tools/                 # Tool documentation
└── TODO.md                # Master task list

Recommended Structure (React App):

project-name/
├── .cursorrules           # Cursor AI configuration
├── .gitignore             # Git ignore patterns
├── README.md              # Project documentation
├── package.json           # Dependencies
├── tsconfig.json          # TypeScript config
├── src/
│   ├── components/        # React components
│   ├── utils/             # Utility functions
│   ├── types/             # TypeScript types
│   ├── hooks/             # Custom hooks
│   ├── App.tsx            # Main app component
│   └── index.tsx          # Entry point
├── public/                # Static files
└── tests/                 # Test files

5. Setup Checklist

## Initial Workspace Setup Checklist

### Repository Setup
- [ ] Clone or initialize Git repository
- [ ] Create .cursorrules file
- [ ] Create .gitignore file
- [ ] Create README.md with project overview
- [ ] Commit initial structure to Git

### Cursor Configuration
- [ ] Open project in Cursor
- [ ] Verify .cursorrules is in workspace root
- [ ] Configure MCP servers (if needed)
- [ ] Test AI assistance with project context
- [ ] Verify Git integration works

### Development Environment
- [ ] Install dependencies (npm install)
- [ ] Set up environment variables (.env)
- [ ] Verify local development server starts
- [ ] Test build process
- [ ] Configure linter and formatter

### Documentation
- [ ] Update README.md with setup instructions
- [ ] Document environment variables needed
- [ ] Add contribution guidelines
- [ ] Link to relevant Pacing documentation

### Team Onboarding
- [ ] Share repository access with team
- [ ] Document MCP server setup process
- [ ] Create onboarding guide for new developers
- [ ] Schedule team walkthrough (if complex project)

### Verification
- [ ] Git status shows no untracked secrets
- [ ] Cursor AI provides relevant assistance
- [ ] Local development works
- [ ] Can create and push feature branches
- [ ] All team members have access

Follow-up Actions

After setting up workspace:

1. Document Workspace

Create comprehensive README.md:

# [PROJECT_NAME]

[Brief project description]

## Setup

1. Clone repository:
   ```bash
   git clone [REPO_URL]
   cd [PROJECT_NAME]

Install dependencies:
```
npm install
```

Configure environment:

cp .env.example .env
# Edit .env with your credentials

Start development server:
```
npm start
```

Cursor Configuration

This project uses workspace rules for AI assistance guidelines (Project Rules in .cursor/rules/ plus a legacy .cursorrules file in this repo).

MCP Servers: [List servers needed]

See Cursor Tool Documentation for setup instructions.

Project Structure

[Describe directory structure]

Development Workflow

[Describe Git workflow, testing, deployment]

### 2. Configure MCP Servers

For each MCP server needed:

1. **Webflow MCP**:
   - Get access token from Webflow settings
   - Add to Cursor MCP configuration
   - Test by asking AI about Webflow CMS

2. **Context7 MCP**:
   - Install via npm (automatic)
   - Test by asking AI about library documentation

3. **Browser MCP**:
   - Install via npm (automatic)
   - Test by navigating to a URL

### 3. Team Onboarding

Share workspace with team:
- Grant repository access
- Share environment variable values (securely)
- Document MCP server setup
- Schedule pairing session for complex projects

### 4. Establish Development Workflow

Configure Git workflow:
- Create `docs/git-workflow.md` if not exists
- Set up branch protection rules
- Configure PR templates
- Set up CI/CD (if applicable)

## Related Documentation

- [Cursor Tool Documentation](../../tools/operational-tools/cursor.md) - Workspace examples
- [Git Workflow](../../git-workflow.md) - Version control process
- [Docusaurus Setup](../../docusaurus/index.md) - For documentation sites
- [Architecture](../../architecture.md) - Tech stack overview

## Success Criteria

Before considering workspace setup complete, verify:

✅ .cursorrules file exists and is configured  
✅ Git repository is initialized with remote  
✅ .gitignore is properly configured  
✅ MCP servers are working (if needed)  
✅ Local development server starts without errors  
✅ Can create and push feature branches  
✅ README.md documents setup process  
✅ Environment variables are documented  
✅ Team members have access  
✅ AI assistance provides relevant context

## Common Issues

### Issue: MCP server not connecting

**Symptoms**: AI doesn't show MCP-specific knowledge

**Solutions**:
1. Verify MCP server configuration in Cursor settings
2. Check environment variables are set correctly
3. Restart Cursor after configuration changes
4. Test server connection:
   - Webflow: Ask "What CMS collections exist?"
   - Context7: Ask "How do I use X library?"
   - Browser: Ask "Navigate to pacing.agency"

### Issue: Workspace rules not applying

**Symptoms**: AI responses don't follow guidelines

**Solutions**:
1. Verify `.cursorrules` is in workspace root directory or Project Rules are in `.cursor/rules/`
2. Check the file is not `.cursorrules.txt` (no extension) if using the legacy file
3. Restart Cursor to reload rules
4. Explicitly mention rules in prompts: "Following our workspace rules (Project Rules / `.cursorrules`)..."

### Issue: Git credentials not working

**Symptoms**: Can't push/pull from repository

**Solutions**:
1. Check SSH keys are configured:
   ```bash
   ssh -T git@github.com

Or use HTTPS with personal access token

Configure Git credentials:

git config user.name "Your Name"
git config user.email "your.email@pacing.agency"

Issue: Environment variables not loading

Symptoms: Application can't access API keys, database URLs

Solutions:

Verify .env file exists (should NOT be in Git)
Check variable names match code:
```
cat .env | grep VARIABLE_NAME
```
Restart development server after .env changes
For Docker: Pass env vars to container

Examples

Example 1: TechStackMain Workspace

Project: Documentation site for Pacing Agency tech stack

# Workspace rules highlights
- Workspace-level docs at root (architecture.md, README.md)
- Tool documentation in tools/ (one file per tool)
- Docusaurus site in docusaurus/
- British English, conversational tone
- MDX compliance for Docusaurus

# MCP Servers
- Webflow (for CMS integration)
- Context7 (for library docs)
- Browser (for testing docs site)

# Directory Structure
TechStackMain/
├── .cursorrules
├── architecture.md
├── README.md
├── TODO.md
├── docs/
├── tools/
├── docusaurus/
└── scripts/

Example 2: Client Website Workspace

Project: Custom web application for client

# Workspace rules highlights
- React + TypeScript
- British English, client-facing tone
- Webflow CMS integration
- GTM tracking implementation

# MCP Servers
- Webflow (for CMS data)
- Context7 (for React/TypeScript docs)

# Directory Structure
client-website/
├── .cursorrules
├── README.md
├── src/
│   ├── components/
│   ├── utils/
│   └── types/
├── public/
└── tests/

Example 3: Automation Scripts Workspace

Project: Collection of n8n workflow automation scripts

# Workspace rules highlights
- JavaScript/Node.js
- Flat file structure
- Each script is self-contained
- Documentation in script headers

# MCP Servers
- Context7 (for Node.js/n8n docs)

# Directory Structure
automation-scripts/
├── .cursorrules
├── README.md
├── webflow-cache-clear.js
├── twentycrm-sync.js
├── google-ads-conversions.js
└── docs/

Last updated: 2026-01-07
Tested on: Cursor v0.43.x
Estimated time: 20 minutes (setup + configuration)

Context​

Prerequisites​

Prompt Template​

Variables to Customize​

Expected Output​

1. Workspace Rules (.cursor/rules or .cursorrules)​

2. MCP Server Configuration​

3. Git Workflow Setup​

4. Directory Structure​

5. Setup Checklist​

Follow-up Actions​

1. Document Workspace​

Cursor Configuration​

Project Structure​

Development Workflow​

Related Documentation​

Issue: Environment variables not loading​

Examples​

Example 1: TechStackMain Workspace​

Example 2: Client Website Workspace​

Example 3: Automation Scripts Workspace​