Install command
Provided
Configure and optimize Cursor and Windsurf AI code editors for maximum productivity. Set up agent mode, composer features, keybindings, and AI-powered refactoring workflows. Customize with .cursorrules and .windsurfrules for project-specific guidance.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.
0
96
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as first-party.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
Package marked verified.
Checksum metadata
SHA-256 hash is present.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Install command
Provided
Config snippet
Not provided
Copy snippet
Provided
Prerequisites
6 to clear
Platforms
6 listed
Difficulty
100/100
Adoption plan
Current risk score 0/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
Package verification/checksum metadata is available.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (6/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is present.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
6/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is available.
rollout
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
6 prerequisites to line up before setup. Have accounts and credentials ready first.
Safety & privacy surface
1 safety and 1 privacy notes across 2 risk areas. Review closely: credentials & tokens, network access.
| Platform | Support | Install path |
|---|---|---|
| claude-code | Native | .claude/skills/<skill-name>/SKILL.md |
| codex | Native | .agents/skills/<skill-name>/SKILL.md |
| windsurf | Native | .windsurf/skills/<skill-name>/SKILL.md |
| gemini | Native | .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md |
| cursor | Adapter | .cursor/rules/<skill-name>.mdc |
| cli | Manual | AGENTS.md or tool-specific context file |
# Project: Next.js 15 SaaS Application
## Tech Stack
- Next.js 15.0+ (App Router, Server Actions)
- React 19.0+
- TypeScript 5.5+ (strict mode)
- Tailwind CSS 4.0+
- shadcn/ui components
- Zod for validation
- Prisma with PostgreSQL
## Coding Conventions
- Use named exports (no default exports except pages)
- Prefix server actions with 'action'
- All async functions must have error handling
- Use Zod schemas for all form inputs
- Components in PascalCase, files in kebab-case
- Max function length: 50 lines
- All props must have TypeScript interfaces
## Patterns to Follow
- Server Actions for mutations (no API routes)
- React Server Components by default
- Client components only when needed ('use client')
- Parallel data fetching with Promise.all
- Error boundaries for all async components
- Loading states with Suspense
- Form validation with Zod + React Hook Form
## Patterns to Avoid
- Don't use 'any' type (use 'unknown' if needed)
- Don't fetch in client components (use server)
- Don't bypass TypeScript with @ts-ignore
- Don't create custom hooks without jsdoc
- Don't use inline styles (use Tailwind)
## Testing
- Unit tests with Vitest
- E2E tests with Playwright
- Minimum 80% coverage
- Test file naming: *.test.ts
## Performance
- Dynamic imports for heavy components
- Image optimization with next/image
- Font optimization with next/font
- Metadata API for SEOClaude can help you configure and optimize Cursor or Windsurf AI code editors for maximum productivity. Both editors provide AI-powered code completion, multi-file editing, and intelligent refactoring. Cursor excels with its Agent mode and Composer features, while Windsurf emphasizes collaborative flows and Cascade AI. From initial setup to advanced workflows, Claude handles IDE configuration and optimization.
SKILL.md.SKILL.md content as reusable workflow instructions..gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported..cursor/rules/*.mdc adapter for project rules.Required:
What Claude handles automatically:
Prompt: "Help me set up Cursor with Claude Sonnet model. Configure keybindings for: inline completion (Tab), chat (Cmd+K), composer (Cmd+I), and agent mode. Optimize for React/TypeScript projects."
Claude will:
Prompt: "Configure Cursor Agent mode for: automatic file edits, test generation, refactoring tasks, and documentation. Set guardrails to prevent breaking changes."
Claude will:
Prompt: "Create .cursorrules file for Next.js 15 project with: TypeScript strict mode, shadcn/ui components, Tailwind CSS, server actions, and Zod validation. Include coding standards."
Claude will:
Prompt: "Set up Windsurf Cascade for: renaming components across files, updating import paths, refactoring prop types, and running type checks. Configure to preview changes before applying."
Claude will:
Use .cursorrules: Create project-specific rules file with tech stack, conventions, and patterns. AI reads this for context.
Composer for Large Changes: Use Cmd+I (Cursor) or Cascade (Windsurf) for multi-file edits. More powerful than inline chat.
@ Mentions for Context: Use @filename, @folder, @docs to give AI specific context. Reduces hallucinations.
Agent Mode Guardrails: Set file permissions and review changes. Don't let agent edit critical files unsupervised.
Model Selection: Claude Sonnet for code quality, GPT-4 for speed. Switch based on task complexity.
Token Optimization: Use codebase indexing wisely. Exclude node_modules, dist, .next from context.
"Configure Cursor for React refactoring workflow:
1. Set up .cursorrules with React 19 patterns
2. Enable TypeScript strict mode validation
3. Configure agent mode for component splits
4. Add rules for shadcn/ui usage
5. Set up automatic prop-types to TS conversion
6. Configure test generation with Vitest
7. Enable preview for all agent changes
8. Add rollback shortcuts"
"Set up Windsurf for API development:
1. Create .cursorrules for FastAPI/Next.js API routes
2. Configure agent to generate OpenAPI docs
3. Set up automatic validation with Zod
4. Add error handling templates
5. Configure test generation
6. Set up database query optimization
7. Enable security scanning
8. Add rate limiting patterns"
"Configure Cursor for migrating JS to TS:
1. Set up .cursorrules for TypeScript migration
2. Configure agent for file-by-file conversion
3. Add type inference rules
4. Set up any type replacement
5. Configure import path updates
6. Enable type checking after each file
7. Add rollback on type errors
8. Generate migration report"
"Set up Windsurf for test generation:
1. Configure agent for unit test creation
2. Add .cursorrules for testing patterns
3. Set up coverage threshold checks
4. Configure mock generation
5. Add integration test templates
6. Set up snapshot testing rules
7. Enable test runner integration
8. Generate coverage reports"
Issue: "AI suggestions are slow or timing out" Solution: Reduce context size by excluding large folders in settings. Use @filename for specific context instead of full codebase. Check API rate limits. Switch to faster model (GPT-3.5) for simple edits. Clear index and rebuild.
Issue: "Agent mode making unwanted changes" Solution: Add .cursorrules with explicit guidelines. Set file permissions to read-only for critical files. Enable preview mode to review all changes. Use 'explain' prompts before 'do' prompts. Add 'do not modify' comments in code.
Issue: "API costs higher than expected" Solution: Exclude unnecessary folders from indexing. Use caching (Cursor's @codebase). Switch to smaller models for simple tasks. Disable auto-complete for comments. Review token usage in settings. Use local models for basic completion.
Issue: "Keybindings conflicting with other extensions" Solution: Check keybindings.json for conflicts. Reassign Cursor/Windsurf shortcuts. Disable conflicting extensions. Use Cmd+K+S (Cursor) to view all shortcuts. Export keybindings and version control them.
Issue: "AI not using project context correctly" Solution: Create detailed .cursorrules file. Use @docs to reference documentation. Add README with architecture overview. Use @folder for package-specific context. Verify codebase indexing is complete. Rebuild index if stale.
Show that Cursor Windsurf AI Code Editor Skill - Claude Code Skills is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/skills/cursor-windsurf-ai-ide-setup)Cursor Windsurf AI Code Editor Skill - Claude Code Skills side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).
Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.
| Field | Configure and optimize Cursor and Windsurf AI code editors for maximum productivity. Set up agent mode, composer features, keybindings, and AI-powered refactoring workflows. Customize with .cursorrules and .windsurfrules for project-specific guidance. Open dossier | Create portable Agent Skills, generate platform adapters, validate package metadata, and prepare PR-first HeyClaude submissions. Open dossier | Master collaborative AI-assisted development with Windsurf IDE's Cascade AI, multi-file context awareness, and Flow patterns for team workflows. Open dossier | Expert Claude Code terminal ergonomics capability pack for auditing multiline input, Option/Meta shortcuts, tmux passthrough, notifications, fullscreen rendering, themes, status lines, Vim mode, and custom keybindings before a user blames Claude for terminal behavior. Open dossier |
|---|---|---|---|---|
| Next stepsDiffers | ||||
| Trust | ||||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trustDiffers | Package verified2025-10-23 | Package verified2026-06-02 | Package verified2025-10-16 | Package not verified |
| Source provenanceDiffers | Source-backed | No submission link | No submission link | Submission linkedSource submission |
| SubmitterDiffers | — | — | — | YB0y |
| Install risk | Review first | Low risk | Low risk | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | ||
| Category | skills | skills | skills | skills |
| Source | first-party | first-party | first-party | source-backed |
| Author | JSONbored | JSONbored | JSONbored | YB0y |
| Added | 2025-10-23 | 2026-04-27 | 2025-10-16 | 2026-06-10 |
| Platforms | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI |
| Source repo | — | — | — | — |
| Safety notes | ✓Setup downloads and unzips a package and changes IDE configuration files; review what it writes and run it in a trusted workspace. | ✓Downloads and unzips a HeyClaude-maintainer-packaged skill archive into a local folder when using the install command. Produces public skill package and submission drafts; review generated files before opening a PR or sharing them. | ✓Setup downloads and unzips a package and changes Windsurf IDE configuration; review what it writes and run it in a trusted workspace. | ✓This skill recommends terminal and Claude Code configuration changes; it must not edit dotfiles, keybindings, hooks, themes, or tmux settings without showing the proposed diff first. `/terminal-setup` writes terminal or editor keybindings and may adjust integrated-terminal settings; run it in the host terminal and record what changed before relying on it. tmux passthrough allows escape sequences to reach the outer terminal; enable it deliberately, especially on shared, remote, or security-sensitive hosts. Notification hooks can execute local commands when Claude needs attention; keep them simple, review command paths, and avoid hooks that send prompts or logs to third-party services. Fullscreen rendering, theme files, status lines, and keybinding changes should be treated as reversible local UI preferences, not fixes for model quality or project bugs. |
| Privacy notes | ✓Cursor and Windsurf send your code and prompts to their AI backends to power completion and chat; review each editor's data-handling settings and keep API keys out of committed config. | ✓Does not require credentials and should only process public skill requirements, source URLs, and validation notes. Do not include private repository names, customer data, tokens, or unpublished operating details in generated skill packages. | ✓Windsurf (Cascade) sends your code and prompts to its AI backend to power multi-file operations; review Windsurf's data-handling settings and keep API keys and secrets out of committed config. | ✓Terminal settings, tmux files, keybinding files, status line commands, and hook snippets can expose usernames, hostnames, project paths, shell aliases, secrets in environment commands, and internal repository names. Notification commands and status line scripts may reveal task names, working directories, git branches, model names, costs, or local operational context. Remote terminal and SSH notification behavior can surface session activity on a local desktop; confirm the user is comfortable with that visibility. Public PR or issue notes should summarize symptoms and redacted settings, not paste complete dotfiles, shell history, terminal transcripts, or private hook scripts. |
| Prerequisites |
|
|
|
|
| Install | | | | — |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.