Devin Desktop (formerly Windsurf)
Devin Desktop is the AI code editor that used to be called Windsurf. It reads the project's AGENTS.md and the rule files in .devin/rules/.
Configuration File
.devin/rules/project.mdA Markdown rule file. LynxPrompt starts it with trigger: always_on frontmatter, so the rule applies to every request. Devin Desktop still reads .windsurf/rules/ and the old .windsurfrules file, and lynxp push picks up all three.
File Location
your-project/ ├── .devin/ │ └── rules/ │ └── project.md ← Your rule file goes here ├── src/ └── package.json
Devin Desktop reads the root AGENTS.md on every request too. When you pick it together with other tools, LynxPrompt writes the rules once in AGENTS.md and skips the separate rule file.
How Devin Desktop Uses It
Devin Desktop's agent reads your rules to:
- Understand your project context
- Generate code matching your style
- Follow your specified conventions
- Provide more relevant suggestions
Example Rules File
--- trigger: always_on --- # Project Rules ## Project Overview Full-stack e-commerce application ## Tech Stack - Frontend: Vue 3 with Composition API - Backend: Python FastAPI - Database: PostgreSQL - Cache: Redis ## Code Guidelines ### Frontend - Use TypeScript for all Vue components - Prefer <script setup> syntax - Use Pinia for state management - Follow Vue style guide ### Backend - Use Pydantic models for validation - Type hints on all functions - Async endpoints where beneficial - SQLAlchemy ORM for database ## Git Conventions - Conventional commits - Feature branches from main - Squash merge for PRs
Tips
Structure with Headers
Use markdown headers to organize rules by topic.
Separate Frontend/Backend
For full-stack projects, clearly separate rules for each part.
Include Examples
Show code snippets demonstrating your preferred patterns.
Keep Updated
Update rules as your project evolves and conventions change.