windsurf-architecture-variants
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".
- License 许可
- MIT
- 最近更新
- 2026-05-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- windsurf-architecture-variants
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- version
- 1.0.0
- description
- 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".
- allowed-tools
- Read, Grep
- compatible-with
- claude-code, codex, openclaw
03 SKILL.md 正文
Windsurf Architecture Variants
Overview
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.
Prerequisites
- Windsurf installed
- Understanding of Cascade's workspace indexing
- Git workflow established
Instructions
Step 1: Single Project Workspace (Simple)
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.
Step 2: Focused Monorepo Windows (Moderate)
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/
Step 3: Multi-Window Team Workflow (Scale)
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"
Decision Matrix
| 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 |
Error Handling
| 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 |
Examples
Optimized .windsurfignore
node_modules/
dist/
build/
.next/
coverage/
*.min.js
*.map
__pycache__/
.venv/
*.log
Resources
Output
- Configuration files or code changes applied to the project
- Validation report confirming correct implementation
- Summary of changes made and their rationale
04 同仓库更多 Skills
zustand-store-ts
Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.
zustand-store-creator
Zustand Store Creator - Auto-activating skill for Frontend Development. Triggers on: zustand store creator, zustand store creator Part of the Frontend Development skill category.
zero-trust-config-helper
Zero Trust Config Helper - Auto-activating skill for Security Advanced. Triggers on: zero trust config helper, zero trust config helper Part of the Security Advanced skill category.
zapier-integration-helper
Zapier Integration Helper - Auto-activating skill for Business Automation. Triggers on: zapier integration helper, zapier integration helper Part of the Business Automation skill category.
zai-cli
Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP. Use when user needs image/video analysis, OCR, UI-to-code conversion, error diagnosis, real-time web search, web page to markdown extraction, or GitHub code exploration. Trigger with phrases like "analyze this image", "search the web for", "read this page", "explore this repo", or "use zai". Requires Z_AI_API_KEY.
yt-research
Research competitor YouTube channels, niches, and trending topics for your content strategy. Use this skill whenever the user says "research channels", "analyze competitors", "find trending topics", "niche analysis", "competitive research", "what are other creators doing", "scrape YouTube channels", or wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.