windsurf-load-scale
Offers strategies for scaling Windsurf usage in teams of 50+ developers by managing monorepo workspaces and performance configuration.
Install
mkdir -p .claude/skills/windsurf-load-scale && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/7102" && unzip -o skill.zip -d .claude/skills/windsurf-load-scale && rm skill.zipInstalls to .claude/skills/windsurf-load-scale
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Scale Windsurf adoption across large organizations with workspace strategiesKey capabilities
- →Partition large monorepos into sub-workspaces
- →Distribute configuration templates across teams
- →Implement credit budgeting for large organizations
- →Configure network endpoints for enterprise environments
- →Automate onboarding and extension management
How it works
It provides architectural patterns for partitioning large codebases into smaller sub-workspaces and distributing standardized configuration files to ensure consistent performance.
Inputs & outputs
When to use windsurf-load-scale
- →Scale Windsurf in large teams
- →Manage large monorepo performance
- →Partition development workspaces
- →Plan enterprise-scale IDE deployment
About this skill
Windsurf Load & Scale
Overview
Strategies for deploying Windsurf AI IDE across large organizations (50-1000+ developers). Covers workspace partitioning for monorepos, configuration distribution, credit budgeting, and performance at scale.
Prerequisites
- Windsurf Teams or Enterprise plan
- Admin dashboard access
- Understanding of team structure and repository layout
- Network/IT involvement for enterprise features
Instructions
Step 1: Workspace Strategy for Large Codebases
# Windsurf performance degrades with workspace size
# Cascade context quality inversely correlates with file count
workspace_sizing:
optimal: "<5,000 files — fast indexing, precise Cascade context"
acceptable: "5,000-20,000 files — add .codeiumignore, expect slower indexing"
problematic: "20,000+ files — must partition into sub-workspaces"
unworkable: "100,000+ files at root — Cascade context diluted, indexing very slow"
# Strategy: one Windsurf window per service/package
# Each developer opens their assigned service directory
Step 2: Monorepo Partitioning
# Large monorepo (100K+ files)
company-monorepo/
├── .windsurfrules # Brief shared conventions only
├── .codeiumignore # Aggressive: exclude EVERYTHING except src
├── apps/
│ ├── web-app/ # Developer A opens this window
│ │ ├── .windsurfrules # Next.js-specific AI context
│ │ └── .codeiumignore # Local exclusions
│ ├── mobile-app/ # Developer B opens this window
│ │ ├── .windsurfrules # React Native context
│ │ └── .codeiumignore
│ └── admin-portal/ # Developer C opens this window
│ ├── .windsurfrules
│ └── .codeiumignore
├── services/
│ ├── api-gateway/ # Backend team opens individual services
│ ├── auth-service/
│ ├── payment-service/
│ └── notification-service/
├── packages/
│ └── shared-types/ # Library maintainer opens this
└── infrastructure/
└── terraform/ # DevOps opens this
Rule: Never open the monorepo root in Windsurf. Each developer opens their service directory.
Step 3: Configuration Distribution at Scale
# Central config repo for team-wide standards
windsurf-config/
├── templates/
│ ├── windsurfrules/
│ │ ├── nextjs.md # Template for Next.js projects
│ │ ├── fastify.md # Template for Fastify APIs
│ │ ├── react-native.md # Template for mobile apps
│ │ └── shared-library.md # Template for shared packages
│ ├── codeiumignore/
│ │ ├── node-project.ignore
│ │ ├── python-project.ignore
│ │ └── go-project.ignore
│ └── workflows/
│ ├── deploy-staging.md
│ ├── pr-review.md
│ └── quality-check.md
├── scripts/
│ ├── setup-windsurf.sh # Onboarding script
│ └── sync-config.sh # Distribute updates
└── README.md
Sync script:
#!/bin/bash
set -euo pipefail
# scripts/sync-config.sh — run from monorepo root
TEMPLATE_DIR="/path/to/windsurf-config/templates"
for service_dir in apps/*/ services/*/; do
[ -d "$service_dir" ] || continue
SERVICE=$(basename "$service_dir")
# Copy .codeiumignore if missing
[ -f "$service_dir/.codeiumignore" ] || \
cp "$TEMPLATE_DIR/codeiumignore/node-project.ignore" "$service_dir/.codeiumignore"
# Copy shared workflows
mkdir -p "$service_dir/.windsurf/workflows"
cp "$TEMPLATE_DIR/workflows/"*.md "$service_dir/.windsurf/workflows/" 2>/dev/null || true
echo "Synced: $SERVICE"
done
Step 4: Credit Budgeting at Scale
# Credit planning for large teams
credit_budget:
team_size: 100
tier_allocation:
power_users: 20 # Pro: heavy Cascade users (senior devs, architects)
regular_users: 50 # Pro: daily Supercomplete + occasional Cascade
light_users: 20 # Free: reviewers, designers, PMs with code access
contractors: 10 # Free: temporary, limited AI needs
monthly_cost:
pro_seats: 70 x $30 = $2,100
free_seats: 30 x $0 = $0
total: $2,100/month
vs_alternative:
cursor_equivalent: 70 x $20 = $1,400 # But fewer features
copilot_equivalent: 100 x $19 = $1,900 # No agentic features
optimization:
quarterly_review: "Audit usage, downgrade inactive seats"
training_program: "Monthly 30-min workshop for new features"
workflow_investment: "Build team workflows to reduce per-user credit waste"
Step 5: Enterprise Network Configuration
# IT/Network team requirements
network_config:
endpoints_to_whitelist:
- "*.codeium.com" # AI inference
- "*.windsurf.com" # Auth, updates, admin portal
- "windsurf.com" # Downloads, documentation
proxy_support:
http_proxy: "${HTTP_PROXY}"
https_proxy: "${HTTPS_PROXY}"
no_proxy: "localhost,127.0.0.1,.internal.company.com"
# Set via Windsurf Settings or environment variables
deployment_modes:
cloud: "Standard — code context sent to Codeium cloud"
hybrid: "Code stays local, only prompts sent to cloud"
self_hosted: "Everything on-prem (Enterprise plan required)"
Step 6: Onboarding Automation
#!/bin/bash
set -euo pipefail
# Large-team onboarding script
echo "=== Windsurf Team Onboarding ==="
# 1. Install Windsurf
if ! command -v windsurf &>/dev/null; then
echo "Installing Windsurf..."
brew install --cask windsurf 2>/dev/null || {
echo "Download from: https://windsurf.com/download"
exit 1
}
fi
# 2. Import existing editor settings
echo "Importing VS Code settings..."
windsurf 2>/dev/null & # First launch imports settings
sleep 3
kill %1 2>/dev/null || true
# 3. Install approved extensions
EXTENSIONS=(
"esbenp.prettier-vscode"
"dbaeumer.vscode-eslint"
"biomejs.biome"
)
for ext in "${EXTENSIONS[@]}"; do
windsurf --install-extension "$ext" 2>/dev/null
done
# 4. Disable conflicting extensions
CONFLICTS=("github.copilot" "tabnine.tabnine-vscode")
for ext in "${CONFLICTS[@]}"; do
windsurf --disable-extension "$ext" 2>/dev/null || true
done
# 5. Set team config
echo "Configuring team settings..."
echo ""
echo "Complete. Next steps:"
echo "1. Open your service directory in Windsurf (not monorepo root)"
echo "2. Sign in with company SSO when prompted"
echo "3. Verify .windsurfrules exists in your service directory"
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| Indexing slow across team | Large workspaces | Partition into sub-workspaces per service |
| Config drift between services | No central templates | Implement sync-config.sh script |
| Credit overspend | No budgeting | Implement tier allocation, quarterly review |
| Network blocking Windsurf | Firewall rules | Whitelist .codeium.com and.windsurf.com |
| Inconsistent AI suggestions | Different .windsurfrules | Use central template repository |
Examples
Quick Team Health Dashboard
echo "=== Team Windsurf Health ==="
echo "Services with .windsurfrules:"
find . -maxdepth 3 -name ".windsurfrules" | wc -l
echo "Services with .codeiumignore:"
find . -maxdepth 3 -name ".codeiumignore" | wc -l
echo "Services without config (needs fix):"
for d in apps/* services/*; do
[ -d "$d" ] || continue
[ -f "$d/.windsurfrules" ] || echo " MISSING: $d/.windsurfrules"
done
Resources
Next Steps
For reliability patterns, see windsurf-reliability-patterns.
When not to use it
- →When implementing reliability patterns (use windsurf-reliability-patterns instead)
Prerequisites
Limitations
- →Requires developers to open service-specific subdirectories rather than the monorepo root
How it compares
It specifically addresses the performance degradation caused by large file counts in IDE indexing, which generic scaling advice ignores.
Compared to similar skills
windsurf-load-scale side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| windsurf-load-scale (this skill) | 1 | 27d | Review | Advanced |
| software-architecture | 333 | 6mo | No flags | Intermediate |
| architect-review | 109 | 4mo | No flags | Advanced |
| mcp-builder | 136 | 3mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
software-architecture
davila7
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
architect-review
sickn33
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.
mcp-builder
anthropics
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
solid-principles
SmidigStorm
Enforce SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) in object-oriented design. Use when writing or reviewing classes and modules.
codex
Lucklyric
Invoke Codex CLI for complex coding tasks requiring high reasoning capabilities. This skill should be invoked when users explicitly mention "Codex", request complex implementation challenges, advanced reasoning, or need high-reasoning model assistance. Automatically triggers on codex-related requests and supports session continuation for iterative development.
architecture-patterns
wshobson
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.