Sync Cursor Settings Across Your Team in 15 Minutes

# In your project root
mkdir -p .cursor

# Create team rules file
touch .cursor/rules

# Team AI Rules - MyProject

## Code Style
- Use const/let, never var
- Max line length: 100 characters
- Prefer functional components in React
- Use async/await, not .then() chains

## Naming Conventions
- Components: PascalCase (UserProfile.tsx)
- Utilities: camelCase (formatDate.ts)
- Constants: UPPER_SNAKE_CASE (API_TIMEOUT)
- Types: PascalCase with T prefix (TUserData)

## Project Context
- We use tRPC for API calls, not REST
- Tailwind for styling, no CSS modules
- Zod for runtime validation
- Server actions in Next.js 15, not API routes

## Testing
- Write tests alongside features
- Use Vitest, not Jest
- Prefer integration over unit tests

{
  "cursor.general.enableTelemetry": false,
  "cursor.ai.model": "claude-sonnet-4",
  "cursor.ai.contextLines": 100,
  "cursor.ai.maxTokens": 4000,
  
  "cursor.autocomplete.enabled": true,
  "cursor.autocomplete.debounceDelay": 150,
  
  "cursor.chat.defaultModel": "claude-sonnet-4",
  "cursor.chat.includeWorkspaceContext": true,
  
  "files.exclude": {
    "**/.git": true,
    "**/node_modules": true,
    "**/.next": true
  }
}

mkdir -p .cursor/prompts

# React Component Template

Create a new React component following our standards:

1. Functional component with TypeScript
2. Props interface with TComponentNameProps
3. Tailwind for styling (no inline styles)
4. Error boundary if it handles data
5. Loading state for async operations
6. Accessible HTML (proper ARIA labels)

Example structure:
- ComponentName.tsx (component)
- ComponentName.test.tsx (tests)
- index.ts (export)

# Add to Git
git add .cursor/

# .gitignore should NOT ignore .cursor/
# Only ignore personal cache
echo ".cursor/.cursorcache" >> .gitignore

git commit -m "Add team Cursor settings and AI rules"
git push

# Cursor Setup for New Team Members

1. Pull latest from main
2. Restart Cursor to load `.cursor/` settings
3. Verify rules loaded: Open Cursor chat → should see project context
4. Test: Ask Cursor to "create a new component" → should follow our template

**Troubleshooting:**
- Settings not applied? Check Cursor → Settings → "Workspace" tab
- Rules not working? Ensure `.cursor/rules` has no syntax errors

# Pull on different machine
git pull

# Open Cursor and check
# Cursor → Settings → Workspace
# Should show your team settings

{
  "cursor.theme": "dark",
  "cursor.fontSize": 14,
  "cursor.fontFamily": "JetBrains Mono",
  "editor.minimap.enabled": false
}

echo ".cursor/settings.local.json" >> .gitignore

# .github/workflows/cursor-validate.yml
name: Validate Cursor Settings

on: [pull_request]

jobs:
  validate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      
      - name: Check Cursor rules exist
        run: |
          if [ ! -f .cursor/rules ]; then
            echo "❌ .cursor/rules missing"
            exit 1
          fi
          
      - name: Validate JSON settings
        run: |
          if [ -f .cursor/settings.json ]; then
            jq empty .cursor/settings.json || exit 1
          fi
          
      - name: Check for committed cache
        run: |
          if [ -d .cursor/.cursorcache ]; then
            echo "❌ Don't commit .cursorcache"
            exit 1
          fi

# .cursor/rules

- Use Server Components by default
- Client Components: 'use client' at top
- Server Actions in app/actions/, not API routes
- Zod schemas in lib/schemas/
- No useState for server data, use React Server Components

# .cursor/rules

- Type hints required (PEP 484)
- Pydantic models for data validation
- async/await for all IO operations
- Docstrings: Google style
- Max function length: 50 lines

# .cursor/rules

- Use Result<T, E> for errors, not panic!
- Prefer iterators over loops
- Public APIs must have docs
- Run clippy before committing
- Use thiserror for custom errors