windsurf-upgrade-migration
Upgrade Windsurf IDE, migrate settings from VS Code or Cursor, and handle breaking changes. Use when upgrading Windsurf versions, migrating from another editor, or handling configuration changes after updates. Trigger with phrases like "upgrade windsurf", "windsurf update", "migrate to windsurf", "windsurf from cursor", "windsurf from vscode".
What this skill does
# Windsurf Upgrade & Migration ## Current State !`windsurf --version 2>/dev/null || echo 'Not installed'` !`code --version 2>/dev/null | head -1 || echo 'VS Code not installed'` ## Overview Guide for upgrading Windsurf to new versions and migrating from VS Code or Cursor. Covers settings transfer, extension compatibility, and Windsurf-specific configuration that doesn't exist in other editors. ## Prerequisites - Current editor installation accessible - Git for version controlling config files - Backup of existing settings ## Instructions ### Step 1: Check Current Windsurf Version ```bash # Current version windsurf --version # Check for updates # Windsurf auto-updates by default # Manual: Help > Check for Updates (or download from windsurf.com) ``` ### Step 2: Migrate from VS Code Windsurf is VS Code-based and supports most VS Code settings and extensions: ```bash # Windsurf imports VS Code settings on first launch # For manual migration: # 1. Export VS Code extensions list code --list-extensions > vscode-extensions.txt # 2. Install in Windsurf cat vscode-extensions.txt | xargs -L1 windsurf --install-extension # 3. Copy settings # macOS: cp ~/Library/Application\ Support/Code/User/settings.json \ ~/Library/Application\ Support/Windsurf/User/settings.json # Linux: cp ~/.config/Code/User/settings.json \ ~/.config/Windsurf/User/settings.json ``` **Key difference:** Remove or disable GitHub Copilot -- it conflicts with Windsurf's Supercomplete. ### Step 3: Migrate from Cursor Cursor and Windsurf both extend VS Code but have different AI config files: ```yaml # Mapping Cursor concepts to Windsurf: cursor_to_windsurf: .cursorrules: .windsurfrules # AI context rules .cursorignore: .codeiumignore # AI indexing exclusions .cursor/rules/: .windsurf/rules/ # Workspace rules cursor_settings: windsurf_settings # IDE preferences Composer: Cascade # Agentic AI assistant Tab: Supercomplete # Inline completions Cmd+K: Cmd+I # Inline editing Cmd+L: Cmd+L # AI chat (same!) ``` **Migration script:** ```bash #!/bin/bash set -euo pipefail echo "Migrating Cursor config to Windsurf..." # Convert .cursorrules to .windsurfrules [ -f .cursorrules ] && cp .cursorrules .windsurfrules && echo "Copied .cursorrules → .windsurfrules" # Convert .cursorignore to .codeiumignore [ -f .cursorignore ] && cp .cursorignore .codeiumignore && echo "Copied .cursorignore → .codeiumignore" # Migrate workspace rules if [ -d .cursor/rules ]; then mkdir -p .windsurf/rules cp .cursor/rules/*.md .windsurf/rules/ 2>/dev/null echo "Copied workspace rules to .windsurf/rules/" echo "NOTE: Check frontmatter -- Windsurf uses 'trigger:' field, Cursor uses different format" fi echo "Migration complete. Review .windsurfrules for Cursor-specific references." ``` ### Step 4: Add Windsurf-Specific Configuration After migration, add Windsurf-exclusive features: ```markdown <!-- New Windsurf features not in VS Code or Cursor --> 1. Cascade Workflows (.windsurf/workflows/*.md) - Reusable multi-step automation via slash commands - No equivalent in VS Code or Cursor 2. Cascade Memories - Persistent facts across sessions - Partial equivalent: Cursor notepad 3. Turbo Mode - Auto-execute terminal commands - Cursor has "auto-run" but different config 4. Browser Previews - In-IDE preview with element selection - Send UI elements to Cascade for editing 5. Workspace Rules with Trigger Modes - glob, always_on, manual, model_decision - More granular than Cursor's rule system ``` ### Step 5: Post-Upgrade Validation ```bash set -euo pipefail echo "=== Windsurf Post-Upgrade Check ===" echo "Version: $(windsurf --version)" echo "Extensions: $(windsurf --list-extensions | wc -l) installed" echo "Rules: $([ -f .windsurfrules ] && wc -c < .windsurfrules || echo 'none') bytes" echo "Ignore: $([ -f .codeiumignore ] && wc -l < .codeiumignore || echo 'none') patterns" # Test AI features echo "" echo "Manual checks:" echo "1. Open a code file -- Supercomplete should show ghost text" echo "2. Press Cmd/Ctrl+L -- Cascade should open and respond" echo "3. Press Cmd/Ctrl+I -- Command mode should activate" ``` ## Error Handling | Issue | Cause | Solution | |-------|-------|----------| | Extensions not loading | Incompatible with Windsurf | Check Windsurf marketplace for alternative | | Settings not applied | Wrong config directory | Verify OS-specific settings path | | .cursorrules not working | Wrong filename | Rename to `.windsurfrules` | | Keyboard shortcuts different | Windsurf overrides some defaults | Check Keyboard Shortcuts editor | | Copilot still active | Not disabled | Extensions > search "copilot" > Disable | ## Examples ### Backup Before Upgrade ```bash # Backup current Windsurf config tar -czf windsurf-config-backup-$(date +%Y%m%d).tar.gz \ ~/.config/Windsurf/User/ \ ~/.codeium/ \ .windsurfrules \ .codeiumignore \ .windsurf/ 2>/dev/null ``` ### Check Windsurf Changelog ``` Visit: https://windsurf.com/changelog Look for: breaking changes, deprecated settings, new features ``` ## Resources - [Windsurf Changelog](https://windsurf.com/changelog) - [Windsurf Download](https://windsurf.com/download) - [Migrating from Cursor](https://docs.windsurf.com) ## Next Steps For CI integration, see `windsurf-ci-integration`.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.