windsurf-load-scale
Implement Windsurf load testing, auto-scaling, and capacity planning strategies. Use when running performance tests, configuring horizontal scaling, or planning capacity for Windsurf integrations. Trigger with phrases like "windsurf load test", "windsurf scale", "windsurf performance test", "windsurf capacity", "windsurf k6", "windsurf benchmark".
Install
mkdir -p .claude/skills/windsurf-load-scale && curl -L -o skill.zip "https://mcp.directory/api/skills/download/7102" && unzip -o skill.zip -d .claude/skills/windsurf-load-scale && rm skill.zipInstalls to .claude/skills/windsurf-load-scale
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.
More by jeremylongshore
View all skills by jeremylongshore →You might also like
flutter-development
aj-geddes
Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.
drawio-diagrams-enhanced
jgtolentino
Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.
ui-ux-pro-max
nextlevelbuilder
"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."
godot
bfollington
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.
nano-banana-pro
garg-aayush
Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.
fastapi-templates
wshobson
Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.
Related MCP Servers
Browse all serversEnhance software testing with Playwright MCP: Fast, reliable browser automation, an innovative alternative to Selenium s
Automate API testing with Postman collections or OpenAPI specs. Generate test cases in TypeScript, JavaScript, and Pytho
Connect Claude to Apifox for direct API docs access and testing via env-auth and TypeScript/Express integration.
Discover JNews, a lightweight Python FastAPI server using uv for dependencies and GitHub Actions for CI/CD. Ideal for Fa
Break down complex problems with Sequential Thinking, a structured tool and step by step math solver for dynamic, reflec
Build persistent semantic networks for enterprise & engineering data management. Enable data persistence and memory acro
Stay ahead of the MCP ecosystem
Get weekly updates on new skills and servers.