windsurf-architecture-variants

# Windsurf Architecture Variants ## Overview How you structure your Windsurf workspace directly impacts Cascade's effectiveness. Large monorepos, multi-service setups, polyglot codebases, and different team sizes each require different approaches. This skill covers workspace strategies from solo projects to 100+ developer organizations. ## Prerequisites - Windsurf installed - Understanding of Cascade's workspace indexing model - Git workflow established ## Instructions ### Variant 1: Single Project (Solo / Small Team) **Best for:** 1-3 developers, single service, <10K files. ``` my-project/ ├── .windsurfrules # Full project context ├── .codeiumignore # Exclude build artifacts ├── src/ ├── tests/ ├── package.json └── README.md ``` **Configuration:** - Open entire project as workspace - Cascade indexes everything — no partitioning needed - `.windsurfrules` contains complete stack and architecture details ### Variant 2: Focused Monorepo Windows (Medium Team) **Best for:** 3-15 developers, monorepo with 2-10 packages. ``` monorepo/ ├── .windsurfrules # Brief shared conventions ├── .codeiumignore # Aggressive exclusions at root ├── packages/ │ ├── api/ │ │ ├── .windsurfrules # API-specific rules │ │ └── .codeiumignore │ ├── web/ │ │ ├── .windsurfrules # Frontend-specific rules │ │ └── .codeiumignore │ └── shared/ │ ├── .windsurfrules # Library conventions │ └── .codeiumignore └── .windsurf/ └── ...