windsurf-load-scale
Scale Windsurf adoption across large organizations with workspace strategies and performance tuning. Use when rolling out Windsurf to 50+ developers, managing large monorepo workspaces, or planning enterprise-scale deployment. Trigger with phrases like "windsurf at scale", "windsurf large team", "windsurf monorepo", "windsurf organization", "windsurf 100 developers". '
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill windsurf-load-scale --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 ```yaml # 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 # Ag
- Overview
- Prerequisites
- Instructions
- Step 1: Workspace Strategy for Large Codebases
- Step 2: Monorepo Partitioning
- Step 3: Configuration Distribution at Scale
- Step 4: Credit Budgeting at Scale
- Step 5: Enterprise Network Configuration
- Step 6: Onboarding Automation
- Error Handling
- Examples
- Quick Team Health Dashboard
- Resources
- Next Steps
set -euo pipefail scripts/sync-config.sh — run from monorepo root for service_dir in apps/*/ services/*/; do cp "$TEMPLATE_DIR/codeiumignore/node-project.ignore" "$service_dir/.codeiumignore" mkdir -p "$service_dir/.windsurf/workflows" cp "$TEMPLATE_DIR/workflows/"*.md "$service_dir/.windsurf/workflows/" 2>/dev/null || true echo "Synced: $SERVICE" done Large-team onboarding script echo "=== Windsurf Team Onboarding ==="
What does the windsurf-load-scale skill do?
Scale Windsurf adoption across large organizations with workspace strategies and performance tuning. Use when rolling out Windsurf to 50+ developers, managing large monorepo workspaces, or planning enterprise-scale deployment. Trigger with phrases like "windsurf at scale", "windsurf large team", "windsurf monorepo", "windsurf organization", "windsurf 100 developers". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill windsurf-load-scale --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.