Zed vs Cursor Vergleich

// Zed - Agent, externer ACP-Agent und Editor-Einstellungen (settings.json)
{
  "agent": {
    "commit_message_instructions": "Use the Conventional Commits format",
    "tool_permissions": {
      "default": "confirm"
    }
  },
  "agent_servers": {
    "custom-acp-agent": {
      "type": "custom",
      "command": "node",
      "args": ["~/projects/agent/index.js", "--acp"],
      "env": {}
    }
  },
  "edit_predictions": {
    "provider": "zed"
  },
  "lsp": {
    "rust-analyzer": {
      "initialization_options": {
        "check": { "command": "clippy" }
      }
    }
  },
  "languages": {
    "Rust": {
      "format_on_save": "on",
      "tab_size": 4
    }
  },
  "vim_mode": false,
  "theme": "One Dark",
  "buffer_font_size": 15
}

// Cursor - Projektregel-Datei (.cursor/rules/backend.mdc)
---
description: Backend API standards
globs:
  - "src/api/**/*.ts"
alwaysApply: true
---

# Code rules
- Validate every endpoint input with a Zod schema
- Error body must be machine-readable: { "error": "invalid_payload" }
- Every new route requires a matching test file

// .cursorignore - Pfade, die der Agent nicht scannt
node_modules/
dist/
*.generated.ts
.env*

// Ein Custom Mode wird nicht über eine Config-Datei geöffnet, sondern indem man im "/"-Menü
// einen Skill auswählt und ihn mit Option+Enter (Windows: Alt+Enter) anheftet.
// Skill-Datei: .cursor/skills/reviewer/SKILL.md
---
name: reviewer
description: Read-only review pass before opening a pull request
icon: shield
color: blue
---

Review the diff only; do not edit files.
Report findings as a numbered list with file path and line number.