windsurf-local-dev-loop
Configures an optimized Windsurf dev loop using project rules, Turbo mode, and terminal integration.
Install
mkdir -p .claude/skills/windsurf-local-dev-loop && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5385" && unzip -o skill.zip -d .claude/skills/windsurf-local-dev-loop && rm skill.zipInstalls to .claude/skills/windsurf-local-dev-loop
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Configure Windsurf local development workflow with Cascade, Previews,Key capabilities
- →Define project-specific AI rules in .windsurfrules
- →Exclude files from AI indexing using .codeiumignore
- →Enable Turbo mode for automated terminal execution
- →Preview web applications directly within the IDE
- →Use natural language commands in the terminal
How it works
Cascade uses project-specific rules and ignore files to maintain context, while Turbo mode allows it to execute terminal commands based on defined allow lists.
Inputs & outputs
When to use windsurf-local-dev-loop
- →Create project-specific AI rules for consistent code
- →Configure Turbo mode for faster AI responses
- →Setup local development workflow with testing
- →Define stack-specific architecture for Cascade
About this skill
Windsurf Local Dev Loop
Overview
Set up a fast, AI-augmented local development workflow using Windsurf's Cascade, Turbo mode, Previews, and terminal integration. The goal is a tight loop: edit with Cascade, preview in-IDE, iterate, test, commit.
Prerequisites
- Windsurf authenticated and project open
- Node.js 18+ or Python 3.10+
- Git initialized in project
Instructions
Step 1: Create .windsurfrules for Project Context
<!-- .windsurfrules - placed at project root, committed to git -->
# Project: my-app
## Stack
- Language: TypeScript (strict mode)
- Framework: Next.js 14 (App Router)
- Styling: Tailwind CSS v3
- Testing: Vitest + Testing Library
- Package manager: pnpm
## Architecture
- Server Components by default
- Client Components only when state/interactivity needed
- API routes in app/api/
- Business logic in lib/services/
- Types in lib/types/
## Conventions
- Named exports, never default
- async/await, never raw .then()
- zod for all runtime validation
- Error handling: Result pattern in services
Step 2: Configure .codeiumignore
# .codeiumignore - exclude from AI indexing (same syntax as .gitignore)
node_modules/
.next/
dist/
build/
coverage/
*.min.js
*.map
.env
.env.*
Step 3: Set Up Turbo Mode for Fast Terminal Execution
Turbo mode lets Cascade auto-execute terminal commands without asking permission for each one.
Enable: Windsurf Settings > Cascade > Terminal Execution Level > Turbo
Configure safety lists:
// Settings (JSON) — search "cascadeCommands"
{
"windsurf.cascadeCommandsAllowList": [
"npm", "pnpm", "npx", "node", "tsc",
"vitest", "jest", "eslint", "prettier",
"git status", "git diff", "git log", "git add"
],
"windsurf.cascadeCommandsDenyList": [
"rm -rf", "sudo", "git push --force",
"git reset --hard", "DROP TABLE", "shutdown"
]
}
Step 4: Use Previews for UI Development
Ask Cascade to preview your web app:
"Start the dev server and preview the app"
Cascade starts the server and opens an in-IDE Preview tab. From the Preview:
- Click "Send element" (bottom-right) to select a UI element and send it to Cascade
- Console errors are automatically forwarded to Cascade for debugging
- Iterate by describing changes: "Make the header sticky and add a dark mode toggle"
Step 5: The Dev Loop
1. Open Cascade (Cmd/Ctrl+L)
2. Describe the feature or fix
3. Cascade edits files and runs commands (Turbo mode)
4. Preview updates in-IDE (hot reload)
5. Click broken elements → send to Cascade
6. Cascade fixes → repeat until correct
7. Run tests: "Run vitest for the files you changed"
8. Commit: "Commit these changes with message: add dark mode toggle"
Step 6: Terminal Integration
Use Cmd/Ctrl+I in the terminal for natural language commands:
Type: "find all files importing the Button component"
Windsurf generates: grep -rl "import.*Button" src/
Type: "run tests for auth module only"
Windsurf generates: npx vitest run src/auth/
Highlight terminal errors and press Cmd/Ctrl+L to send to Cascade for diagnosis.
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| Cascade not seeing project context | No .windsurfrules | Create rules file at project root |
| Slow AI suggestions | Large repo indexed | Add .codeiumignore |
| Turbo mode running dangerous commands | Missing deny list | Configure cascadeCommandsDenyList |
| Preview not loading | Dev server not started | Ask Cascade to start it first |
| Hot reload not working | Preview disconnected | Close and re-open Preview tab |
Examples
Quick Project Bootstrap
Cascade prompt: "Initialize a new Next.js 14 project with TypeScript,
Tailwind CSS, and Vitest. Set up the folder structure matching
our .windsurfrules conventions."
Debug-Fix Loop
1. See error in terminal or Preview console
2. Highlight error text → Cmd/Ctrl+L → "Fix this error"
3. Cascade reads error, finds root cause, applies fix
4. Preview auto-reloads → verify fix
Resources
Next Steps
See windsurf-sdk-patterns for workspace configuration patterns.
When not to use it
- →When working without Git initialized in the project
- →When using environments below Node.js 18 or Python 3.10
Prerequisites
Limitations
- →Turbo mode requires explicit configuration of allow and deny lists
- →Large repositories may experience slow AI suggestions
How it compares
This workflow integrates terminal execution and in-IDE previews directly into the AI iteration loop, unlike manual development cycles.
Compared to similar skills
windsurf-local-dev-loop side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| windsurf-local-dev-loop (this skill) | 1 | 27d | Review | Intermediate |
| command-development | 16 | 9mo | Review | Intermediate |
| skill-forge | 11 | 9mo | Review | Intermediate |
| codex-skill | 12 | 5mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
command-development
anthropics
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
skill-forge
WilliamSaysX
Automated skill creation workshop with intelligent source detection, smart path management, and end-to-end workflow automation. This skill should be used when users want to create a new skill or convert external resources (GitHub repositories, online documentation, or local directories) into a skill. Automatically fetches, organizes, and packages skills with proactive cleanup management.
codex-skill
feiskyer
Use when user asks to leverage codex, gpt-5, or gpt-5.1 to implement something (usually implement a plan or feature designed by Claude). Provides non-interactive automation mode for hands-off task execution without approval prompts.
agent-factory
alirezarezvani
Claude Code agent generation system that creates custom agents and sub-agents with enhanced YAML frontmatter, tool access patterns, and MCP integration support following proven production patterns
subagent-driven-development
davila7
Use when executing implementation plans with independent tasks in the current session
peekaboo
openclaw
Capture and automate macOS UI with the Peekaboo CLI.