From windsurf-pack
Choose and implement Windsurf validated architecture blueprints for different scales. Use when designing new Windsurf integrations, choosing between monolith/service/microservice architectures, or planning migration paths for Windsurf applications. Trigger with phrases like "windsurf architecture", "windsurf blueprint", "how to structure windsurf", "windsurf project layout", "windsurf microservice".
How this skill is triggered — by the user, by Claude, or both
Slash command
/windsurf-pack:windsurf-architecture-variantsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Workspace and project architectures for Windsurf AI IDE. How you structure your workspace directly impacts Cascade's effectiveness -- large monorepos, multi-project setups, and team configurations each require different approaches.
Workspace and project architectures for Windsurf AI IDE. How you structure your workspace directly impacts Cascade's effectiveness -- large monorepos, multi-project setups, and team configurations each require different approaches.
Best for: Individual developers, single-service projects.
my-project/
├── .windsurfignore # Exclude build artifacts
├── src/
├── tests/
├── package.json
└── README.md
Cascade indexes the entire workspace. Keep it focused on one project for best AI context.
Best for: Teams with monorepo, multiple services.
# DON'T: open the entire monorepo root in Windsurf
# Cascade will index thousands of files, slow context
# DO: open individual service directories
code packages/api/ # One Windsurf window for API
code packages/frontend/ # Another window for frontend
# .windsurfignore at monorepo root (if you must open root)
packages/*/node_modules/
packages/*/dist/
packages/*/coverage/
**/build/
**/generated/
Best for: Large teams, microservices, shared codebase.
Developer A: Windsurf -> services/auth/ (auth service)
Developer B: Windsurf -> services/payments/ (payments service)
Developer C: Windsurf -> shared/libs/ (shared libraries)
# Each developer gets focused Cascade context
# Shared libraries in a separate workspace
Team conventions:
1. One Windsurf window per service/package
2. Use .windsurfignore in every package
3. Cascade tasks scoped to current workspace only
4. Cross-service changes: open both workspaces
5. Tag cascade commits: git commit -m "[cascade] description"
| Factor | Single Project | Focused Monorepo | Multi-Window Team |
|---|---|---|---|
| Team Size | 1-2 | 3-10 | 10+ |
| Codebase | < 10K files | 10K-100K files | 100K+ files |
| Cascade Speed | Fast | Moderate | Fast (per window) |
| Setup | None | .windsurfignore | Per-service windows |
| Issue | Cause | Solution |
|---|---|---|
| Cascade is slow | Too many files indexed | Open smaller workspace, add .windsurfignore |
| Wrong file context | Monorepo root open | Open specific service directory |
| Conflicting edits | Multiple devs, same files | Use feature branches per Cascade session |
node_modules/
dist/
build/
.next/
coverage/
*.min.js
*.map
__pycache__/
.venv/
*.log
npx claudepluginhub aiminnovations/claude-code-plugins-plus --plugin windsurf-packGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 11, 2026