windsurfrules v5 (kinopeee) — Summary

windsurfrules v5 is a bilingual (Japanese/English) Windsurf rule set — a direct port of kinopeee/cursorrules from Cursor's MDC format to Windsurf's .windsurf/rules/*.md format (with trigger: always_on replacing alwaysApply: true) and .windsurf/workflows/*.md for workflow commands. The content is structurally identical: v5 core rule, commit message format, PR message format, test strategy, prompt injection guard, and three git workflow commands (commit-only, commit-push, commit-push-pr). Additionally, the repo includes an .agent/ directory for Antigravity (a newer Windsurf-adjacent AI coding tool). The main architectural difference from the Cursor version is the Windsurf rule front matter format (trigger: always_on, globs:, no alwaysApply).

differs_from_seeds: Identical to cursorrules-kinopeee in content (same repository author, same v5 rules), but targets Windsurf instead of Cursor. The closest seed is agent-os for behavioral standards. The primary research interest of this entry relative to cursorrules is the format translation: shows how Cursor's MDC alwaysApply translates to Windsurf's trigger: always_on, and how .cursor/commands/ translates to .windsurf/workflows/. This is a canonical example of the same content distributed across IDE-specific rule file formats.

windsurfrules v5 (kinopeee) — Overview

Origin

Created by kinopeee (GitHub) as a direct port of cursorrules. Active (last commit December 2025). Stars: 364. MIT license. Explicitly described as:

"This repository provides custom instructions optimized for Windsurf and Antigravity. It is a port of cursorrules adapted for Windsurf Cascade and Antigravity."

Philosophy

Identical to cursorrules v5 — the same behavioral philosophy applies:

• Tricolor task classification (🟢/🟡/🔴)
• Stop-then-confirm security protocol for injection defense
• Structured git workflow with branch protection
• Bilingual Japanese/English support

Format Translation

The key technical contribution of this repo vs cursorrules is demonstrating the IDE format translation:

Antigravity Support

In addition to Windsurf, the repo includes .agent/ directory rules for Antigravity — a newer AI coding tool in the Windsurf ecosystem.

Usage

# Windsurf
cp -r windsurf-antigravity-rules/en/.windsurf ~/your-project/

# Antigravity
cp -r windsurf-antigravity-rules/en/.agent ~/your-project/

windsurfrules v5 (kinopeee) — Architecture

Distribution

Standalone repository. Clone and copy directories to project root.

Install

# Windsurf (English)
cp -r windsurfrules/en/.windsurf ~/your-project/

# Windsurf (Japanese)
cp -r windsurfrules/ja/.windsurf ~/your-project/

# Antigravity (English)
cp -r windsurfrules/en/.agent ~/your-project/

OR configure via Windsurf settings:

Windsurf > Settings > Set Workspace AI Rules > Edit Rules

Directory Tree

windsurfrules/
├── en/                           # English version
│   ├── .windsurf/
│   │   ├── rules/
│   │   │   ├── v5.md             # Core rule (trigger: always_on)
│   │   │   ├── commit-message-format.md
│   │   │   ├── pr-message-format.md
│   │   │   ├── test-strategy.md
│   │   │   └── prompt-injection-guard.md
│   │   └── workflows/            # Workflow commands (Windsurf equivalent of Cursor commands)
│   │       ├── commit-only.md
│   │       ├── commit-push.md
│   │       └── commit-push-pr.md
│   └── .agent/                   # Antigravity format
│       └── ...
├── ja/                           # Japanese version (same structure)
├── LICENSE
├── README.md
└── TRANSLATION_GUIDE.md

Rule File Format

Windsurf rule format (.windsurf/rules/*.md):

---
trigger: always_on
description: Foundation rules for coding assistance. Defines task classification 
             (lightweight/standard/critical), tool usage policies, and response style
globs:
---
# Rule content (identical to Cursor version)...

Comparison with Cursor format:

Target AI Tools

• Primary: Windsurf (.windsurf/rules/ format)
• Secondary: Antigravity (.agent/ format)

Required Runtime

None beyond Windsurf IDE.

windsurfrules v5 (kinopeee) — Components

Rule Files (5 total) — identical content to cursorrules v5

Workflow Commands (3 total)

Windsurf Tool Names (differ from Cursor)

The v5.md rule references Windsurf-specific tool names:

• read_file → same
• edit / multi_edit (Windsurf) vs apply_patch (Cursor)
• grep_search / code_search (Windsurf) vs grep / codebase_search (Cursor)
• run_command (Windsurf) vs run_terminal_cmd (Cursor)
• search_web (Windsurf) vs web_search (Cursor)
• Blocking: false (Windsurf long-running commands) vs is_background: true (Cursor)
• update_plan (Windsurf critical tasks) vs create_plan (Cursor)

These differences are meaningful — the tool name translations are not just cosmetic; they reflect Windsurf's and Cursor's different tool naming conventions.

windsurfrules v5 (kinopeee) — Uniqueness

differs_from_seeds

Identical in content to cursorrules-kinopeee (same author, same v5 philosophy, same security rules). The architectural distinction is pure format translation: Cursor's alwaysApply: true MDC → Windsurf's trigger: always_on MD, and Cursor's create_plan tool → Windsurf's update_plan tool. Like cursorrules, the closest seed comparison is agent-os (standards-first behavioral rules). The primary value of studying this entry is the format mapping it demonstrates between Cursor and Windsurf rule systems — both define "always-on" rules, both support on-demand rules, both have workflow/command file directories, but use different directory paths, different front matter keys, and different tool names. This translation table is useful for any framework author wanting multi-IDE support.

Positioning

• Functional duplicate of cursorrules for Windsurf/Antigravity: Same content, different format
• Format reference: Canonical example of Cursor → Windsurf format translation
• 364 stars: Less popular than the Cursor version (1,118 stars)

Observable Failure Modes

Same as cursorrules v5:

1. No memory/persistence
2. No spec discipline
3. Critical task classification ambiguity
4. MCP/gh dependency for PR creation

Additional Windsurf-specific: 5. update_plan vs create_plan: Windsurf uses update_plan for critical tasks — if Windsurf changes its plan management API, the rule breaks. 6. Antigravity stability: Antigravity is a newer, less-established tool — the .agent/ directory rules may need frequent updates.