Agent skill · Workflow & Productivity

windsurf-local-dev-loop

Configure Windsurf local development workflow with Cascade, Previews, and terminal integration. Use when setting up a development environment, configuring Turbo mode, or establishing a fast iteration cycle with Windsurf AI. Trigger with phrases like "windsurf dev setup", "windsurf local development", "windsurf dev environment", "windsurf workflow", "develop with windsurf". '

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-codecan modify filesMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill windsurf-local-dev-loop --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Version: 1.11.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadWriteEditBash(npm:*)Bash(pnpm:*)Grep
Requires: Designed for Claude Code, also compatible with Codex and OpenClaw
Path: skills/.curated/windsurf-local-dev-loop/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,630
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 ```markdown <!-- .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 ```gitignore # .codeiumignore - exclude from AI indexing (same syntax as .gitignore) node_modules/ .next/ dist/

What's inside
Steps it walks through
  1. Overview
  2. Prerequisites
  3. Instructions
  4. Step 1: Create .windsurfrules for Project Context
  5. Step 2: Configure .codeiumignore
  6. Step 3: Set Up Turbo Mode for Fast Terminal Execution
  7. Step 4: Use Previews for UI Development
  8. Step 5: The Dev Loop
  9. Step 6: Terminal Integration
  10. Error Handling
  11. Examples
  12. Quick Project Bootstrap
  13. Debug-Fix Loop
  14. Resources
More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the windsurf-local-dev-loop skill do?

Configure Windsurf local development workflow with Cascade, Previews, and terminal integration. Use when setting up a development environment, configuring Turbo mode, or establishing a fast iteration cycle with Windsurf AI. Trigger with phrases like "windsurf dev setup", "windsurf local development", "windsurf dev environment", "windsurf workflow", "develop with windsurf". '

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill windsurf-local-dev-loop --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going